Time Spent per Visits(seconds) | Community
Skip to main content
Level 2
Jul 26, 2021 6:15 AM UTC
Solved

Time Spent per Visits(seconds)

Hi.

 

According to the instruction of AA help(https://experienceleague.adobe.com/docs/analytics/components/metrics/time-spent-per-visit.html?lang=en), 

the formula for Time Spent per Visits(seconds) metric should be <Total seconds spent / (visits - bounces)>. 

 

However, I am getting some different results in my workspace. 

 

 

61,190,025 /(309,071 - 121,858) should be 327. But, as you can see, the number of 'Time Spent per Visit (seconds)' is 332. 

 

Why does it show a different result? 

Is there any exception for this metric? 

 

Thanks.

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
vidurb80577666Accepted solution
Employee
Jul 26, 2021 8:44 PM UTC

The reason there is a difference is because in Time Spent per Visits(seconds) calculation, not all visits are counted - only those that have the timespent seconds on page attribute set. This is not exactly the same as visits - bounces. For many visits, there could be no timespent set, and therefore they are not included in the avg timespent calculation. This ends up with fewer of the visits being counted than just subtracting the bounces, leading to a smaller denominator and therefore a larger calculated number.

 

It should be possible to create a segment that is "visits that have timespent seconds set (great than zero)", which would allow you to get the same number to use as your divisor that we are.

3 replies

vidurb80577666Accepted solution
Employee
Jul 26, 2021 8:44 PM UTC

The reason there is a difference is because in Time Spent per Visits(seconds) calculation, not all visits are counted - only those that have the timespent seconds on page attribute set. This is not exactly the same as visits - bounces. For many visits, there could be no timespent set, and therefore they are not included in the avg timespent calculation. This ends up with fewer of the visits being counted than just subtracting the bounces, leading to a smaller denominator and therefore a larger calculated number.

 

It should be possible to create a segment that is "visits that have timespent seconds set (great than zero)", which would allow you to get the same number to use as your divisor that we are.

Translate
zoe_kimAuthor
Level 2
Jul 27, 2021 1:28 AM UTC
Thank you very much!
Translate
Level 7
Jul 26, 2021 7:32 AM UTC

@zoe_kim  It is not recommended to compare the manually calculated metric value with the given in workspace as there are some other factors involved as well in the algorithm after which the value in computed in the workspace.

Translate