<?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 Invalid Hits: Accuracy is Quite Important</title>
	<atom:link href="http://joelnagy.com/blog/2009/06/tracking-invalid-hits-accuracy-is-quite-important/feed/" rel="self" type="application/rss+xml" />
	<link>http://joelnagy.com/blog/2009/06/tracking-invalid-hits-accuracy-is-quite-important/</link>
	<description>web technology is a way of life</description>
	<pubDate>Wed, 08 Sep 2010 03:09:45 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Sinan Ascioglu</title>
		<link>http://joelnagy.com/blog/2009/06/tracking-invalid-hits-accuracy-is-quite-important/comment-page-1/#comment-163</link>
		<dc:creator>Sinan Ascioglu</dc:creator>
		<pubDate>Fri, 17 Jul 2009 20:52:50 +0000</pubDate>
		<guid isPermaLink="false">http://joelnagy.com/blog/?p=140#comment-163</guid>
		<description>Well,
I had been spending a lot of hours in my last 3 years reading analytics, and I think that wouldn't be the biggest problem in tracking user stats. Besides if pages get being tracked accurately or not, I think the big problem that people couldn't still solve is how to provide that data. We know that, since tracking == raw data. It doesn't help much, so everyone wrote their own algorithms to analyze data and come up with terms like 'unique visitor', 'pageview vs. unique pageviews', 'time spend on site', etc.. I think the questionability of these algorithms are far more of an issue than if pages being tracked accurately or not. Take 'time spend on site' for example; every time I meet an analytics professional, I ask how it gets tracked, and every time the answer I get is different, and none of them can correctly define the 'time' spend on site, since no website starts a counter watch to count that time. Eg. Google analytics counts this as (last page hit time - first page hit time) in the exact same session. This is especially a bad calculation method for sites like NYTimes.com, since one would expect to find an article after 3 clicks, read the article for 10 minutes, and close the site. Because the calculations went very complicated, they don't show unique pageviews and visit for the same page for example... 
And yet, it become even harder to track since we started to track event calls, ajax calls, etc.. so, is an event call another hit for a visit? should I include that in a "we broke the record of our monthly visitors!" report... 
So since giving thought on these, I started looking at the data more referencing to itself than absolute number. Those number are good for comparing (with last month, with this section, etc..) rather than seeing them absolute numbers..
My 2 cents..</description>
		<content:encoded><![CDATA[<p>Well,<br />
I had been spending a lot of hours in my last 3 years reading analytics, and I think that wouldn&#8217;t be the biggest problem in tracking user stats. Besides if pages get being tracked accurately or not, I think the big problem that people couldn&#8217;t still solve is how to provide that data. We know that, since tracking == raw data. It doesn&#8217;t help much, so everyone wrote their own algorithms to analyze data and come up with terms like &#8216;unique visitor&#8217;, &#8216;pageview vs. unique pageviews&#8217;, &#8216;time spend on site&#8217;, etc.. I think the questionability of these algorithms are far more of an issue than if pages being tracked accurately or not. Take &#8216;time spend on site&#8217; for example; every time I meet an analytics professional, I ask how it gets tracked, and every time the answer I get is different, and none of them can correctly define the &#8216;time&#8217; spend on site, since no website starts a counter watch to count that time. Eg. Google analytics counts this as (last page hit time - first page hit time) in the exact same session. This is especially a bad calculation method for sites like NYTimes.com, since one would expect to find an article after 3 clicks, read the article for 10 minutes, and close the site. Because the calculations went very complicated, they don&#8217;t show unique pageviews and visit for the same page for example&#8230;<br />
And yet, it become even harder to track since we started to track event calls, ajax calls, etc.. so, is an event call another hit for a visit? should I include that in a &#8220;we broke the record of our monthly visitors!&#8221; report&#8230;<br />
So since giving thought on these, I started looking at the data more referencing to itself than absolute number. Those number are good for comparing (with last month, with this section, etc..) rather than seeing them absolute numbers..<br />
My 2 cents..</p>
]]></content:encoded>
	</item>
</channel>
</rss>
