<?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: Analytics and Customer Driven Decisions</title>
	<atom:link href="http://www.100dollarseo.com/analytics-and-customer-driven-decisions/blogging/feed" rel="self" type="application/rss+xml" />
	<link>http://www.100dollarseo.com/analytics-and-customer-driven-decisions/blogging</link>
	<description>You Get What You Pay For</description>
	<pubDate>Wed, 07 Jan 2009 00:52:41 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Carlos del Rio</title>
		<link>http://www.100dollarseo.com/analytics-and-customer-driven-decisions/blogging/comment-page-1#comment-191</link>
		<dc:creator>Carlos del Rio</dc:creator>
		<pubDate>Tue, 29 Jul 2008 18:56:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.100dollarseo.com/?p=198#comment-191</guid>
		<description>You can also solve the problem by setting a cookie. Let me know if that is the way you want to go.</description>
		<content:encoded><![CDATA[<p>You can also solve the problem by setting a cookie. Let me know if that is the way you want to go.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carlos del Rio</title>
		<link>http://www.100dollarseo.com/analytics-and-customer-driven-decisions/blogging/comment-page-1#comment-190</link>
		<dc:creator>Carlos del Rio</dc:creator>
		<pubDate>Tue, 29 Jul 2008 18:27:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.100dollarseo.com/?p=198#comment-190</guid>
		<description>That's a good one. 
Normally I would use a lookup table for all the IP addresses, but Google doesn't support that. 
So have your beta testers visit http://whatsmyip.org/ and tell you the IP.

Once you have the IPs send me an e-mail. I'll go into more detail on working around the the lack of Lookup Tables.</description>
		<content:encoded><![CDATA[<p>That&#8217;s a good one.<br />
Normally I would use a lookup table for all the IP addresses, but Google doesn&#8217;t support that.<br />
So have your beta testers visit <a href="http://whatsmyip.org/">http://whatsmyip.org/</a> and tell you the IP.</p>
<p>Once you have the IPs send me an e-mail. I&#8217;ll go into more detail on working around the the lack of Lookup Tables.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MikeTek</title>
		<link>http://www.100dollarseo.com/analytics-and-customer-driven-decisions/blogging/comment-page-1#comment-189</link>
		<dc:creator>MikeTek</dc:creator>
		<pubDate>Tue, 29 Jul 2008 11:53:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.100dollarseo.com/?p=198#comment-189</guid>
		<description>I like the redesign, Carlos.  Looking sharp.  

I'm definitely looking forward to the release of the new content. 

I'm not sure if it's already "on the list," but I recently had a bit of an analytics conundrum with a client - perhaps you have a solution.  Essentially, a new website was developed for an industrial association.  The site is live, but has not been actively promoted yet.  The client wanted to give a group of association members the chance to "beta test" the site but did not want their activities to convolute the analytics.  The trouble: collecting IP addresses from all beta testers (of which there are likely to be several dozen) and filtering them out of Google Analytics manually.  The site is database driven (on DotNetNuke) and relatively large.  

Not sure if there's a simple solution to that problem, but I'd be interested to hear your thoughts.</description>
		<content:encoded><![CDATA[<p>I like the redesign, Carlos.  Looking sharp.  </p>
<p>I&#8217;m definitely looking forward to the release of the new content. </p>
<p>I&#8217;m not sure if it&#8217;s already &#8220;on the list,&#8221; but I recently had a bit of an analytics conundrum with a client - perhaps you have a solution.  Essentially, a new website was developed for an industrial association.  The site is live, but has not been actively promoted yet.  The client wanted to give a group of association members the chance to &#8220;beta test&#8221; the site but did not want their activities to convolute the analytics.  The trouble: collecting IP addresses from all beta testers (of which there are likely to be several dozen) and filtering them out of Google Analytics manually.  The site is database driven (on DotNetNuke) and relatively large.  </p>
<p>Not sure if there&#8217;s a simple solution to that problem, but I&#8217;d be interested to hear your thoughts.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
