Criteo

Criteo uses the concept of private apps to create API keys containing the Client ID and Client Secret, which are used to authenticate Hevo to read your marketing and advertising data. The app is configured with the requisite permissions to fetch the different types of data from Criteo using REST APIs. The Pipeline in Hevo then integrates with the app to access the data and loads it into the Destination.

The transfer of data from your Criteo account to the Destination location, therefore, comprises the following one-time setups:

• Creating an app in Criteo and retrieving the Client ID and Client Secret.

• Assigning permissions to the app to read the data using Criteo’s Rest APIs.

• Creating a Pipeline in Hevo for transferring data from Criteo to the Destination database or data warehouse.

Configuring Criteo as a Source

Perform the following steps to configure Criteo as the Source in your Pipeline:

1. Click PIPELINES in the Asset Palette.

2. Click + CREATE in the Pipelines List View.

3. In the Select Source Type page, select Criteo.

4. In the Configure your Criteo Source page, specify the following:

   

   • Pipeline Name: A unique name for your Pipeline.

   • Client ID: The client ID provided in the file you downloaded in Step 4 of section, Retrieving the Client ID and Client Secret to enable Hevo to read data from your Criteo account.

   • Client Secret: The Client Secret provided in the file you downloaded in Step 4 of section, Retrieving the Client ID and Client Secret.

   • Timezone: The timezone as per which the Adset Transaction Report data must be replicated. Default timezone: UTC.

   • Currency: The currency in which the transaction values in the Adset Transaction Report must be replicated. Default currency: USD.

   • Historical Sync Duration: The duration for which the past data must be ingested.

5. Click TEST & CONTINUE.

6. Proceed to configuring the data ingestion and setting up the Destination.

---

Data Replication

Default Pipeline Frequency	Minimum Pipeline Frequency	Maximum Pipeline Frequency	Custom Frequency Range (Hrs)
3 Hrs	30 Mins	24 Hrs	1-24

• Historical Data: Hevo ingests the historical data for the campaign_report object on the basis of the historical sync duration selected at the time of creating the Pipeline.

• Incremental Data: Once the historical data ingestion is complete, every subsequent run of the Pipeline fetches the entire data for the objects. In case of the campaign_report object though, only the new and modified data is ingested.

• Refresher Data: All reporting data for the campaign_report object is refreshed on a rolling basis to update any conversions attributed to clicks for the past 30 days.

Note: The time taken to fetch historical data depends on how many days are selected at the time of creating a Pipeline. Hence, Hevo defaults this period to one year before today, and if required you may customize it to any date, with the earliest being January 01, 2010.

---

Schema and Primary Keys

Hevo uses the following schema to upload the records in the Destination database:

---

Data Model

The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:

Object	Primary Key	Description
Advertiser	- id	Contains the list of specific advertisers for your user. (Advertiser Portfolio).
Adset	- id	Contains the complete list of adsets (earlier called campaigns) for an advertiser along with activity and bid statuses.
Adset Transaction Report	- transaction_id	Contains report data of transactions within a given time period, transactions associated with select or all advertisers in your portfolio or specific transaction IDs.
Audience	- id	Stores the contact lists which are used for your advertising campaigns.
Statistics Report	- adset_id - advertiser_id - category_id - day	Contains day-level data related to your adsets’ (campaign) performance. The report returns all possible metrics supported by Criteo across the Advertiser, Category, and Adset dimensions for each day.

---

Limitations

None.