<?xml version="1.0" encoding="UTF-8ISO-8859-1"?><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: Google Finally Announces Mobile Analytics</title>
	<atom:link href="http://www.brysonmeunier.com/google-finally-announces-mobile-analytics/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.brysonmeunier.com/google-finally-announces-mobile-analytics/</link>
	<description>Mobile SEO and Web Search Optimization Strategies from Chicago SEO Bryson Meunier</description>
	<lastBuildDate>Sun, 07 Mar 2010 01:39:15 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Bryson Meunier</title>
		<link>http://www.brysonmeunier.com/google-finally-announces-mobile-analytics/comment-page-1/#comment-5991</link>
		<dc:creator>Bryson Meunier</dc:creator>
		<pubDate>Sun, 25 Oct 2009 16:30:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.brysonmeunier.com/?p=300#comment-5991</guid>
		<description>Thanks, Larry. I saw that too, and appreciate the attention from the good folks at Bango, as always. It&#039;s important to note, however, that the study of mine that Andy mentions happened prior to the GA mobile tracking announcement, and didn&#039;t account for the improvements I&#039;m mentioning here. 

Point taken, though. There will likely still be inaccuracies with Google Analytics, even with the improved mobile tracking. From the &quot;known issues&quot; included with the tracking tag:

&lt;blockquote&gt;Inaccurate Locations. Google Analytics uses IP addresses to determine user location for the Map Overlay report. These are subject to possible inaccuracy, as mobile IPs originate from the wireless carrier gateway which is not necessarily co-located with mobile users.&lt;/blockquote&gt;

More later as they roll this out...</description>
		<content:encoded><![CDATA[<p>Thanks, Larry. I saw that too, and appreciate the attention from the good folks at Bango, as always. It&#8217;s important to note, however, that the study of mine that Andy mentions happened prior to the GA mobile tracking announcement, and didn&#8217;t account for the improvements I&#8217;m mentioning here. </p>
<p>Point taken, though. There will likely still be inaccuracies with Google Analytics, even with the improved mobile tracking. From the &#8220;known issues&#8221; included with the tracking tag:</p>
<blockquote><p>Inaccurate Locations. Google Analytics uses IP addresses to determine user location for the Map Overlay report. These are subject to possible inaccuracy, as mobile IPs originate from the wireless carrier gateway which is not necessarily co-located with mobile users.</p></blockquote>
<p>More later as they roll this out&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Larry Larmor</title>
		<link>http://www.brysonmeunier.com/google-finally-announces-mobile-analytics/comment-page-1/#comment-5981</link>
		<dc:creator>Larry Larmor</dc:creator>
		<pubDate>Sun, 25 Oct 2009 10:02:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.brysonmeunier.com/?p=300#comment-5981</guid>
		<description>Andy Bovingdon has blogged about this - and he even mentions Bryson!
http://blog.bango.com/2009/10/21/google-analytics-plays-mobile-catch-up%e2%80%a6%e2%80%a6and-still-manages-to-come-last/</description>
		<content:encoded><![CDATA[<p>Andy Bovingdon has blogged about this &#8211; and he even mentions Bryson!<br />
<a href="http://blog.bango.com/2009/10/21/google-analytics-plays-mobile-catch-up%e2%80%a6%e2%80%a6and-still-manages-to-come-last/" rel="nofollow">http://blog.bango.com/2009/10/21/google-analytics-plays-mobile-catch-up%e2%80%a6%e2%80%a6and-still-manages-to-come-last/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->