CoolaData provides these options for specifying the timestamp of an event –

  • Device’s Timestamp (Default) – The CoolaData Tracker automatically adds the device’s timestamp.
  • Your Own Timestamp (Optional) – You can add your own timestamp to the event which overrides the device’s timestamp (described above).
  • CoolaData Server Timestamp (Optional) – CoolaData assigns its own server’s timestamp to all events.

CoolaData automatically performs a sanity check of all event timestamps.

Note – Each CoolaData Tracker automatically enriches the events that you send by adding more properties (these are also called common properties). To see the list of common properties that are automatically enriched by CoolaData’s Trackers into each event.

Device’s Timestamp – Default

CoolaData automatically enriches each event with an event timestamp (named event_time_ts). This timestamp is determined by the device’s timeclock and indicates when the event happened, meaning when it was sent by your app using the CoolaData Tracker. CoolaData automatically stores and presents event timestamps in UTC time standard. The CoolaData Tracker also automatically adds a timezone_offset property to each event specifying the device’s time zone offset from UTC time, in hours. For example, -2.5.

CoolaData automatically performs a sanity check of the timestamp.

Your Own Timestamp – Optional

To specify your own timestamp for each event, simple add the event_time_ts property to the event’s JSON. Specify this timestamp in 13-digit format (milliseconds). CoolaData then uses this timestamp instead of your device’s (event_time_ts – described above).

CoolaData automatically performs a sanity check of the timestamp.

This option is only relevant when CoolaData is not set to use its server timestamp, as described in CoolaData Server Timestamp – Optional.

IMPORTANT NOTE – When using JavaScript Tracker or CoolaData REST API  in order to include your own timestamp, simple include the event_timestamp_epoch property (instead of event_time_ts – described above) in the event’s JSON. CoolaData then uses this timestamp which is UTC time standard.

CoolaData Server Timestamp – Optional

In general the timeclocks of some devices’ may not be accurate. Upon request, CoolaData can configure your system so that CoolaData automatically assigns the timestamp of the CoolaData server to each event instead of the timestamp of the device that sent the event. To activate this feature, contact your CoolaData customer success representative.

Benefit – The advantage of using this feature is to ensure that all the collected data is synchronized to the same clock, and that no events are rejected because of invalid dates.

When this feature is activated, all timestamps that you send with the event are ignored and an accurate UTC timestamp is assigned instead. If you would like to use this feature and would also like to send your own timestamp, then add your own timestamp to each event in another property. For example, you could name it client_timestamp.

Timestamp Sanity Check

CoolaData automatically performs a sanity check of the device’s timestamp or of your timestamp.

By default, an event is considered Invalid when its timestamp is more than 12 hours into the future or 30 days into the past. For example, future timestamps may occur when an end user’s clock is set incorrectly.

These types of events are not stored in CoolaData and appear in the Invalid List with the following reason – Future event sent or Past event sent

Click here to see how to reconfigure this time range in the CoolaData Administrator console.

Print Friendly