Google Analytics Fast Access Warning

[Update: May 10th - This warning originally read "This report is based on sampled data". Google have now explained that the warning appears any time you report on more than one dimension in Analytics on a date range containing more than 500,000 visits. See the Google Analytics Fast Access Mode help page for more detail.]

Everyone loves Google Analytics. It’s free, full of great features, and most of the time it works like a charm. We use GA data regularly in WhatClinic.com to make important decisions about everything from internal linking structures to on page keyword priorities, and it really comes into its own when something on the site is broken and we need to track the problem down.

However, like a lot of great free web services GA suffers from being too popular. The amount of data it has to crunch for our website alone is staggering, so imagine the load when you add in the tens if not hundreds of millions of other websites that use it too. Unfortunately the strain starts to show as soon as you really dig into your data.

The Dreaded Fast Access Mode Message

One of my most used features on GA is the Advanced Segment, which lets me filter the traffic I’m reporting on in a myriad of different ways. I can report on only the people who landed on our search pages, or only the people who came from Canada, or pretty much any set of people with an analytics parameter in common.

Google have a problem with this great feature though: in order to give you an answer to your query in a reasonable length of time they often fall back on using sampled data, or “Fast Access Mode” as they now call it, if you are using a date range that contains over 500,000 visits.

Google Analytics using sampled data

Sampled Data

Using sampled data is absolutely fine when your data points don’t suffer from a lot of volatility, but if they do then the results can be very unreliable. Take a look at the data set above. It uses sampled data because I’ve created an Advanced Segment with two parameters (user location and page URL) and I’m looking at a period of three and a half months which contains far more than 500,000 visits. Analytics is reporting a conversion rate in April of just 2.65% for the set of visitors I’m looking at.

Now look at the data set below. It is reporting a conversion rate in April of 4.36%. The difference is that it isn’t looking at sampled data because the period of time is much shorter and the visitors number is less than 500,000.

Google Analytics not using sampled data

Real Data

Our conversion data can be very volatile in places because of the niche or long tail nature of what we offer and what I need to report on from time to time. For instance. We might get 1,000 enquiries for dental clinics in Dublin in a week, but if I look at just the visitors who were looking for clinics in Rathmines that figure might drop to just 10, and those ten might have been made up of 3 on Monday, none on Tuesday, 1 on Wednesday, and so on. It’s the same when you look at American visitors to our Mexican dentists pages, or UK visitors to our Turkish cosmetic surgery pages.

Be Sure To Perform A Sanity Check

As with the case above, when something looks like a problem we all tend to look into it and see what’s going on, but when something looks good we tend to let it slide. My advice is any time you see the Fast Access Mode message in GA you should sanity check it by using shorter periods of time. This takes a little time but it will give you a far more reliable picture of what’s going on.

When Advanced Segments in Google Analytics were introduced just over a year ago I was delighted. Finally there was an easy way to slice our website data in more than one dimension at a time. By setting up an advanced segment for just “Organic Visitors from the United States” for instance I could really drill down into what a specific set of users were doing on the site and see how their behaviour differed from the norm.

Every now and again though I used to see some strange results come back for reports I was doing. At the start I put this down to the feature being in Beta, but the anomalies didn’t go away. Having come back to use advanced segments in recent days to dig into some very specific user behaviour I noticed the problem was still there so I decided to find out what was causing it.

As an example, when I did a search (filter) in my top content report for all the URLs containing “/dentists/” I got a figure of 313,000 page views for the period of time I was looking at. However, if I swapped out the filter and used an advanced segment I had set up to do the same thing (i.e. only include data for pages that contained “/dentists/” in the URL) I got a figure of 434,000 page views, and I could see pages that clearly didn’t match the segment I thought I had setup.

At this stage the difference was far too big to ignore, and I assumed that lots of other users would be aware of it too. I was right. The Google Analytics help forum was full of questions about why data sliced with filters wasn’t matching data sliced by advanced segments.

The answer came in one line from a guy called MikeOstrowskiASU. He said simply that “Advanced segments are based on visitor sessions.”

Suddenly it was all clear. The advanced segments when used on the top content report were bringing back all the pages visited by anyone who had visited a page with “/dentists/” in the URL during their session rather than just the pages with “/dentists/” in the URL.

Just to confuse matters, advanced segments on visitor reports do match up with filtering because they are based on user sessions. For instance, using an advanced segment for “Visitors from the United Kingdom” on the visitors report will match up with going into the Map Overlay and clicking on the UK.

So, the moral of the story is be careful how you use advanced segments and what you infer from the data you get back. They might not be doing what you think they are.

Have you had a similar problem with Google Analytics, and have you found any workaround for it?

In Google Analytics you can only view 500 rows of results from a query at any time. When you try to export the results of the query, unhelpfully it only exports the results that are on your screen at the time, so if you need more than the 500 results on the screen, you have to page through them and export them by hand one page at a time.

Or so I thought.

A little bit of digging around has revealed that if you add the string &limit=50000 to the end of the URL of the page you are looking at, and then export as CSV or TSV you will get up to 50,000 20,000 records in your downloaded report file. [Update: So many people were using this trick that Google limited the output to 20,000 rows.]

Being able to export large volumes of segmented data is of great value to us here in RevaHealth.com, especially with our focus on long tail SEO. Hopefully this tip will save you some time too.

P.S. If you’re using Analytics and haven’t checked out advanced segments yet, you owe it to yourself to do so. They are the answer to innumerable problems that existed in Analytics reporting up to now.

Tagged with:  
© 2010 WhatClinic.com Blog