- Analytics Admin Guide
- Analytics Release Notes
- Adobe admin console
- Analytics admin tools
- Admin tools overview
- Code Manager
- Data Sources
- Exclude by IP address
- Logs
- Reporting Activity Manager
- Report Suite manager
- Edit settings of a report suite
- General
- General Account settings
- Internal URL Filters
- Customize Calendar
- Paid Search Detection
- Customize Menus
- Processing Rules
- Processing rules overview
- Processing Rules
- Processing rules examples
- Examples of processing rules
- Populate a campaign ID from a query string parameter
- Set the product view event from the product overview page
- Add a subcategory by concatenating the category and page name
- Determine a path by copying an eVar value to a prop
- Clean up values in a report
- Populate internal search terms using a query string parameter
- Copy a context data variable to an eVar
- Set an event using a context data variable
- Remove an event from a hit
- Processing rules tips and tricks
- Bot Rules
- Privacy Settings
- Timestamps Configuration
- Server-Side Forwarding
- Traffic
- Conversion
- Marketing Channels
- Traffic Management
- Default Metrics
- App Management
- Media Management
- Activity Map
- AEM
- Adobe Campaign
- Privacy Reporting
- Document Cloud Management
- Advertising Analytics Configuration
- Real-Time
- General
- Manage report suites
- Rollup and global report suites
- Save a report suite search
- Download report suite settings
- New report suite
- Report suite templates
- Edit settings of a report suite
- Company Settings
- Data Governance Privacy Labeling
- Server Call Usage
- User and Product Management (Legacy)
- Admin API
Timestamps optional
Combine both timestamped and non-timestamped data into a single report suite.
Timestamps Optional lets you:
- Mix timestamped and non-timestamped data in the same global report suite.
- Send timestamped data from a mobile app to a global report suite.
- Upgrade apps to use offline tracking without having to create a new report suite.
If you use Timestamps Optional, do not set s.visitorID on data that is already timestamped. This can lead to out-of-order data and negatively impact time calculations (such as time spent values), attribution (eVar persistence), visit number/visit counts, and pathing reports.
Timestamp-enabled session data is kept for up to 92 days. This means that a visit/session will be “held open” for 92 days while any additional hit - that isn’t 30 minutes after the previous hit (in hit time) - can still be included in the same visit/session. Any “old” hits that are received out of order will produce “unknown” results, since a number of factors (segmentation, allocation, expiration, etc.) influence whether these hits will be included in reporting or not.
New Report Suites
-
If created from a template, a new report suite defaults to Timestamps Optional.
(You can create a new report suite from a template at Admin > Report Suites > Create New > Report Suite.)
-
If copied from an existing report suite, then the new report suite inherits the timestamp setting from the original, including:
- Timestamps not allowed (setting s.visitorID supported)
- Timestamps required (setting s.visitorID not supported)
- Timestamps optional (setting s.visitorID supported but not on timestamped hits)
To change existing report suites to Timestamps Optional
-
Go to Admin > Report Suites > Edit Settings > General > Timestamp Configuration.
-
Select the Convert selected report suites to Timestamps Optional box.
This will change your report suite to Timestamps Optional.
If a report suite was set to Timestamps Optional, to change this to any other setting, please contact Adobe Client Care.
Business.Adobe.com resources
Resources
Adobe Account
