Measuring and analyzing web services (in Finnish)

I’ve just blogged about setting goals to web services, measuring and analyzing them (sorry folks, in Finnish only). The blog post can be found from my company’s blog:

5 yksinkertaista askelta – tavoitteiden mittaaminen verkkopalveluiden kehityksessä.

 

Advertisements

Passed Google Analytics Individual Qualification (IQ) test

Dear Reader,

Google Analytics IQ test, Rami Karhu

Google Analytics IQ test

I’m congratulating myself for having just passed the Google Analytics Individual Qualification test. I thought the test was almost easy in the end although my score was (only?) 86% right (75% correct answers needed to pass). Most of the questions were not very hard and even though there were 70 questions in all, I had answered them in approximately 30 minutes not counting a couple of marked questions that I reviewed after completing the rest. The test has a 90 minute time limit.

The video tutorials on the Conversion University Help page were really helpful and most questions were actually almost directly taken from the video material. The test has been available from the beginning of March 2009 and I’m now the 819th to be certified.

Web Strategy 1: Web Analytics

Dear reader,

I thought I’d start an irregularly written series of postings dealing with various aspects of web strategy. This first blog post handles with web analytics – a subject that absolutely no-one in the field of web can bypass. Here goes.

Web Analytics

Analytics in the realm of web generally answers to the need: “We want to know what our visitors are doing in our web services”. It measures the visitors online behaviour and seeks to enable a company’s web team to make educated guesses on the analytics reports, and thus improve the service, drive new leads in, analyze and improve Return on Investment (ROI), etc.

There exists an expression “half of the marketing budget is wasted, but we don’t know which half”, which is not entirely true anymore when it comes to web marketing. Web analytics makes the gathering of information and success rate possible based on a company’s set needs and goals.

With most analytics tools it is possible to apply or define filters (e.g. one might want to filter out their own company’s visitors from the general visitor metrics) and goals (“I want to know how many visitors came from Google and ended up buying our product”). With most tools it is also possible to investigate visitors’ navigation paths in a visualized manner. Other information of interest include e.g. the visitors browser and platform information, screen resolution, company name (can be sought by ip number), etc. Some of the analytics applications are more information rich than others – the tool to use should always be decided after defining the metrics and process.

A good analytics solution gathers information on different aspects of the visit, including:

  • Content analysis
    • Top Content
    • Enter page, Exit page
  • Visitor / Visit analysis
    • Path analysis
    • New visitors
    • Returning  visitors
    • Read pages per visit
    • Duration of visit
  • Traffic (source) analysis
    • Search engines
    • Directories
    • Keywords
    • Links
    • Direct
  • Technical analysis
    • Browsers
    • Platforms
    • Screen resolution, etc

Other good traits in an analytics solution are:

  • Customizable dashboards
  • Automatic and customizable reports e.g. by e-mail
  • Export to different formats (pdf, XML, Excel)
  • Integration to Customer Relationship Management software (CRM)
  • Integration to marketing tools such as Google AdWords
  • Lightweight user rights management (eventually you’ll want others to just see the reports but not mess up the dashboards, for example)
  • Visually pleasing and accurate graphs, pies, etc.
  • Comparison to history data
  • Benchmarking or anonymous comparison between similar sites
  • Realtime monitoring
  • Fast reports
  • User friendly GUI

How ever feature rich the application is, bear in mind that you should only acquire an analytics application that suits your  business needs, matches with your budget and so on. If there are no inhouse resources or know-how (as often is the case) I heartily suggest using a professional consultant company to help define the needs and processes for your business.

The definition phase

Before buying any analytics software, one should always first define: 

  • Key Performance Indicators (KPIs) to be followed (i.e. the needs of information to be followed continuously)
  • The process of what happens when a certain metric’s set threshold is exceeded
  • Who does what when a certain metric is succeeded (i.e. who ‘owns’ each metric)
  • Whether to use log based or page tagging analytics software, or both

Different analytics solutions

The main difference between analytics applications is how they actually measure the visits and hits. There are log based analytics tools (often called log analyzers or log parsing tools) and tag based tools (often called page tagging tools).

Most experts think that the most accurate results can be achieved by utilizing best of both. This of course requires careful definition, know-how and resources. Some of the analytics applications are able to utilize both tags and logs. The essential differences between these two measuring methods are:

Log analyzers

Log analyzers, as their name suggests, create their reports from web server logs. This means that:

  • Search engine spiders or crawlers get logged as well (unless delibe-rately filtered out of the results)
  • It is a bit more easy to measure downloaded files
  • In a multi-server farm, there are multiple log files that the solution should be able to combine
  • If acquiring a log based solution, one already has the history data as-suming old web server log files are available
  • Log analyzers cannot be seen e.g. by competitors from page source (as opposed to page tagging)

Page tagging solutions

Page tagging analytics software are inherently different from log analyzers. Some of the features of page tagging are:

  • One has to embed a couple of rows of JavaScript in the end of each page (the tag itself)
  • Page tagging analysis reports are usually read from the vendors web service (e.g. Google Analytics). This might be a showstopper for some security aware (or phobic) companies
  • Page tagging is often used in conjunction with cookies, meaning that it will provide more accurate results and can, to some extent, recognize old visitors more easily
  • If a visitor has blocked JavaScript and / or cookies, their visit will not be logged by the analytics software
  • The same can apply if the user exits the page without letting it load completely, because the JavaScript tag is usually put at the bottom of the source code (just before the closing </body> tag)
  • Page tagging is currently thought to be more accurate measuring method by most experts

There are numerous web analytics software out there ranging from free of charge to pricy applications and from log parsing analyzers to page tagging software (see differences above). Some of the most prominent web analytics solutions are:

%d bloggers like this: