Mismatch Between Metrics in Date Comparison vs Panel Date Range | Community
Skip to main content
S
SusiePo1
Level 2
June 14, 2024
Solved

Mismatch Between Metrics in Date Comparison vs Panel Date Range

  • June 14, 2024
  • 1 reply
  • 1641 views

Hello,

 

I am having a weird issue in workspace with some date ranges associated to Segments. Our segments are setup at a hit container, utilizing Tracking Code "starts with", as our operator. Our Tracking Code dimension has a 7 day expiration.

 

When I utilize the segment in a Freeform table within a Date Range comparison, I see a different number for Visits & Revenue than I see when creating a Freeform Table under a new panel with the 2023 dates as the panel date range. Can someone help me understand why this might be happening? Shouldn't the numbers be the same?

 

Thank you!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Jennifer_Dungan

Hmm maybe try some other correlations / metrics with this setup?

 

For instance, what if you look at the Tracking Code Instance (which should only trigger when the tracking code is explicitly set/sent to Adobe? Of course this won't work with the Revenue, since that is down stream (the purchase won't be on the same hit as the tracking code being set).

 

With something that is limited to the hit, the different date range qualifiers shouldn't impact the data as much (it should match).... 

1 reply

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
June 14, 2024

You would think they would be the same... but I think there may be something to the 7 day Tracking Code attribution and the way the dates are handled slightly differently in the logic... for instance, a tracking code that started before June 11 or extended beyond June 15 may be cut off slightly differently between the panel date range and the custom date range.... 

 

 Unfortunately, the logic of those pulls is a bit of a black box....

    S
    SusiePo1Author
    Level 2
    June 17, 2024

    Thank you for your response Jennifer. I was thinking that as well, is there anything I can dig into further to prove that is the 7-day expiration? We have other segments that use similar logic for the Tracking Code dimension that do not have this same issue. 

    Jennifer_Dungan
    Community Advisor and Adobe Champion
    Jennifer_DunganCommunity Advisor and Adobe ChampionAccepted solution
    Community Advisor and Adobe Champion
    June 17, 2024

    Hmm maybe try some other correlations / metrics with this setup?

     

    For instance, what if you look at the Tracking Code Instance (which should only trigger when the tracking code is explicitly set/sent to Adobe? Of course this won't work with the Revenue, since that is down stream (the purchase won't be on the same hit as the tracking code being set).

     

    With something that is limited to the hit, the different date range qualifiers shouldn't impact the data as much (it should match).... 

    Terms & ConditionsAccessibility statement

    Loading footer...