<?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: Tracking Ajax Requests in Analytics</title>
	<atom:link href="http://ajaxian.com/archives/tracking-ajax-requests-in-analytics/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/tracking-ajax-requests-in-analytics</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Tue, 16 Mar 2010 01:41:49 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Alex</title>
		<link>http://ajaxian.com/archives/tracking-ajax-requests-in-analytics/comment-page-1#comment-249127</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Sun, 08 Apr 2007 09:31:55 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/tracking-ajax-requests-in-analytics#comment-249127</guid>
		<description>Iâ€™m working on a new analytics platform explicitly designed for Ajax applications - http://www.ajaxmetrics.com - and Iâ€™d love to hear what you have to say about it.</description>
		<content:encoded><![CDATA[<p>Iâ€™m working on a new analytics platform explicitly designed for Ajax applications &#8211; <a href="http://www.ajaxmetrics.com" rel="nofollow">http://www.ajaxmetrics.com</a> &#8211; and Iâ€™d love to hear what you have to say about it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ITå¿«é¤&#8212;&#8212;&#8211;å‘çŽ°,åˆ†äº«,å…³æ³¨äº’è”ç½‘ &#187; 10-13</title>
		<link>http://ajaxian.com/archives/tracking-ajax-requests-in-analytics/comment-page-1#comment-127641</link>
		<dc:creator>ITå¿«é¤&#8212;&#8212;&#8211;å‘çŽ°,åˆ†äº«,å…³æ³¨äº’è”ç½‘ &#187; 10-13</dc:creator>
		<pubDate>Fri, 13 Oct 2006 05:43:47 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/tracking-ajax-requests-in-analytics#comment-127641</guid>
		<description>[...] å¾ˆé…·çš„å›¾åƒåˆ‡æ¢æ•ˆæžœ http://smoothslideshow.jondesign.net/showcase.html  Tracking Ajax Requests in Analytics [...]</description>
		<content:encoded><![CDATA[<p>[...] å¾ˆé…·çš„å›¾åƒåˆ‡æ¢æ•ˆæžœ <a href="http://smoothslideshow.jondesign.net/showcase.html" rel="nofollow">http://smoothslideshow.jondesign.net/showcase.html</a>  Tracking Ajax Requests in Analytics [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doug Karr</title>
		<link>http://ajaxian.com/archives/tracking-ajax-requests-in-analytics/comment-page-1#comment-126575</link>
		<dc:creator>Doug Karr</dc:creator>
		<pubDate>Thu, 12 Oct 2006 15:20:34 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/tracking-ajax-requests-in-analytics#comment-126575</guid>
		<description>You can also utilize the Funnel controls within Google Analytics.  This is useful to identify what step in your Ajax people have gotten to or abandoned on.  I&#039;ve done this with &lt;a href=&quot;http://www.payraisecalculator.com&quot; rel=&quot;nofollow&quot;&gt;Payraise Calculator&lt;/a&gt; to identify how many times the calculator was executed.

Here&#039;s an example:
urchinTracker(&quot;/funnel_G1/step2.html&quot;);</description>
		<content:encoded><![CDATA[<p>You can also utilize the Funnel controls within Google Analytics.  This is useful to identify what step in your Ajax people have gotten to or abandoned on.  I&#8217;ve done this with <a href="http://www.payraisecalculator.com" rel="nofollow">Payraise Calculator</a> to identify how many times the calculator was executed.</p>
<p>Here&#8217;s an example:<br />
urchinTracker(&#8221;/funnel_G1/step2.html&#8221;);</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fading Roses &#38; Raging Viruses &#187;</title>
		<link>http://ajaxian.com/archives/tracking-ajax-requests-in-analytics/comment-page-1#comment-125500</link>
		<dc:creator>Fading Roses &#38; Raging Viruses &#187;</dc:creator>
		<pubDate>Wed, 11 Oct 2006 18:01:54 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/tracking-ajax-requests-in-analytics#comment-125500</guid>
		<description>[...] [::[ Wed 11 Oct 2006 ]::[ General ]::[ ]::]  I just read a post over at Ajaxian.com on how to use Google Analytics online, another to track Ajax Pages. Google Analytics is a really good tool for Web 1.0 fashioned pages but is terribly wrong for Web 2.0, first of all a pageview cannot be translated to anything in an Ajax Page. Is a refresh of a part of the page, let&#8217;s say the user list currentlypageview or is only the change of the main content a new pageview? Google Analytics themselfs suggest that you call the urchinTracker upon every successful XMLHttpRequest, but I believe that this is really dangerous. By triggering too many pageviews we first of all obscure the data we are actually interested in (how do you distinguish a single content reload among thousands of minor updates of some small widget?) and you significantly reduce the speed of your application by generating additional overhead. So my advise: although it might be tempting to use things like Prototype&#8217;s Ajax.Responder to trigger the urchinTracker function, don&#8217;t! It generates a huge overhead and actually obscures your statistics.Technorati Tags: Ajax, Google, Google Analytics, Statistics [...]</description>
		<content:encoded><![CDATA[<p>[...] [::[ Wed 11 Oct 2006 ]::[ General ]::[ ]::]  I just read a post over at Ajaxian.com on how to use Google Analytics online, another to track Ajax Pages. Google Analytics is a really good tool for Web 1.0 fashioned pages but is terribly wrong for Web 2.0, first of all a pageview cannot be translated to anything in an Ajax Page. Is a refresh of a part of the page, let&#8217;s say the user list currentlypageview or is only the change of the main content a new pageview? Google Analytics themselfs suggest that you call the urchinTracker upon every successful XMLHttpRequest, but I believe that this is really dangerous. By triggering too many pageviews we first of all obscure the data we are actually interested in (how do you distinguish a single content reload among thousands of minor updates of some small widget?) and you significantly reduce the speed of your application by generating additional overhead. So my advise: although it might be tempting to use things like Prototype&#8217;s Ajax.Responder to trigger the urchinTracker function, don&#8217;t! It generates a huge overhead and actually obscures your statistics.Technorati Tags: Ajax, Google, Google Analytics, Statistics [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Lowell</title>
		<link>http://ajaxian.com/archives/tracking-ajax-requests-in-analytics/comment-page-1#comment-125271</link>
		<dc:creator>Matt Lowell</dc:creator>
		<pubDate>Wed, 11 Oct 2006 16:22:34 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/tracking-ajax-requests-in-analytics#comment-125271</guid>
		<description>This begs an interesting question of why not do JS based analytics yourself?  Not meaning write it yourself but at least host it yourself.  Certainly we have had the tools to do so particularly with Ajax and now we need to insert the appropriate calls anyway.  If you did your own you avoid the load issue concerns.  

I think the main reason these outsource analytics firms exist is because marcom people can&#039;t get reasonable data because they are limited access to servers or their IT people are too busy.  It is just too easy for them to jam a .js file call in their page and be on their way, but in many ways from privacy to delivery it just isn&#039;t the right way to do it.  Cost certainly isn&#039;t the issue either folks because until things like Google Analytics came along lots of these stats services like Omniture or HBX cost huge money ($1000s per month) and many still do.  So purchase or implement in some cases might even be cheaper and maybe the rise of Ajax and the analytics implications from it will drive a new trend?</description>
		<content:encoded><![CDATA[<p>This begs an interesting question of why not do JS based analytics yourself?  Not meaning write it yourself but at least host it yourself.  Certainly we have had the tools to do so particularly with Ajax and now we need to insert the appropriate calls anyway.  If you did your own you avoid the load issue concerns.  </p>
<p>I think the main reason these outsource analytics firms exist is because marcom people can&#8217;t get reasonable data because they are limited access to servers or their IT people are too busy.  It is just too easy for them to jam a .js file call in their page and be on their way, but in many ways from privacy to delivery it just isn&#8217;t the right way to do it.  Cost certainly isn&#8217;t the issue either folks because until things like Google Analytics came along lots of these stats services like Omniture or HBX cost huge money ($1000s per month) and many still do.  So purchase or implement in some cases might even be cheaper and maybe the rise of Ajax and the analytics implications from it will drive a new trend?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tinus</title>
		<link>http://ajaxian.com/archives/tracking-ajax-requests-in-analytics/comment-page-1#comment-125214</link>
		<dc:creator>Tinus</dc:creator>
		<pubDate>Wed, 11 Oct 2006 15:30:07 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/tracking-ajax-requests-in-analytics#comment-125214</guid>
		<description>This also means that when Google&#039;s servers are down, your website get very slow. The Analytics scripts in this case, have to be loaded before your page starts displaying, or am I wrong?</description>
		<content:encoded><![CDATA[<p>This also means that when Google&#8217;s servers are down, your website get very slow. The Analytics scripts in this case, have to be loaded before your page starts displaying, or am I wrong?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CiPHER</title>
		<link>http://ajaxian.com/archives/tracking-ajax-requests-in-analytics/comment-page-1#comment-125177</link>
		<dc:creator>CiPHER</dc:creator>
		<pubDate>Wed, 11 Oct 2006 14:27:42 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/tracking-ajax-requests-in-analytics#comment-125177</guid>
		<description>Hmm.. I ment:
&lt;a href=&quot;link to external site&quot; onclick=&quot;return urchinTracker(this.href)&quot;&gt;External link&lt;a&gt;</description>
		<content:encoded><![CDATA[<p>Hmm.. I ment:<br />
&lt;a href=&#8221;link to external site&#8221; onclick=&#8221;return urchinTracker(this.href)&#8221;&gt;External link&lt;a&gt;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CiPHER</title>
		<link>http://ajaxian.com/archives/tracking-ajax-requests-in-analytics/comment-page-1#comment-125176</link>
		<dc:creator>CiPHER</dc:creator>
		<pubDate>Wed, 11 Oct 2006 14:26:36 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/tracking-ajax-requests-in-analytics#comment-125176</guid>
		<description>Could this be used for tracking clickout&#039;s too?
&lt;a href=&quot;http://link-to-external-site&quot; rel=&quot;nofollow&quot;&gt;External link&lt;/a&gt; ?</description>
		<content:encoded><![CDATA[<p>Could this be used for tracking clickout&#8217;s too?<br />
<a href="http://link-to-external-site" rel="nofollow">External link</a> ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://ajaxian.com/archives/tracking-ajax-requests-in-analytics/comment-page-1#comment-125144</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Wed, 11 Oct 2006 13:31:37 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/tracking-ajax-requests-in-analytics#comment-125144</guid>
		<description>I&#039;ve been using this technique and it&#039;s works great.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been using this technique and it&#8217;s works great.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
