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.
- 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 retarget and personalize CDP campaigns
To retarget and personalize campaigns, CDP customers are responsible for completing the following steps:
- Create a new instance.
- Create a new output connector.
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.
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 to get it created.
- On the Destination tab of your CDP campaign:
- Select the
Criteo Output SFTP connector that you created in Step 2. - Select the checkbox to exclude the master customer ID as Criteo cannot process files that contain a
mastercustomerID column. - In the Output Folder Path field, type the directory name from the SFTP detailed in Step 3.
- Schedule and/or export the audience as required.
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
- Sign in to the CDP user interface.
- Navigate to Integrations > Instances.
- Click Add Instance.
- In the Instance Information area:
- In the Name field, type
Criteo Output SFTP. - In the Instance Type field, select
SFTP Service Provision. 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.
- In the Instance Credentials area, leave the SFTP URL Domain, SFTP Port, Username, and Password fields blank.
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 and Creating instances.
Creating a new output connector
Steps to send transactional data to Criteo
Create a Support ticket to send transactional data to Criteo.
This is a responsibility of CDP customers.
Create an incremental export process to send all the required attributes through a template report to Criteo.
For more information, see 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. |
|
For any issues during the setup process, contact Acquia Support.
For more information, see Offline sales - flat file feed Criteo integration.
Criteo
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.
- 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 retarget and personalize CDP campaigns
To retarget and personalize campaigns, CDP customers are responsible for completing the following steps:
- Create a new instance.
- Create a new output connector.
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.
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 to get it created.
- On the Destination tab of your CDP campaign:
- Select the
Criteo Output SFTP connector that you created in Step 2. - Select the checkbox to exclude the master customer ID as Criteo cannot process files that contain a
mastercustomerID column. - In the Output Folder Path field, type the directory name from the SFTP detailed in Step 3.
- Schedule and/or export the audience as required.
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
- Sign in to the CDP user interface.
- Navigate to Integrations > Instances.
- Click Add Instance.
- In the Instance Information area:
- In the Name field, type
Criteo Output SFTP. - In the Instance Type field, select
SFTP Service Provision. 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.
- In the Instance Credentials area, leave the SFTP URL Domain, SFTP Port, Username, and Password fields blank.
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 and Creating instances.
Creating a new output connector
Steps to send transactional data to Criteo
Create a Support ticket to send transactional data to Criteo.
This is a responsibility of CDP customers.
Create an incremental export process to send all the required attributes through a template report to Criteo.
For more information, see 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. |
|
For any issues during the setup process, contact Acquia Support.
For more information, see Offline sales - flat file feed Criteo integration.