Stephan Spencer's Scatterings

The Scattered Wisdom of a scientist turned web marketing virtuoso

July 2008
S M T W T F S
 << <   > >>
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30 31    

Coolest new web analytics tool you've never heard of

One of the 5-minute "lightning round" sessions at Web 2.0 Expo on Sunday night was the folks from Nitobi demoing their brand new Robot Replay technology. All I have to say is... WOW!! Every one of you readers HAVE to go check this tool out. It is a free beta, so there is no excuse for not trying it out! Robot Replay allows you to track the mouse gestures of your visitors and play them back. Imagine tracking individual prospects and see how they are interacting with your site! Not just where they click, but whether they scroll, how they interact with your forms, etc.

Posted by Stephan Spencer on 04/19/2007 | Permalink

Comments (2)| Comments RSS | Filed under: Web Analytics tracking, web metrics            

The Problem with Embedding Tracking Codes in your URLs

The problem with embedding a tracking code into URLs to track referrals from particular marketing campaigns or from particular partners is that inevitably those URLs end up in other places, such as in the search engines. Thus your referral numbers become overinflated.

Case in point: Google's "Inside AdSense" Blog. A couple days ago I searched Google for [inside adsense] and was surprised to find that the #1 result was not http://adsense.blogspot.com. It was the URL with a utm_source and some other stuff appended at the end of the URL (i.e. the URL was something like http://adsense.blogspot.com/? utm_source=aso&utm_campaign=ww-en_US-et-asfe&medium=et). Unfortunately I didn't record the exact URL at the time, and today Google is back to returning what it should be returning for the top result: http://adsense.blogspot.com (without any utm_source or query string). I bet the Analytics folks at Google will be scratching their heads at the spike in popularity of the "ASO" (or whatever it was) referral source when they look back at the month of May (unless of course they've read this blog post!).

Example #2: CBS News. Check this out... Run the query [site:www.cbsnews.com inurl:source=rss] on Google. Google returns 27,900 pages. You'll see that all of those pages have a source=RSS in the URL. Even though I don't believe Google's numbers of results to be even remotely accurate, still there are a heck of a lot of pages there, and those pages are bringing in some amount of traffic from Google searchers. When they do, the referral source is being wrongly attributed to the site's RSS feed. I wonder if CBS News realize this? Probably not.

So, if you must use the URL's query string to track your referral sources, then at least make sure that you aren't ever serving those links to search engine spiders. Drop the referral source from all links when spiders come to visit. Don't worry; the search engines say this sort of "cloaking" is totally okay.

That will ensure your own site isn't providing source coded links for the spiders to explore. But what to do about other sites that are linking to you? I suggest that you 301 redirect all traffic to URLs with tracking codes to the corresponding URL without the tracking code. You should see that your source coded pages in the search engines' indices should drop away to nothing over time (or at least get relegated to "supplemental hell").

Posted by Stephan Spencer on 05/08/2006 | Permalink

Comments (3)| Comments RSS | Filed under: Search Engines, Web Analytics google, tracking codes, urls, web metrics, web stats