The “adjusted bounce rate” mechanism is 15 seconds (it’s not a variable setting right now). Although I suppose it would be easy enough to make it one…
Thanks for your quick reply! It would be great if you could set the time yourself, since what you consider a “not-bounce” is relative. This blog post made sense to me: Adjusting Bounce Rate in Google & Universal Analytics
Is it possible to implement this yourself without messing things up with the plugin?
The code example in the above-mentioned blog post and also this, How To Track Adjusted Bounce Rate, inserts the code for the adjusted bounce rate just AFTER “ga(‘send’, ‘pageview’);”
In the advance settings of Better Google Analytics, there is an input box for extra JavaScript. However, the info says the extra code will inserted just BEFORE “ga(‘send’, ‘pageview’);” Does it matter?
It’s minified, but if you look in the better-analytics/js/ba.js file and find this:
setTimeout("ga('send','event','User','Engagement','Time on page more than 15 seconds')",15E3);
The 15E3 at the end means 15 seconds (well technically it means 15000 ms).
So say for example you wanted it to be 30 seconds, you could make it this:
setTimeout("ga('send','event','User','Engagement','Time on page more than 30 seconds')",30E3);
Either way, it will be a setting in 1.1.2 on the Advanced tab.
In the case of setTimeout firing, it really doesn’t matter if it’s before or after the pageview trigger… all you are doing is telling the JS to do something xxxxx ms in the future from that point. It doesn’t interact with or affect the pageview trigger.
Thanks! To make things clear:
If I change the ‘better-analytics/js/ba.js’-file, I guess it will be overwritten when the plugin is updated next time? The best solution would be to insert the code in the box for extra JavaScript?
Yes, it would be overwritten with the next update… but like I said, the next update will also have the option under the Advanced tab, so…
