Expand my Community achievements bar.

Applications for the 2024-2025 Adobe Analytics Champion Program are open!
SOLVED

Why total seconds spent metrics is different from month wise report and Analytics ID report ?

Avatar

Level 2

Hi,

 

By using total seconds spent metrics data is showing different for month wise report and Analytics ID report. 

 

Attached the screenshot,

Tulassi_0-1695294960282.png

 

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Because in order for any dimension to show against a visit, there must be a minimum of one hit in that visit.

 

Let's look at a few simple examples:

 

Scenario 1 (v94 is a "Visit Level" expiry)

  • Page 1
    • eVar94 is not set
  • Page 2
    • eVar94 is set to "1234"
  • Page 3
    • eVar94 is set to "1234" (overwriting the expiry attribution with the same value)
  • Action 4
    • eVar94 is not set, but maintains value "1234" due to Visit Expiry

The first page view was missing a value, but within the visit, eVar94 was set, therefore Visit is counted

 

 

Scenario 2 (v94 is a "Hit Level" expiry)

  • Page 1
    • eVar94 is not set
  • Page 2
    • eVar94 is set to "1234"
  • Page 3
    • eVar94 is set to "1234"
  • Action 4
    • eVar94 is not set

The first page view and the Action 4 are both missing a value, but within the visit, eVar94 was set, therefore Visit is counted

 

 

The only way that you could have an overall visit (your first image) have more visits then when looking at eVar94 against visits, would be if every hit in the visit was missing a value.

 

Scenario 3

  • Page 1
    • eVar94 not set
  • Page 2
    • eVar94 not set
  • Action 3 
    • eVar94 not set

 

View solution in original post

5 Replies

Avatar

Community Advisor

It looks like Analytics ID (v94) isn't available on all hits, therefore the Time Spent metric will be limited to only the hits with that dimension.

Avatar

Level 2

Hi Jennifer,

 

Thank you for answering my question.

 

I have another few queries that is why visits (metric) is showing same for all the dimensions.

 

Thanks,

Tulassi

Avatar

Level 2

Hi,

 

Please refer the screenshot for visits.

 

Tulassi_0-1695376280363.png

I have used the different dimension but visits metrics is showing same date for all dimensions.

 

Avatar

Correct answer by
Community Advisor

Because in order for any dimension to show against a visit, there must be a minimum of one hit in that visit.

 

Let's look at a few simple examples:

 

Scenario 1 (v94 is a "Visit Level" expiry)

  • Page 1
    • eVar94 is not set
  • Page 2
    • eVar94 is set to "1234"
  • Page 3
    • eVar94 is set to "1234" (overwriting the expiry attribution with the same value)
  • Action 4
    • eVar94 is not set, but maintains value "1234" due to Visit Expiry

The first page view was missing a value, but within the visit, eVar94 was set, therefore Visit is counted

 

 

Scenario 2 (v94 is a "Hit Level" expiry)

  • Page 1
    • eVar94 is not set
  • Page 2
    • eVar94 is set to "1234"
  • Page 3
    • eVar94 is set to "1234"
  • Action 4
    • eVar94 is not set

The first page view and the Action 4 are both missing a value, but within the visit, eVar94 was set, therefore Visit is counted

 

 

The only way that you could have an overall visit (your first image) have more visits then when looking at eVar94 against visits, would be if every hit in the visit was missing a value.

 

Scenario 3

  • Page 1
    • eVar94 not set
  • Page 2
    • eVar94 not set
  • Action 3 
    • eVar94 not set

 

Avatar

Level 4

Do you have "unspecified" or "Low Traffic" filtered out?  Might be that is what is making the delta.  Low Traffic will often happen for ID based dimensions if you go over the 500K monthly limit.  

 

Another thing to look out for is your dat range selection vs your dimensional month items in your table.  See the attached image: 

 

Damonwhall_0-1695333427739.png