<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Data Flexibility: To Range or Not to Range</title>
	<atom:link href="http://markitechture.com/2008/07/18/data-flexibility-to-range-or-not-to-range/feed/" rel="self" type="application/rss+xml" />
	<link>http://markitechture.com/2008/07/18/data-flexibility-to-range-or-not-to-range/</link>
	<description>Marketing In The Age Of Intelligence</description>
	<lastBuildDate>Wed, 21 Apr 2010 11:54:17 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Markitecht</title>
		<link>http://markitechture.com/2008/07/18/data-flexibility-to-range-or-not-to-range/comment-page-1/#comment-11</link>
		<dc:creator>Markitecht</dc:creator>
		<pubDate>Sun, 20 Jul 2008 18:41:31 +0000</pubDate>
		<guid isPermaLink="false">http://markitechture.com/2008/07/18/data-flexibility-to-range-or-not-to-range/#comment-11</guid>
		<description>Great points!  Actually there are plenty of opportunities to touch base with the lead.  Lead gen is usually a marketing and sales process.  So once marketing has got the lead and qualified it, there is most likely some live follow-up process by sales where some of this information can be verified.  Ideally the follow-up happens very close to the date the lead was generated and the information is not stale.

Let&#039;s say the contact was not interested in purchasing product at the time, it is marketing&#039;s responsibility to maintain a relationship with the contact and ensure that over time the contact refreshes their info.

This can be implicit through another offer form, or explicitly by saying something like: &quot;We&#039;re updating our DB and want to make sure we have your correct info on file&quot;.</description>
		<content:encoded><![CDATA[<p>Great points!  Actually there are plenty of opportunities to touch base with the lead.  Lead gen is usually a marketing and sales process.  So once marketing has got the lead and qualified it, there is most likely some live follow-up process by sales where some of this information can be verified.  Ideally the follow-up happens very close to the date the lead was generated and the information is not stale.</p>
<p>Let&#8217;s say the contact was not interested in purchasing product at the time, it is marketing&#8217;s responsibility to maintain a relationship with the contact and ensure that over time the contact refreshes their info.</p>
<p>This can be implicit through another offer form, or explicitly by saying something like: &#8220;We&#8217;re updating our DB and want to make sure we have your correct info on file&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: HM</title>
		<link>http://markitechture.com/2008/07/18/data-flexibility-to-range-or-not-to-range/comment-page-1/#comment-10</link>
		<dc:creator>HM</dc:creator>
		<pubDate>Sat, 19 Jul 2008 15:06:09 +0000</pubDate>
		<guid isPermaLink="false">http://markitechture.com/2008/07/18/data-flexibility-to-range-or-not-to-range/#comment-10</guid>
		<description>There&#039;s also the dynamic nature of this data to consider. Presumably there&#039;s a lag between when the data is collected and the actual communication to the lead. In cases of sustained communication (newsletters, mailers etc) this lag is implicit. The data will certainly change during the course of this lag, possibly shifting it between the categories you talk about above. My present employer had a staff of 25 in February, has one of 40 right now and plans to grow to 65 by the end of the year. Many category leaps in the course of a year, no? The point I&#039;m trying to make is that if the datapoint truly matters, you ought formulate ways to monitor over the course of your relationship. This is akin to your Salesforce database cleanup activity. I wonder if lead-gen companies actually provide such refreshes on the data they supply, or if they even do such refreshes for their own data. Food for thought.</description>
		<content:encoded><![CDATA[<p>There&#8217;s also the dynamic nature of this data to consider. Presumably there&#8217;s a lag between when the data is collected and the actual communication to the lead. In cases of sustained communication (newsletters, mailers etc) this lag is implicit. The data will certainly change during the course of this lag, possibly shifting it between the categories you talk about above. My present employer had a staff of 25 in February, has one of 40 right now and plans to grow to 65 by the end of the year. Many category leaps in the course of a year, no? The point I&#8217;m trying to make is that if the datapoint truly matters, you ought formulate ways to monitor over the course of your relationship. This is akin to your Salesforce database cleanup activity. I wonder if lead-gen companies actually provide such refreshes on the data they supply, or if they even do such refreshes for their own data. Food for thought.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
