Archive for the ‘Web Analytics’ Category
Click here to register, and sign-up.
I’m quite excited to meet other web analytics folks. I’m really looking forward to this one.
I realised that, with increasing use of Omniture for a client, I keep having to trawl the web and forums and email groups for questions about Omniture. This is compounded by the fact that the client doesn’t give me admin access, and I’ve had no formal Omniture training. It’s too costly, and I’ve found it hellish to find an Omniture help file which is useful in a hurry.
I need to put all the useful tips in one place now. That place is here.
We’re going to put up a promo website outside the client’s domain, and I was wondering what we have to do to use the normal tracking codes. I found this, which was the perfect answer:
If you have multiple domains or add your tracking code to third-party sites that do some of your hosting (such as for a promotional campaign, fundraiser or contest), make sure to specify these domains as internal within the Admin tab under Edit/General/Internal. If not, supposedly you’ll have some page names show up as “other” in the reports–in which case you’ll have to call Omniture to find out what those pages are. However, I had a case where I hadn’t identified a third party as an internal domain, yet the data came through fine; the senior implementation consultant who came to the class couldn’t explain this. Nevertheless, I’ll set the internal domains going forward.
Thank you Church Mojo.
Here’s a quick look at two of the tools to check websites for analytics code implementation.
The Web Analytics Solution Provider was built by Immeria and is probably the best tool out there for auditing a website’s analytics code implementation. It provides a whole bunch of solutions, and I’m told that the purchased version is quite powerful – I presently use the Firefox plugin, and it’s most satisfactory. The only drawback is if you’re a non-Firefox user.
It’s a useful free tool to scan an entire website for tracking code implementation – which makes it a very useful starting point for all kinds of exercises. I’ve commisioned a sample scan for one of the non-profit websites which I help pro-bono, and expect a report soon. I’ll post again if there’s anything awry with the report.
A very simple plugin that I use on my Firefox which just simply tells you what cookies are being used – it’s not exactly a web analytics tool, but is a useful tool to keep an eye on how websites are tracking you – something one needs to continously do, as a professional.
Bounce Rate is among the most used web analytics terms around, ever since Avinash Kaushik made it the metric to look at for page abandonment. I agree – it’s definitely an important metric, especially if you’re spending time and money on driving traffic to your website.
There is some discussion on how Site Catalyst can be used to create a bounce rate metric. Here, and here. However, both explanations are too simplistic. If my campaign is a good one, I’ll often attract visitors who only need to look at a single page for what they want to know, and leave (assume that nothing is clicked upon). The concept of using Single Page Access / Entries will count such an instance as a ‘bounce’.
Some may argue that this is a rare occurence – I don’t think so. It’s a common enough occurence, especially if you have certain information-laden pages which work well to attract a well-targeted audience. Ideally, there should be a way to filter the instances of Single Page Access AND less than 5 seconds spent (If I remember correctly, Avinash recommends 5 seconds in his book).
I’m yet to find a good solution to this quandary.
I intend to review a bunch of web analytics tools as I go along.
Today, a look at Crazy Egg, one of those really exciting tools which is no more free (but definitely worth it if you don’t mind shelling out $9 a month).
For a while, Crazy Egg was the closest you get to a free tool that can give the kind of insights that Omniture’s ClickMap gives. They’re not exactly the same tool, but are very useful when working with a designer to redesign or re-layout a page. The do both a heatmap and the click-overlay thing. However, if you’re using a free tool and not Omniture, the fee might be worth your while – at least for your more important pages since there are slabs by number of pages tracked. And the tool called Confetti works like a segmentation add-in.
Some of the strong features which it brings to the table include the ability to show where folks have clicked (even if they aren’t links). I haven’t tried it out on a live implementation yet, but the demos look interesting. I’m definitely going to keep this in mind for future implementations.
I learnt today, that when Google Analytics calculates Average Time on Page, it excludes bounces (0 second page views) from the calculation. However, when it calculates Average Time on Site, it does not exclude bounces.
This might seem like a trivial point, but is important in certain cases. Usually, when the website is having far more bounces on particular pages, than on others, these metrics might give different results for the high-bounce pages.
Just making a note of it, that’s all.