Negative Time Values in Adobe Analytics | Adobe Higher Education
Skip to main content
frederikw694537
Level 2
March 4, 2020

Negative Time Values in Adobe Analytics

  • March 4, 2020
  • 2 の返信
  • 12667 ビュー

Hey Guys,

 

I cam across a strange behavior in Analytics. It seems like it is not able to render negative values in time format correctly, at least in Analysis Workspace.

 

To reproduce, I created two calculated metrics, one with a static value of "30" and one with "-30". Then I formatted them both as time. In Workspace, they look like this:

 

Clearly, the negative value is broken. We need this to compare time spent on specific pages with the average, but it does not work right now. The expected result would be "-00:00:30".

 

Best regards,

Frederik

このトピックへの返信は締め切られました。

2 の返信

Andrey_Osadchuk
Level 10
March 4, 2020

Frederik,

 

I wonder what a negative value in the time format means? Could you share a use case?

Pablo_Childe
Community Advisor
Community Advisor
March 4, 2020

I think its a case of creating 3 calculated metrics.

 

1 avg time spent on page per visit

2 overall avg time spent on all pages per visit

3 the difference of 1-2(or vice versa)

 

All are positives except the last one which (could be negative)

 

 

 

Andrey_Osadchuk
Level 10
March 4, 2020

What question does the 3rd metric answer?

frederikw694537
Level 2
March 5, 2020

The 3rd will answer.

 

If articles avg time spent on the specific page is X, then how does it compare to over all average? A positive number means its better than avg, a negative means its lower.

 

I am assuming he is trying to understand relative content engagement. vs site content engagement average.

 

(this is a very simplified way to measure content engagement as it really only looks at 1 metric as the determiner(avg time spent on page))

 

There are more complete methods to create calculated metrics to indicate page level (thereby content level) engagement but as a first pass will be a good lesson.

 

 


Hey @andrey_osadchuk and @pablo_childe,

well explained, @pablo_childe! That is one of the usecases. This is not only limited to the page dimension, but any other dimension as well. For example, we could compare the time spent per visit across device types compared to the average. That way we could easily see, that our mobile users are spending 3 minutes less on our page than the average over all devices. This is also interesting for marketing campaigns or entry page reports.

For a media company like us, there is even one more case: We have a lot of videos and need to compare the watchtime per video start across videos to the average as well. Things like "video a is watched 2 minutes less than average" are very important to us!

Does this clear things up a bit? 🙂