This variable lets you customize the timestamp of a hit similar to the AppMeasurement libraries for other platforms.
Not reported directly.
Set by data collection servers.
s.timestamp="UNIX or ISO-8601 format timestamp"
The timestamp variable must be in the format explained in the next section.
You can also use the Timestamps Optional setting to mix timestamped and non-timestamped data in the same global report suite, send timestamped data from a mobile app to a global report suite, and upgrade apps to employ timestamps without having to create a new report suite.
Timestamps must be in UNIX (seconds since Jan 1st 1970) or ISO-8601 format, with the following restrictions on the accepted ISO-8601 format:
- Both date and time must be provided, separated by "T"
- The date must be a calendar date with full precision (year, month, and day). . Week dates and ordinal dates are not supported.
- The date can be in standard or extended format ( YYYY-MM-DD or YYYYMMDD ), but they must include the hour and minute. Seconds are optional ( HH:MM , HH:MM:SS , HHMM , or HHMMSS ). Fractional minutes and seconds can be passed in, but the fractional part is ignored.
- An optional time zone can be specified in standard or extended format ( ±HH , ±HH:MM , ±HH , ±HHMM , or Z)
UNIX timestamps continue to be supported (seconds since Jan 1st 1970).
The following list contains examples of valid ISO-8601 format timestamps:
2013-01-01T12:30:05+06:00 2013-01-01T12:30:05Z 2013-01-01T12:30:05 2013-01-01T12:30
A report suite must be enabled to accept custom timestamps by Customer Care before you can use this variable. After custom timestamps are enabled, all hits sent to the report suite must contain a timestamp or they are discarded.
Pitfalls, Questions, and Tips
- Timestamps are primarily used to track offline data on mobile platforms. Custom timestamps are typically disabled unless you are collecting both web and offline app data in the same report suite.
- Data is timestamped when offline data is enabled in the mobile SDK (default setting) or anytime a report suite is configured to accept timestamped data. Data collected offline may be sent hours or weeks after the date when the event originally occurred. These hits may be queued within the Analytics platform for minutes or hours longer than hits without timestamps:
- For timestamped data sent in very near current time, the probable delay is 10-15 minutes.
- For timestamped data sent in from yesterday, the probable delay is about 2 hours.
- For timestamped data sent in that is older than yesterday, every day adds about 2 hours of delay, up to a maximum of 48 hours.