About Timestamps Optional features
Timestamps Optional allows you to integrate and report across multiple report suites with or without client-side timestamps included. With Timestamps Optional you can update your app to employ timestamps while still using non-timestamped data from the previous app.
In previous releases… | In addition… |
---|---|
Timestamped data could not be sent to a non-timestamped global report suite. Consequently, hit data sent from offline devices was dropped when adding to a non-timestamped report suite. Consequently, hit data sent from offline data was dropped when adding to a non-timestamped report suite. | Updating an app to collect and use timestamps required you to employ a new report suite. You could not save to the existing report suite or integrate existing data when updating your app to use timestamps. |
With Timestamps Optional, you can integrate non-timestamped data from a live website with offline data from mobile devices, or update your non-timestamped app to a timestamped app.
Combining data into a Global Report Suite
Combining data into a global report suite can be done in multiple ways, including multi-suite tagging, Vista rules, and imported batch files from offline sources.
Best practices when employing timestamps
The following are best practices and a few requirements and restrictions to be aware of when integrating timestamped with non-timestamped data.
-
In general, timestamps for a given visitor or visit must arrive at Adobe in the correct chronological order.
Out-of-order data can include late arriving data from offline data collection and late arriving hits, or out-of-sync clocks on offline mobile devices. Out-of-order data can negatively impact time calculations (such as time spent values), attribution (eVar persistence), visit number/visit counts, and pathing reports.
-
Using timestamps when setting a s.visitorID is not recommended. It can lead to out-of-order data.
-
Hybrid apps composed of an app (timestamped, offline data) opening a web browser (non-timestamped, live data) should not use timestamps. It results in inaccurate reporting of the session.
In addition, hybrid apps should not set a visitor ID.
More help on this topic
Analytics
- Analytics tech notes
- Adobe Analytics for Google Analytics users
- Analyze data impacted by events
- Client hints
- Cookies
- Data retention
- Domains
- Exclude data
- IP addresses
- Latency
- Low-traffic value
- Migrate Mobile Services processing rules to Adobe Analytics
- Multi-currency support
- Privacy overview
- Processing order
- Progressive web apps
- Redirects and aliases
- Security resources
- Terms used (glossary)
- Timestamps Optional
- Troubleshoot logging in
- Troubleshoot getting logged out
- Unspecified, other, and unknown
- Visitor migration
- VISTA rules
Data Drip: Benefits of migrating from an old system to WebSDK
Data Drip
Thursday, Apr 10, 4:00 PM UTC
Join us as Adobe Technical Advisor, Arindam Agarwal, guides us through the benefits of implementing Adobe WebSDK. Arindam will provide an in-depth overview and answer questions live during the Q&A. Register today!
RegisterAdobe Analytics at Summit
Register for these sessions:
- Elevate and Empower Teams with Agentic AI for Exceptional Experiences (attend online)
- Adobe Analytics: Using Advanced Metrics to Level Up Your Reporting (attend online)
- Adobe’s New Tools: Empowering Third-Party Developers (attend online)
- Put the Customer at the Center and Build Relationships That Last a Lifetime (attend online)
- How EY Enhanced Regulatory Knowledge Management with Adobe Solutions (attend online)
Connect with Experience League at Summit!
Get front-row access to top sessions, hands-on activities, and networking—wherever you are!
Learn more