This method of measuring Bounce Rate is not always best. For a blog, I like it because many people will land on the homepage, and read multiple posts, but Google Analytics only sees one page viewed, and counts it as a bounce, even when they looked at multiple posts. For another type of website, the single page viewed is a valid measurement for bounce rate.

If you already have segmented out Bounces, then you won’t see any data if you implement this custom segment. Also, you are correct in that the bounce measurement will have changed so you will no longer be “comparing apples to apples.”

Ben

MY method of excluding bounced visits from a segment may have to change. it is currently “Bounces Equal to 0″ – which I don’t necessarily trust, but seems to work.

Once this code is loaded, it starts a timer, and once it reaches 10 seconds, it creates an event (pageTracker._trackEvent). If the timer is not reached (due to a visitor leaving the site), then it is a bounce.

Because of the event that is being created and tracked, I don’t need the second page anymore to set the time on site.

Ben

If the intent of changing the bounce calculation from a singe page view to visits less than 10 seconds, how does that help in the case of a single page view? Time on a page is the time between hitting page 1 and hitting page 2. If there is no page 2, then time on page (and time on site) is zero. Let me know if I’m missing something.