Collecting data from Criteo Marketing Solution

This guide explains how to collect data from Criteo Marketing Solution. To learn how to collect data from a different data source, go back to the Available data sources in Adverity overview.


For a list of the fields that you can collect from Criteo Marketing Solution, see Criteo Marketing.


Before you start collecting data from Criteo Marketing Solution, perform all of the following actions:

  1. Generate a consent URL in Criteo Marketing Solution.

  2. Send the consent URL to the account administrators of the advertiser accounts that you want to access.

For more information, see the Criteo documentation.

Creating a datastream to collect data from Criteo Marketing Solution

The basics of creating a datastream to collect data from any data source are explained in our guide to Creating a datastream. This guide contains information about the specific steps to create a datastream to fetch data from Criteo Marketing Solution.

Configuration: Choose the data you want to collect from Criteo Marketing Solution

To choose what data to collect and customize the Criteo Marketing Solution datastream configuration, follow these steps:

  1. (Optional) Rename your datastream.

  1. In Advertisers, select the advertisers for which to collect data. If you do not select any items in a drop-down list, Adverity collects data for all items in the drop-down list.

  1. In Dimensions and Metrics, change the list of fields that you want to see in your data extract.

  1. (Optional) In Currency, select the currency of the cost-related metrics.

  1. (Optional) In Time Zone, select the timezone of the time-related metrics.

What's next?

Troubleshooting Criteo Marketing Solution

I cannot fetch more than 100,000 rows from Criteo Marketing Solution

The Criteo Marketing Solution API limits the maximum number of returned rows per request to 100,000.

To resolve this issue, instead of collecting all your data in one fetch, change your datastream settings and collect your data over several smaller fetches, e.g. using shorter date ranges.