ePrivacy and GPDR Cookie Consent by Cookie Consent Skip to main content

Criteo Destination

1. Steps to implement Criteo destination

  1. Create a task in #help_it to create the destination in Business Explorer (CDP).

    For on-premise implementation, instructions may be given by product team for clients to execute.

  2. Create a workspace in Meiro Integrations (MI) for the Criteo destination. This is the workspace that will run when the user clicks on "Export" in the segment builder.
  3. The workspace consists of a CDP Destination connector, a processor, and a Criteo loader.
  4. In Business Explorer, select the MI workspace under Meiro Integrations that you have created for the Criteo destination.
  5. Set up an attribute for "Emails" which contains all the emails of a customer, as well as the attribute definition in Customer Data Model (CDM). (Optionally, you can include a Mobile Ad Identifier attribute if it's available, or any other identifier type supported by the Criteo loader. More details can be found in the documentation for Criteo loader. )
  6. Go to Administration > Entities > Destinations > image-1617862210083.png (pencil icon) Edit
  7. Add the created attribute under exported attributes and mandatory attributes.
  8. Add Parameters - Parameters will show up in the segment builder when user chooses Criteo destination as an export destination. It will be populated into the MI workspace variable of the same name. Parameters to add:
    1. advertiser_id (required, user input) - Advertiser ID (if client has only one Advertiser ID, it can be set manually in MI Workspace and the parameter in destination can be removed, the id can be found in Criteo app in the url on homepage)
    2. audience_id(user input) - Audience ID
    3. audience_name(required, user input) - Audience Name
    4. audience_description (required, user input) - Audience Description (Same as Advertiser ID - can be set manually as default value in MI Workspace and removed from destination)

Note: Audience ID is an optional field, when left empty, it creates a new audience upon export, with the name defined in Audience Name, and description in Audience Description. If filled, it removes existing users and adds new users to an existing audience after removing existing emails from that audience upon export, but it won't modify the Audience Name and Audience Description of the audience. Refer to the Criteo Loader documentation for more information.


If you defined parameters, you must make sure the Meiro Integrations Key matches the Workspace variable name in the chosen MI workspace.

When you are done, you should check the destination under Administration > Entities > Destinations (Example below)


Note down the ID of the destination, you will need it for the CDP Destination connector configuration

2. Configurations for Workspace in Meiro Integrations

CDP Destination connector
  • You will need to setup the MI API credentials and on the CDP
  • You will require the CDP API credentials for this connector.
  • The "Export Destination ID" is the ID of the CDP Destination for Google Analytics that is setup in Business Explorer.
  • You will require the credentials for the CDP database as well.
  • The output of this configuration is /data/out/tables/export.csv. Your processor will need to move it into /data/out/files/input.csv after processing.


  • For the processor, read from the segment export CSV file at /data/in/tables/export.csv . The CSV file should contain two columns, one for the customer_entity_id , and another one is the "Emails" attribute set up in the previous steps. You can always check the header name for that column in the file in MI. The "Emails" attribute column  should contain rows of JSON arrays in the form of ["john.doe@gmail.com", "mary.sue@gmail.com"].
  • Your processor would need to "unnest" the array and prepare the output CSV in the format required by the Criteo Loader, namely, with type and value columns. For every row, type should contain the value "email" and value should contain a single email value. The output file should be written by the processor into /data/out/tables/input.csv .
Criteo loader
  • The loader expects the exported audience segment to be in the path:  /data/in/tables/input.csv , though you can optionally specify a different file name under CSV Input File Name.
  • Set the Advertiser ID, Audience ID, Name of New Audience, and Description of New Audience to the workspace variables advertiser_id, audience_id, audience_name, and audience_description respectively. It is recommended to use workspace variables for the API Client ID and API Client Secret as well for the Criteo API Credentials.