Tracking Ajax Pages with Google Analytics
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’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‘s Ajax.Responder to trigger the urchinTracker function, don’t! It generates a huge overhead and actually obscures your statistics.
