--- title: "Criteo" date: "2024-02-14T06:18:38+00:00" summary: "Enhance your advertising strategy with Criteo integration in Customer Data Platform. Retarget audiences, personalize campaigns, and optimize ad spend by leveraging user behavior and transaction data for more effective marketing." image: type: "page" url: "/customer-data-platform/criteo" id: "7aef3907-8863-4221-9668-6a3449676956" --- You can use Criteo to display interactive banner advertisements to your audience. Criteo displays ads based on the online browsing preferences and behavior of your users. Use cases --------- You can use the integration of Customer Data Platform (CDP) with Criteo in the following scenarios: * **Enable retargeting or personalization**: You can use the **Actions** interface to send an audience selection from CDP to Criteo for retargeting or personalization of your ads. Criteo can use the email addresses of the users in the audience segment and retarget. To set up the integration, see [Steps to retarget and personalize CDP campaigns](#steps-to-retarget-and-personalize). * **Avoid retargeting**: You can upload a file with the latest transactions to Criteo and prevent re-advertising to the customers who have already made a purchase. You can send the details of offline transactions to Criteo to enhance your revenue by not targeting users who purchased your product already. Therefore, you can get a better view of your ROI by including the attribution calculation offline transactions of ads viewers. To set up the integration, see [Steps to send transactional data to Criteo](#steps-to-send-transactional-data-to-Criteo). Steps to retarget and personalize CDP campaigns ----------------------------------------------- To retarget and personalize campaigns, CDP customers are responsible for completing the following steps: 1. [Create a new instance](/node/56903/#creating-a-new-instance). 2. [Create a new output connector](/customer-data-platform/criteo#creating-a-new-output-connector "Criteo"). 3. Connect to the SFTP server using the credentials that you generated. You must note the directory or folder created, which is a number by default. Rename the directory for clarity and ease of identification. For example, _Criteo Audiences_. 4. Navigate to **Actions** > **Campaigns+** and create an audience that you want to send to Criteo. When selecting the content for your audience, you must use an MD5 hash as Criteo does not support SHA256-based values. If your CDP tenant does not have an MD5 email hash column, [create a Support ticket](/service-offerings/support "Support") to get it created. 5. On the Destination tab of your CDP campaign: 1. Select the `Criteo Output SFTP` connector that you created in Step 2. 2. Select the checkbox to exclude the master customer ID as Criteo cannot process files that contain a `mastercustomerID` column. 3. In the **Output Folder Path** field, type the directory name from the SFTP detailed in Step 3. 6. Schedule and/or export the audience as required. 7. Collaborate with Criteo and ask them to establish a process to ingest files from the SFTP.  You must contact Criteo to initiate the setup and share the SFTP hostname, port, username, and password with Criteo in a secure manner. Using the credentials, Criteo can only access the SFTP directory that was created when you created the new Output Connector.  ### Creating a new instance 1. [Sign in to the CDP user interface](/customer-data-platform/getting-started/signin-cdp). 2. Navigate to **Integrations** > **Instances**. 3. Click **Add Instance**. 4. In the **Instance Information** area: 1. In the **Name** field, type `Criteo Output SFTP`. 2. In the **Instance Type** field, select `SFTP Service Provision`. 3. In the **Allow-List Source IP Addresses** field, enter one or more IP addresses that Criteo uses to access the SFTP. You must obtain the IP addresses from Criteo. 5. In the **Instance Credentials** area, leave the **SFTP URL Domain**, **SFTP Port**, **Username**, and **Password** fields blank. 6. Click **Save**. The **Instance Credentials** are populated. Ensure that you copy the credentials and secure them for future use. After you leave the page, the credentials are no longer accessible. If you regenerate the credentials, your connector stops functioning until Criteo uses the new ones. For detailed information on Instances, see [Instances](/customer-data-platform/instances "Instances") and [Creating instances](/customer-data-platform/creating-instances "Creating instances"). ### Creating a new output connector 1. [Sign in to the CDP user interface](/customer-data-platform/getting-started/signin-cdp). 2. Navigate to **Integrations** > **Output Connectors**. 3. Click **Add Integration**. The system displays the **Add Integration** page. 4. In **Destination**, click **SFTP CSV Connector**. 5. Click **Next**. 6. In **Basic Information**: 1. In the **Name** field, type `Criteo Output SFTP.` 2. In the **Description (Optional)** field, type a description to indicate the purpose for the connector that is visible to other users. 7. Click **Next**. 8. In **Credentials**: 1. In the **Select SFTP Instance Type** area, click **SFTP CDP**. 2. In the **Select CDP Instance** area, in the **Instance Name** field, select `Criteo Output SFTP`. 9. Click **Next**. 10. In  **Format**: 1. **Basic Parameters**: 1. In the **Delimiter** field, select `Comma (,)`. 2. In the **Exclude 'executionID' column in output file** field, select `Yes`. 3. In the **Date and Time Format** field,  select `yyyy-MM-dd`. 2. **Advanced Parameters**: 1. In the **Do you want to use a non-traditional CSV format?** field, select `No`. 2. In the **Date and Time format for output file name** field, select `yyyy-MM-dd`. 3. In the **Do you want to enable PGP encryption** field, select `No`. 4. In the **Modify extension in output file** field, keep the auto-populated value `csv`. 11. Click **Publish**. Steps to send transactional data to Criteo ------------------------------------------ 1. [Create a Support ticket](/service-offerings/support#contact-acquia-support) to send transactional data to Criteo. This is a responsibility of CDP customers. 2. Create an incremental export process to send all the required attributes through a template report to Criteo. For more information, see [Template report](#template-report). This is a responsibility of Acquia. ### Template report The template report contains the following columns: Field name Description `user_email` The MD5 hash of the customer’s email. `event_timestamp` The transaction timestamp in ISO 8601 standard `UTC:yyyy-MM-ddTHH:mm:ssZ`. `event_store_id` The store ID where the transaction is made. `event_name` The name of the event hardcoded as `storeTransaction`. `event_item_quantity` The quantity of products bought as a part of transaction separated by pipe delimiter (|) for transactions having more than one product bought. `event_item_price` The price of products bought as a part of transaction separated by pipe delimiter (|) for transactions having more than one product bought. `event_item_id` The product IDs bought as part of transaction separated by pipe delimiter (|) for transactions having more than one product bought. `event_id` The transaction ID of the transaction made in the store. `event_currency` The currency of the transaction. For any issues during the setup process, [contact Acquia Support](/service-offerings/support#contact-acquia-support). For more information, see [Offline sales - flat file feed Criteo integration](https://help.criteo.com/kb/guide/en/offline-sales-onboarding-flat-file-feed-integration-8g1zFYawMy/Steps/775585).