Archive for the ‘More Traffic’ Category

Analytics Tuesday – Cookies

Last Tuesday, in the first in this series of posts, I looked at some of the main reasons for gathering metrics from your site. This week, I want to start covering some of the key terms you’ll come across in discussions of metrics.

I’m going to start with ‘cookies’.
mexican hot chocolate cookies by rachel is coconut&lime

No, not those sorts of cookies.

Cookies are probably not the first thing you think of when you think about capturing metrics from your site. You may not think about cookies at all, in fact. However, they’re pretty damned important. Here’s why.

Cookies and Page Tags

For the sake of simplicity, I’m going to assume (dangerous, I know) that you’ve plumped for using Google Analytics (GA) as your metrics package of choice. After all, it’s free and the range of data it supplies is probably enough for the great majority of small businesses. Best of all, it uses page tags that you add to each of your site’s pages – so you don’t need access to your server logs – and the data is available to you through your own on-line dashboard at Google.

Page tags work (i.e. gather data) by setting cookies when visitors arrive at your site. Cookies have had a bad press, which, for the most part, is a result of ignorance. After all, a cookie is simply a very small text file (which can always be examined by a user in a normal text editor, or even deleted) that gets associated with your browser when you visit a site.

Then, whenever your browser accesses that site, it takes the cookie with it. It’s a way for a site to recognise repeat visitors or visitors accessing more than one page in the site.

If you use Amazon, for instance, you know that when you use your normal computer, you’ll get the ‘Welcome, Graham’ message (replace ‘Graham’ with your own name!) but when you visit from a different computer, Amazon doesn’t know who you are. That’s the power of cookies.

GA uses only first party anonymous cookies. This is what Google says about its cookies in its help area:

Google Analytics uses cookies to define user sessions, as well as to provide a number of key features in the Google Analytics reports. Google Analytics sets or updates cookies only to collect data required for the reports. Additionally, Google Analytics uses only first-party cookies. This means that all cookies set by Google Analytics for your domain send data only to the servers for your domain. This effectively makes Google Analytics cookies the personal property of your website domain, and the data cannot be altered or retrieved by any service on another domain.

The down side, of course, is that some companies and people prevent cookies being written to their computers. That means you’ll miss some of the data you want to collect. The number will be small, however.

Next week, I’ll look at one of the key areas where cookies come into their own: differentiating between visits and unique visits.

Remember, if you miss one of the Analytics Tuesday posts, you can simply click on the blog topic in the sidebar with that name and you’ll see a list of the posts so far.

Introducing Analytics Tuesday

As part of our new focus on core web tools and tactics for small businesses, we’ve decided that Tuesday will now be known as Analytics Tuesday (not to be confused with Pancake Tuesday here in the UK) on the bpodr blog. Each week, either Adam or I will put up a post about analytics/metrics and some links to places to find more information.

A good place to start is with the decision to install analytics on your site. When we conduct site reviews, we come across a startling number of sites with no means to capture metrics (and just as many where the metrics aren’t collected, even when the means to measure it is installed). So, we’re kicking off this week with a look at why installing a way to capture data on your site is, without question, as important as having a working web site in the first place.

GA2

A site without metrics is a brain without oxygen

Choosing to launch a web site and then do nothing to measure its effectiveness is akin to buying an expensive house without finding out where it is nor caring about its condition.

Of course, measuring effectiveness also implies that there is a clearly defined objective. In other words, you need to know the main purpose of your web site. For most businesses, this will usually come down to one of these:

1. To drive more sales;
2. To generate more qualified leads;
3. To establish credibility.

The first two may appear similar on the face of it but the primary objective for the site itself will depend on whether you’re running a true ecommerce site or a site that seeks to bring prospects into your pipeline.

Let’s say you’ve got a B2B business and your product or service is not something you can pop in the post and send to a customer on receipt of an on-line payment. In this case, your site is probably looking to get visitors to pick up the phone and call you (or request a brochure or fill in a contact form).

Metrics provide the data for your business decisions

A decent metrics package will let you know where your visitors are coming from, what pages they visit on your site, and how long they stay there. With experience – or help from someone familiar with analytics data – you’ll start to see if and why potential customers are failing to answer that call to action on your site. That data alone can form the basis of a marketing strategy for driving more traffic, or improving your landing pages, or even making sure you implement a plan for loading fresh content on a weekly basis.

When you capture data from your site and analyse it properly, you’ll immediately be in a position of competitive advantage. (Whether you do anything with that advantage is up to you, of course, but the chances are that at least one of your competitors will make use of data gleaned from their own site.)

In the early (earlier?) days of the web, much was made of ‘hits’. The web was much simpler then and hits on your site actually meant something. Nowadays, with each web page containing so much information served in separate calls to your server, counting a hit is as much use as counting bricks to decide which house to buy. My favourite quotation about this comes from Jim Sterne ( as quoted in Avinash Kaushik’s excellent book “Web Analytics An Hour A Day”). Jim defines ‘hits’ as “how idiots track success”.

Jim Sterne and Avinash Kaushik both have blogs that focus on web analytics. Browsing the archives on their sites is a great place to start if you want to delve into the subject further (and quicker).

Coming next week….

Alternatively, you can just wait until next week, when I’ll look at some of the key terms used when talking about metrics.

If you miss any of the posts in the series, just click on the ‘Analytics Tuesday’ category for a complete list.

Let us know if there are any metrics topics that you want to see covered. Questions, opinions, gripes, and corrections are also always welcome.