web technology is a way of life
Why do tracking/analytics companies want their code placed at the top of the page (meaning below the opening tag) to be properly tracked? If a user exits quickly they should not be tracked. It seems quite duplicitous to track a user that has exited a page before it has even finished loading. Granted if you have a site that takes a bit to load you shouldn’t wait till everything on the page loads, otherwise you’d never realize that your page load time results in lost visitors. But if a user exits a page or clicks away very quickly that visit doesn’t really count. It would be like Nielsen tracking every channel I skip when I surf TV using the channel up button.
I also simply can not believe it when a tracking company claims that their code will not be guaranteed to work if placed in the <head> of the document or if the code is wrapped inside a generic tracking function. If your code can’t be wrapped or placed in the <head> what did you do wrong in the first place, or what kind of tricks are you trying to pull? I don’t like to always use the exact code provided by these companies when working on a client website. Your client’s needs for analytics may result in them changing tracking companies and then the developer would be forced to make widespread changes across a site to deal with such change. Granted this type of change is not all that frequent, but it does happen and being prepared is far easier than redoing work.
I’m also not convinced that the analytics provided by many companies is accurate enough. I’ve seen on many occasions that raw stats provide disparaging numbers when put against 3rd party companies and even between multiple 3rd party tracking companies when used together on the same page. When the numbers of hits you receive on your site is the means for convincing ad placement or other financing I think that accuracy is quite important.
The Livescribe Pulse smartpen gets an app store. This little pen is quite amazing, and it just shows that the business model of an app store is already changing the market for every type of electronic device. So when does my…
The Ghostwire (DSiWare) game looks great and reminds me a lot of Fatal Frame.
FloorPlanner is an interesting bit of software built in Flash that allows you design your home in 2D and view in 3D.
The new Stargate Universe [Philosphocal] teaser looks awesome. I stopped watching Atlantis a bit ago because it got boring, I hope this pumps up the energy as BSG did. It has Lou Diamond Philips and Ming-Na in it, that could make…
Here’s a plethora of well designed RSS Feed icons for free!
One Response for "Tracking Invalid Hits: Accuracy is Quite Important"
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..