Expand my Community achievements bar.

Announcement: Calling all learners and mentors! Applications are now open for the Adobe Analytics 2024 Mentorship Program! Come learn from the best to prepare for an official certification in Adobe Analytics.

Bring Back Time Spent Per Visit for total site

Avatar

Level 10

2/12/10

In 13.5 the Time Spent Per Visit report listed the average time spent in the total in addition to broken out by the various time buckets. This disappeared in 14. Currently the only way to get this is via the ExcelClient

time_spent_14.pngtime_spent_14.png

12 Comments

Avatar

Level 1

2/12/10

Instead of using the ExcelClient:

 

1. Go to an existing dashboard

2. Click Add Custom Reportlet

3. Select Content Metric = Average Time Spent On Site

Avatar

Level 1

2/16/10

I miss this. I have to use dashboards or ExcelClient datablocks for it now. I'd also like to see it as an option in DataWarehouse. 

Avatar

Level 2

3/18/10

There's actually a way to get this in Omniture Suite.


Site Metrics > Page Views.

Scroll down to the bottom.

Under Related Reports - Time Spent per Visit. 

 

Not sure how this report varies from the "regular" Time Spent per Visit, but the actual average number appears.  Would be nice if this appeared on all the Time Spent per Visit reports.

Avatar

Level 2

4/8/10

Whilst you can get to average time spent  by the ways mentioned above,  you can't actually get a trended report for average time spent per visit (only  top 5 or selected 5 time ranges) so you cant show  he trend in dashboards at all.

 

This would be useful, even though time spent is not really true ( given time spent on last page of a visit can't actually be measured)

Avatar

Level 1

11/19/10

@ericmatisoff - Visits (Report Specific) metric doesn't appear to help matters, there's still no site average, just the breakdown (reporting the number of visits per time segment).

 

@tkochersperger - We've just seen release of SC v14.9 and the site average appears to be still available through the method WJungHearst suggests above.

 

Since they're obviously calculating this anyway, it would be nice to have it available as a regular report.