timestamp com data incorreta | Community
Skip to main content
M
mpiovesan
June 13, 2023
Solved

timestamp com data incorreta

  • June 13, 2023
  • 1 reply
  • 590 views

Good afternoon,

Currently, I configured the timestamp eVar for terms in Adobe Analytics reports with the configuration of:

But there are some records that are being returned as "(Low traffic)"

And the records after being exported by the data Warehouse come with past or future data (compared to the date in question)
Pulling the specific date range (hypothetically):
06/12/2023.
Within the "Timestamp" field, it returns as "01/01/2015".

Has anyone experienced this problem or know what kind of configuration I should do?

 

NOTE: These are some cases, not all.

 

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

Since you are relying on client time codes, are you sure these aren't just coming from users with their device time set incorrectly? Especially since this is just some cases and not all?

 

Have you tried testing by messing with your device time and seeing what happens?

 

Maybe people are using an emulator, and they have no onus to actually care if the system time is actually correct? Maybe this is part of your automated testing process using a bot which also may not pass or use a valid time code?

 

Sadly relying on client timestamps can come with difficulties that can be out of your control...

1 reply

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
June 13, 2023

Since you are relying on client time codes, are you sure these aren't just coming from users with their device time set incorrectly? Especially since this is just some cases and not all?

 

Have you tried testing by messing with your device time and seeing what happens?

 

Maybe people are using an emulator, and they have no onus to actually care if the system time is actually correct? Maybe this is part of your automated testing process using a bot which also may not pass or use a valid time code?

 

Sadly relying on client timestamps can come with difficulties that can be out of your control...

    Terms & ConditionsAccessibility statement

    Loading footer...