Load IDs

Before you begin, you need to understand how data collection and load IDs work in the Digital Data Exchange API.

Some data event types do not return complete data until their associated session is complete. For example, page view event data can be collected as soon as that event takes place, and before the visitor's current session ends. However, purchase event data or cart abandonment event data needs to be calculated from completed session data; therefore, it is not sent until the session is complete. When you make an API request, only completed events are included in returned data.

API requests can be configured to return data that is associated with Load IDs for a range of 8 days before the current Load ID. Data for load IDs earlier than 8 days is not available.

Collected data is loaded into the database every 5 minutes. Each new batch of data is identified by a unique Load ID. The Load ID is a number that is assigned by the system that processed that batch of data. The Load ID increments by a set amount for each new batch of data and is defined by the last batch Epoch time value included in that Load. More information on Epoch conversions can be found at the following URL http://www.epochconverter.com/epoch/timezones.php.

When you make API requests, the Load ID is required as a parameter in the API request URL. To acquire data continuously over time, you need to create an iterative process to pass API request URLs with sequentially incremented Load IDs.

You can use the Load ID for filtering purposes to request data from the API. You can also use the Load ID to request data pro-grammatically in your API call to continuously update the most recent data. .