This article demonstrates how to configure the Criteo Connector in your UDH profile and enable cookie sync between Criteo and AudienceStream.

Table of Contents Placeholder

Requirements

  • Criteo Account
  • Client Account ID

Supported Actions

Action Name What does it do Trigger on Audiences Trigger on Streams
Homepage Event Tracks homepage visits
Listing Event Tracks category or product listing page visits
Product Event Tracks product views
Cart Event Tracks cart activities
Conversion Event Tracks successful conversions
Search Event Tracks site search and other generic visitor activities

Configure Settings

Go to the Connector Marketplace and add a new Criteo Connector. Read the Connector Overview article for general instructions on how to add a Connector.

To configure your vendor, follow these steps:

  1. In the Configure tab, provide a title for the Connector instance.
  2. Enter the Client Account ID you received from Criteo.
  3. Provide additional notes about your implementation.
  4. Click Save

Action Settings - Parameters and Options

Click Next or go to the Actions tab. It's where you'll set up Actions and trigger them. This section describes how to set up Parameters and Options for each Action. 

The following Parameters are common to all Criteo Actions.

  1. Criteo ID/Encrypted User ID (REQUIRED): Your criteo cookie ID (same as the userid parameter). Select the relevant Attribute or enter the ID as custom value in this list.
  2. Site Type: The device type or site version used for browsing. See available options below.
  3. Dynamic Site Type: If the site type value is dynamic, use this field instead. Select an Attribute that contains one of the following values:
    • d for desktop
    • m for mobile
    • t for tablet
  4. Event Data to Set: Additional homepage event data to send to Criteo. Map relevant Attribute(s) to your Criteo destination in the To field. Click the plus button to add more mappings.

Options - Site Type

Option Description
Desktop The desktop or classic version of your site. This is often the site that browsers will access.
Mobile The mobile version of your site
Tablet The tablet version of your site

 

Below are Action-specific parameters. You'll configure them along with the common parameters (described above).

 

Action  Parameter Description
Listing Event  

Item ID(s) to Set (REQUIRED

List of product or category identifiers to send to Criteo.

Enter the ID as a custom value or select the relevant Attribute(s) that contains it. Click the plus button to map multiple identifiers.

Product Event  

Item ID (REQUIRED)

 Unique id of the item or product being tracked. 

Enter the ID as a custom value or select the relevant Attribute(s) that contains it. 

Cart Event and Conversion Event Set Item Properties (REQUIRED)

 Additional data about the cart item(s) being tracked. 

Map the data from a Tally or a String Attribute to a Criteo property name in the To dropdown.

NOTE: You are required to map Item Quantity and Item Price. For additional mappings, click the plus button.

Conversion Event

General Data to Set

(OPTIONAL)

 Additional data about the conversion or transaction.

Map the relevant Attribute to an option in the To dropdown. See available options below.

 Search Event

Search Data to Set (OPTIONAL)

Additional data about a product or item that the visitor searched for.

Map the relevant Attribute(s) and enter a custom Criteo destination in the To dropdown.

Options - General Data to Set

Option Description
Transaction ID Unique identifier of the transaction
New Customer

Boolean value that determines whether or not the visitor is new.

Set to 1 for first purchase and 0 for subsequent purchases (leave blank if not available).

Deduplication Set to 1 if attributed to Criteo or 0 if not attributed (leave blank if not available) 

Enabling cookie sync between Criteo and UDH

In order for AudienceStream to receive a redirect call from Criteo, you must sync it with the Criteo ID. Here are the steps to do that:

 

Step 1: In your Tealium iQ account, set up a Variable to store the the Criteo ID.  

criteo ID variable.png

 

Step 2: Add and configure the Criteo Cookie Matching Service Tag from Tealium’s Tag Marketplace. Attach a custom Load Rule to load the Tag only when the The Criteo ID String (a.k.a. Trait) Attribute is not defined in the matching UDH account.

cookie sync tag.png

Save and Publish the changes you made in Tealium iQ.

Step 3: Go to the matching UDH account. Create a Rule that checks if the Criteo ID Variable is assigned and populated (i.e. not empty).

Criteo ID Rule.png

 

Step 4: Create a visitor-scoped String Attribute to capture the Criteo ID in UDH. Attach the Rule you created in step 3. 

Criteo ID String Attribute.png

Step 5: Create a visitor-scoped Boolean Attribute to check whether the ID has been captured. Attach the Rule you created in step 3.

Criteo ID Flag.png

 

Step 6. In your Criteo Connector configuration, make sure to set the Criteo ID/Encrypted User ID parameter to the String Attribute you created in step 4.

Finally, save and publish in your UDH profile. UDH is now set up to accept the Criteo ID.

Validating Criteo Cookie Sync using Trace

The 1st user event will be the standard page load. But the 2nd user event will be the reception of the Criteo ID. 

Trace screen.png

The left navigation shows the current state of your visitor profile. In the Attributes Added section, notice the Criteo is present with a value and the Boolean flag (true) further confirms it was indeed captured. This confirms that UDH is receiving and storing the Criteo ID.

Version history
Revision #:
8 of 9
Last update:
‎06-20-2017 08:34 AM
Updated by: