Google Analytics change to setVar to affect bounce rate and time on page

Google announced on Tuesday that as of Wednesday January 27th calls to the setVar method (used to create custom segments on your site) will no longer be counted as an interaction hit.  

What is an interaction hit?

Prior to January 27th, a call to setVar would be logged as an interaction hit meaning that if it followed a call to trackPageView, the bounce rate for that page would be 0% and the time on page would be tiny, reflecting the difference between the first call and the second call.

This change is a positive move since bounce rate has long been considered a critical measure of success of marketing campaigns from all sources.  If you drive someone to a page and they leave immediately it is called a bounce and indicates that the messaging used to lure them to your site conflicts with what they were able to see when they arrived on your site (in the 8 seconds they typically spend on a given page).  Similarly if your time on page was underreported you might mistakenly waste time optimizing a problem that doesn't exist.

Who does this affect?

A significant number of people who use Google Analytics "out of the box" won't be affected by this change as setVar is only something you implement as a conscious decision to group visitors into custom segments.  If in doubt, right click on a page on your site and click view source then look for setVar in the code (Control+F will pull up a search dialog).

Why use segmentation?

You might choose to group landing pages into custom segments so you can compare the effect of landing pages on visitor behaviour.  Another common application is to use segments to label a visitor by their perceived intent.  

I might track visitors landing on my site into segments based on source to differentiate the behaviour of visitors from social networking sites from that of other referral sources.  

Why?  The custom segments extend beyond the first visit and will only be changed if the visitor receives a subsequent segment, since the last referal before a sale is commonly accepted as the key influencer.  That said, if social networking sites deliver a lot of traffic but convert poorly into sales, I can see that trend across the larger group rather than look at myspace, facebook and twitter separately.  Similarly, the bounce rate and browsing habits might be very different so I would want to isolate this behavior from paid search to make sure I'm not optimizing to a biassed crowd.

Alternatives to setVar

Google recently launched a beta program for "Advanced Segments" located in the top right of the dashboard.  It allows you to pick from pre-defined segments and create your own.  It is a subset of the functionality provided by custom segments since it only tracks visits, not visitors, but is still incredibly useful.  

For example, you can compare behaviour on the site between browsers.  Looking for patterns here like drastically higher bounce rates could mean that your site renders poorly in one browser or actually appears broken to visitors for that browser.  

I have two segments I created to identify visitors who started on my blog and another to track visitors who began their visit on my home page.  Believe me, the insight this provides may help you divert the CEO's demands to put every new toy on the home page...

I encourage you to play with the advanced segments feature, create some segments and compare behavior against the site and other similar but distinct segments to look for trends.  If you need help with this tool, of course you can contact me through the contact form on the site or leave me a question in the comments.

Comments (Comment Moderation is enabled. Your comment will not appear until approved.)
Ken Klispie's Gravatar Adam,

Thanks for the update on setVar(). I just implemented for a client believing it would not affect bounce rate and according to the implementation documentation it should not. However I have data that shows hundreds of visits with a average page views per visit of 1.3-1.8, average time on site of 0:75 to 1:65 and a bounce rate of 3-9%. So... leaves me wondering. The only other pieces in line are:

var pageTracker = _gat._getTracker("UA-xxxxxx9-1");
pageTracker._setCampContentKey("contentid");
pageTracker._setCampMediumKey("channelid");
pageTracker._setCampNameKey("eadid");
pageTracker._setCampNOKey("overrideid");
pageTracker._setCampSourceKey("sourceid");
pageTracker._setCookieTimeout("63072000");
pageTracker._setDomainName(".clientdomaniname.com");
pageTracker._setSampleRate("100");

then the trackPageview() ... anyone else ever experience this (post change) ...?

Thanks -K
# Posted By Ken Klispie | 3/26/09 8:38 PM
Alexcaid's Gravatar The problem is that setVar still counts like a visit. If you create a profil and apply a filter to inclde only a folder like "^/folder/", you will end up with pageviews stats limited to /folder/ content, but visits and unique visitors information will reflect the stats of your entiry webiste.

I can't understand what GA is behaving like that and why Google is not correcting this problem.
# Posted By Alexcaid | 5/11/09 2:18 PM
Keith's Gravatar Hi, I noticed a drastic drop on my bounce rate (from 70+ to 1.5-) within a couple of days, but not much difference on the time on site. I've read several replies to comments like this saying that the SetVat was to blame. I've ready your explanation and searched on my site for it and it's not there. Do you know of any other possible reason for the bounce rate to drop so dramatically?
# Posted By Keith | 10/20/09 1:41 PM
Adam Howitt's Gravatar Hi Keith - I just blogged about this topic and how to troubleshoot a drastic drop in bounce rate: http://www.adamhowitt.com/blog/index.cfm/2010/1/23.... Could be some AJAX code on your page or other technical issues. See the blog post for more.
# Posted By Adam Howitt | 1/26/10 2:48 PM