Using _setVar? Here's an update on bounce rate and time on page
Thursday, January 29, 2009 | 12:06 PM
Labels: Advanced Topics, Code and Configuration
In the past we've received a lot of feedback from our users who have implemented the _setVar method requesting that custom visitor segments not affect bounce rates. You've asked for it and we've listened! Today we're modifying this feature so that the _setVar method no longer counts as an interaction hit with the result that you may see higher bounce rates and more accurate time on page metrics in your reports.
As a refresher, Google Analytics calculates bounces and durations based upon interaction hits. Now, interaction hits will only include pageviews, events, transactions and experiments (such as with Google Website Optimizer). Here's more on how this change to the _setVar method could affect your data:
Higher bounce rates in your reports
Let's say that you've used the _setVar method on your landing pages to segment member vs. non-member site visitors. Previously, if a visitor came to your site and triggered the _setVar call, but viewed only one page, this would not be counted as a bounce. With this change the user defined call will not send an interaction hit and overall bounce rates will increase as this single page visit will now be counted as a bounce.
More accurate time on page metrics
Time on page metrics are normally counted by the difference in time stamps which are set by interaction hits. Prior to this change, using _setVar would cause Google Analytics to calculate the time on page metric between the time of the pageview hit and the interaction hit of the user defined variable. Now, as user-defined hits are no longer counted as an interaction hit, time on page metrics should more accurately reflect the time between one pageview and the next.


16 comments:
Stefano Pochet said...
Is there any connection with my recent answer in this post:
http://www.google.com/support/forum/p/Google+Analytics/thread?tid=6f03f6ce52cb9864&hl=en? :)
Congratulations, this kind of features really makes your users happy!
4:35 PM
Stefano said...
4:17 PM
economist said...
Does this now track data in the same session as the variable was set, or does a delay still exist from visit to visit?
5:16 PM
Julien said...
Thank you, glad to hear our voices were heard at the last GAAC summit! :-)
3:16 AM
John Henson said...
"Now, interaction hits will only include pageviews, events, transactions and experiments (such as with Google Website Optimizer)."
Just to clarify, GWO hits are really just pageviews to a different UA-xxxxx-y number. Since GWO experiments would send their hits to a different UA-xxxxx-y number than your GA code, those GWO hits would not normally have any impact on the bounce rate in your GA account, correct?
6:41 AM
Bill Chiam said...
I just installed the analytics code into my website yesterday and get a close look at the features, it is truely awesome!
I hearby would like to congrats the google team and appreciate them for the great effort.
If there is a feature to allow us to track which page the visitor browser browse based on specific keyword, it would be nice.
My one cent worth. :)
God Bless,
Bill Chiam
12:17 PM
Andrew Laffoon said...
Glad to see this fixed guys! I found out about this bug, reported it to you, and fixed it on our site (Mixbook) only two days before you fixed it yourself!
You guys truly rock!
Andrew
10:08 PM
Ole Laursen said...
When are you going to roll this out? As far as I can tell, the _setVar call is still causing an extra gif request.
The thing is that on my site I keep track of people's status in Javascript (with a cookie). So ideally I would like to call _setVar with the current status just before the _trackPageview on each page. If I understand what you're saying correctly, with the change you've announced, this should be fine.
However, with Firebug I can see that the browser is sending two gif requests?
2:10 AM
John Henson said...
Ole,
The call to _setVar will continue to create the gif request. However, that gif request will not be considered am "Interaction" hit by Google Analytics any longer.
Hope that answers your question,
John
6:39 AM
Ole Laursen said...
John: That's good to know. I guess this is needed to preserve backwards compatibility.
However, in the interest of avoiding an unnecessary gif request, are there any plans to extend the API with a _setVar that just updates the cookies without sending a gif request immediately? It could be as simple as adding a dontSendRequest parameter to _setVar that we could set to true (it would then be null and thus false as default for backwards compatibility).
2:07 AM
Danielle said...
On one account, we use setVar, and have not seen an increase in the number of bounces (6.3% of almost 14 million hits.) However, Visitor Loyalty- > Depth of Visit - > 1 page lists a 29.5% rate.
On another high-volume account which didn't use setVar, these numbers were the same. It seems to me like bounce reporting with setVar is still way off. Anyone else experiencing this?
1:16 PM
Ole Laursen said...
Yes, from the minute we started using setVar, bounce rate fell, and it hasn't gone up again. I believe they didn't fix it at all.
I simply don't get why they don't introduce a setVar-like thing that doesn't contact Google but just sets one of the cookies.
3:19 AM
Mike Dierken said...
"don't get why they don't introduce a setVar-like thing that doesn't contact Google but just sets one of the cookies."
When javascript sets a cookie, it can only set it for the domain of the web page - which isn't google.com, so that cookie would never be sent on later pageviews.
There has to be an extra request out to google.com in order for their cookie to be set.
12:02 PM
Craig said...
We implemented _setVar on our site on 3/17/09 and we also saw a significant drop in the bounce rate. Is there something special that needs to be need to have this fix take place?
2:36 PM
SEO Alchemist said...
Does it still delete session cookies meaning that the referral source is lost, and if not are there plans to fix that too? There are loads of posts about this problem in the forums.
12:36 AM
Marc Baron said...
Did this fix take a while to be implemented? We saw a huge drop in bounce rate when we introduced the _setVar to our site in March 2009 but it returned to normal levels in late April 2009 without any changes on our part.
2:56 PM
Post a Comment