A “better” way to calculate total time spent and bounce for a given value when using Segments

RobertBlakeley

10-05-2013

Total Time Spent and Bounces are not calculated as I would expect when using a Segment.

  • Filtered out calls are not counted when calculating time spent, inflating the time spent for the given value.
  • Filtered our calls are counted when calculating Bounces, deflating the bounces for a given value.

I would like the reverse; filtered pages to be counted for calculating Time Spent and ignored for calculating Bounce. This request is to provide at least the option to count that way.

 

Gritty Detail:

 

Currently, Total Time Spent is calculated on a value from page 1 to page 2, from page 2 to page 3, from page 3 to page 4, etc and added up. (Time on page 6 is not determined).

 

If I do a Segment on prop 1, value a, time spent on page 2 is calculated from page 2 to page 5, not page 2 to page 3. This skews the time spent on the “a” value in the segment.

 

In the example below, if each time spent on each value were 1 second, the Total Time Spent on value “a” in the segment would be 5, not 3 as I would want.

 

In this case, I would rather not have ignored the missing pages in calculating time spent on value.

 

 TimeSpentFlow1.png

 

Bounce is defined as one call in the visit. If I segment on prop1, value a, the Bounce calculation still sees page 2 so the bounce on the Prop1 value is not seen as a bounce.

 

In this case, it makes more sense to me to ignore the filtered out page to show a bounce on prop1, value a. I am more interested in bounces to the value than to the report suite.

 

In the example below, Bounces on value “a” in the segment would be 0, not 1 as I would want.

 

TimieSpentFlow2.png

 

So what I would think would happen is the opposite of what is happening. I would think the filtered pages should be counted for Time Spent and ignored for Bounce.

Comment