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.
Criteo Output SFTP connector that you created in Step 2.mastercustomerID column.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.
Criteo Output SFTP.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.
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.
Click Add Integration.
The system displays the Add Integration page.
Criteo Output SFTP.Criteo Output SFTP.Comma (,).Yes.yyyy-MM-dd.No.yyyy-MM-dd.No.csv.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.
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.
For more information, see Offline sales - flat file feed Criteo integration.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
csvevent_id |
| The transaction ID of the transaction made in the store. |
event_currency | The currency of the transaction. |
If this content did not answer your questions, try searching or contacting our support team for further assistance.