This article describes how to set up the Criteo connector.
In this article:
Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector.
After adding the connector, configure the following settings:
Click Next or go to the Actions tab. This is where you configure connector actions.
This section describes how to set up parameters and options for each action.
|Event Type||The standard web, travel, or store event to send.
For more information, see Criteo Server to Server - Event Payloads.
|Account||The partner ID of the account you are sending the data to. It can be filled on the connector configuration screen or on the action screen. The value on the action screen has higher priority than on the connector configuration screen.|
|Email Raw||The user's raw email address. Will use the first non-empty value of email.|
|Email MD5 (apply MD5 hash)||The user's unhashed email address.|
|Email MD5 (already MD5 hashed)||The user's email address hashed with MD5.|
|Email SHA256 (apply SHA256 hash)||The user's unhashed email address.|
|Email SHA256 (already SHA256 hashed)||The user's email address hashed with SHA256.|
|Email SHA256 MD5 (apply SHA256 MD5 hash)||The user's unhashed email address.|
|Email SHA256 MD5 (already SHA256 MD5 hashed)||The user's email address hashed with MD5 and SHA256.|
|GAID||Google's advertising identifier.|
|IDFA||Apple's identifier for Advertisers unique identifier.|
|Mapped User Id||(Required) The Criteo salted user ID (GUM ID) returned by the GUM call. See: Criteo Server to Server - Criteo GUM Call.|
|Mapping Key||The unique Criteo S2S key for the partner.|
|Site Type||The device type (or site version) used for browsing. Default option is "desktop". Available values are d (for Desktop), t (for Tablet), m (for Mobile).|
|Useragent||The user-agent of the browser or device.|