A report suite with timestamp support disabled uses the date and time from which the image request was sent directly to Adobe data collection servers. If this type of report suite receives a hit with a custom timestamp, that hit is immediately and permanently discarded.

A report suite with timestamp support enabled uses the date and time as specified in the timestamp variable (s.timestamp in JS Appmeasurement or the ts query string). If this type of report suite receives a hit without a custom timestamp, that hit is immediately and permanently discarded.

Timestamped and non-timestamped data cannot co-exist in the same report suite; the two settings are mutually exclusive.

Behavior of timestamped data

Data timestamped for a date that has already passed can be displayed in Adobe Analytics, provided the report suite supports time stamped hits. Because of this capability, all historical data has the possibility to increase as historically timestamped data is collected.

Mobile applications frequently use timestamped report suites to assist in the collection of offline data. Since mobile devices are not always connected to the internet, the app stores multiple hits and sends them to data collection servers when connection is restored.

If a device has its system timezone set to one that is different from the one they are actually in, the timestamp can be logged for a future hour. Users can potentially see data for hours that have not yet happened yet due to this scenario. Visitors can spoof their time zone in their device settings, so it is possible for data to be collected for both past and future dates. 

이 작업에는 Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License의 라이센스가 부여되었습니다.  Twitter™ 및 Facebook 게시물은 Creative Commons 약관을 적용받지 않습니다.

법적 고지 사항   |   온라인 개인 정보 보호 정책