Average Time Spent on Site breakdown difference

Question

Hi there!I feel extremely confused questioning the documentation, but can somebody explain why 1m 40 sec is not taken into consideration for site section calculation?Next piece of question relates to why I was reading this part of article again and again: we had built following tableSo, I'm struggling to explain why in this case average time spent on Site for the segment is 106 and for Pages dimension is 141?I imagine that to get lower number there should be more unbroken sequences of pages with /library/stories, right? But how it can be, that there are more unbroken sequences of the segment, than unbroken sequences of the pages it contains? Thank you in advance.

Jennifer_Dungan · Accepted Answer

Ah.. but here, stacking the metric with your segment results in the 141 second average, which matches with one of the values on your first screen shot (the deeper one).

I would assume that the 106 from the original screenshot wasn't properly averaging the individual pages, possibly due to some of those pages being concurrent, so the divisor was different...

At least in the stacked version, you won't see two different values that you have to explain why they don't match.

Now, there is a slight difference between the filtered pages vs the segment pages (144 to 141), I assume there may be a slight difference in what is being pulled back in the two columns.... but it's a lot closer than 106 and 144 (if that makes you feel better?)

Jennifer_Dungan · Answer

To be honest, I think that documentation has an issue... I would think in the second scenario, where the breakdown is by Site Section, I think because of the consecutive "foxes" values, it would look at the initial start time and end time of when "foxes" was sent, so 140/1 = average of 140 seconds (or 2m 20s).... OR it would look at each hit of "foxes" so (30 + 100 + 10)/3 = 46.67 seconds. I would expect the second scenario, treating each hit independently.

I don't use Adobe's time spent too much, we have another system that does a heartbeat tracking so we normally defer to that over Adobe's. But like you, that documentation indicating that 1m 40s is missing doesn't make sense....

Now, for your specific issue, being a calculated metric you can get some odd behaviours sometimes, I've also found a lot more issues when I add metrics into the breakdown area...

Can you do a test? Can you stack your metric and segment in the column, then just have your pages as the breakdown?

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded