ON THIS PAGE
Criteo is a demand-side platform (DSP) provider built on the open internet, which enables retailers, brands, and big and small publishers to display personalized online ad campaigns to users who have previously visited their website.
You can replicate your campaign information and campaign performance statistics to your Destination database or data warehouse using Hevo Pipelines.
An active Criteo account.
Criteo API key and secret for authorizing Hevo to access the data in Criteo.
Configuring Criteo as a Source
Perform the following steps to configure Criteo as the Source in your Pipeline:
Click PIPELINES in the Asset Palette.
Click + CREATE in the Pipelines List View.
In the Select Source Type page, select Criteo.
In the Configure your Criteo Source page, specify the following:
Pipeline Name: A unique name for your Pipeline.
Client ID: The API token that you created in Criteo to enable Hevo to read data from your Criteo account.
Client Secret: The API Secret for the API Key that you created in Criteo.
Historical Sync Duration: The duration for which the past data must be ingested.
Click TEST & CONTINUE.
Proceed to configuring the data ingestion and setting up the Destination.
Obtaining the API Key and Secret
To provide Hevo access to your Criteo data, you need to create an API user in Criteo, and log in to Hevo using that user’s API key and secret.
Sign in to your Criteo Marketing Console.
Click on the hamburger menu and scroll down and click Team.
In the Team page, click Add API User.
In the Contact Email field, specify the Email ID to which you wish to give the API access, and assign a role to this user. Available roles include Business Manager, Financial Manager, and Technical Manager.
Click Add User.
The new user is created. Copy the Client ID and Client Secret. You will be using it to configure Criteo in Hevo.
Select the confirmation check box and click Close.
You can now view the list of API users in the page:
Historical Data: Hevo ingests the historical data for the
campaign_reportobject 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_reportobject though, only the new and modified data is ingested.
Refresher Data: All reporting data for the
campaign_reportobject 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:
The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:
|Advertiser||Retrieve list of specific advertisers for your user. (Advertiser Portfolio)|
|Bid||All bids associated to each campaign category are stored in the Bid object.|
|Budget||Budget details such as name, amount, balance etc associated to an advertisers profile are stored in the Budget object. A budget is the maximum amount of money you would like to spend to show people your ads. It also helps you control your overall spend across your Criteo campaigns.|
|Campaign||The complete list of campaigns for Advertiser(s) along with activity and bid statuses are stored in the Campaign Object. Campaigns include Running, Inactive as well as Archived campaigns.|
|Campaign Report||Daily level reports showcasing all statistical metrics, available in the following dimensions:
- Campaign ID
- Category ID
Note: To keep the data sanitised, we will update the data for the last 30 days for the campaign report object.
|Category||All campaign categories for a specific advertiser’s campaigns are stored in this object along with pricing, bid, names, and activity status.|