This article is a step-by-step guide for installing the Criteo OneTag in your Tealium iQ profile.
Table of Contents Placeholder
Tag Configuration
First go to the Tag Marketplace and add the Criteo OneTag to your profile (see how to add a tag).
After adding the tag, configure the below settings:
- Title: The default title is "Criteo OneTag". You have the option to replace it with a descriptive name of choice.
- Account (Required): Enter your Criteo account number. If you have more than one account, you may enter multiple account numbers as a comma-separated list.
You may override or dynamically set this value using the Tag's Data Mappings tab (more on this below).
- Event Name: Select the event (also called Advertiser Events) that corresponds to the page type you want to include Criteo OneTag on.
- viewHome: Set this Event on your home page. The account number is sent.
- viewItem: Set this Event on a product page. The account number, product ID, and user segment data is sent.
- viewList: Set this Event on a page that lists products. The account number, product IDs, and keywords are sent.
- viewBasket: Set this Event on a cart/basket page. The account number, product IDs, product quantities, and product prices data are sent.
- viewSearch: Set this Event on a search or search results page.
- trackTransaction: Set this event on the transaction page.
If you want to trigger multiple events with a single instance of Criteo OneTag, use the Data Mappings tab.
- Override Base URL (Optional): This field is pre-populated with the default location of the .js file. You have the option to override it but only if Criteo has instructed to host their file locally.
Load Rules
Load Rules determine when and where to load an instance of Criteo OneTag on your site.
Recommended Load Rule: Create custom Load Rules to load the tag on any page where you want trigger Criteo Events. For example, if you are tracking conversion events, load this tag on the checkout page or the confirmation page.
Data Mappings
Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see Data Mappings.
The destination variables for Criteo OneTag are built into the Data Mapping tab. Available categories are:
Standard
| Tag destination |
Description |
| Account ID (overrides account) |
Criteo account number |
| Event(s) (overrides default) |
Name of the Criteo event (see Event Name under Tag Configuration) |
| Search Keyword (for viewList) |
Search string (optional for the viewList event)
Make sure the Variable you are mapping contains a string value
|
| Customer ID (ci) |
Customer's unique identifier.
Criteo requires that this ID not contain personally identifiable information such as names, email addresses, unencrypted phone numbers, etc. Leave it empty if the customer is unknown or your site does not have unique IDs.
NOTE: This variable is not related to E-Commerce Extension's _ccustid variable.
|
| Deduplication/Sales Attribution (dd) |
Conversion attribution flag
The default value is 1, meaning the conversion is attributed to Criteo. A values of 0 means you are not attributing the conversion to Criteo. Mapping to this destination overrides the default.
|
| New Customer (nc) (set to 0 or 1) |
New customer flag.
The default value is 1, meaning the customer is new. A value of 0 means the customer is not new.
|
| Site Type (site_type) |
Version of the site.
Possible values are:
- m - The mobile version of your site
- t - The tablet version of your site
- d (default) - The classic version of your site. This is often the site that browsers will access.
|
| User Segment (si) |
User segment tracking value.
For example, a value of "1" can denote the home page, while a value of "2" can denote all other page types.
|
| Email/Hashed Email (hashed_email) [Array] |
Hased/unhashed email address of the customer
|
| Login/Hashed Login (hashed_login) [Array] |
Hased/Unhashed username set for the account
|
| setData Value (setData.###) |
Additional data points to be set and sent |
E-Commerce
Since the Criteo OneTag is e-commerce enabled, it will automatically use the default E-Commerce Extension mappings. Manually mapping in this category is generally not needed unless:
- you want to override any Extension mappings
- your desired ecommerce variable is not offered in the Extension
| Tag Destination |
Description |
E-Commerce Extension Variable |
| Order ID (order_id) (Overrides _corder) |
Unique transaction identifier.
|
_corder |
| Product IDs (overrides _cprod) [Array] |
Unique identifier of each product in the product array
|
_cprod |
| Product Prices (overrides _cprice) [Array] |
Unit price of each product in the product array |
_cprice |
| Product Quantities (overrides _cquan) [Array] |
Quantity of each product in the product array |
_cquan |
Travel
| Tag destination |
Description |
| Checkin Date |
Date of the check-in (yyyy-MM-dd). E.g. date of booking for a trip or rental. |
| Checkout |
Date of the check-out (yyyy-MM-dd) |
| Number of adults |
Number of adults in the booking |
| Number of children |
Number of children specified in the booking
|
| Number of babies |
Number of infants specified in the booking |
| Number of rooms |
Number of rooms specified in the booking |
Events
Map to these destinations for triggering Criteo events on a page. The event triggers when the supplied value is found in the Data Layer.
- Select an event from the dropdown list. You may choose from the predefined list or create a 'Custom' event. For 'Custom' event, enter a name with which to identify it.
- In the 'Trigger' field, enter the value of the Variable being mapped.
- Click Add.
- To map more events, click + and repeat #1, #2, and #3.
| Event Name |
Description |
| viewHome |
Home page viewed |
| viewItem |
Products viewed
|
| viewList |
Product listing viewed |
| viewBasket |
Cart page activity |
| viewSearch |
Search action |
| trackTransaction |
Transaction page activity |
| Custom |
Custom event |
Parameters
Map to this category if you want to pass additional data with the Event(s) destinations you mapped earlier.
In this category, you can send Parameters with predefined Criteo Events only. To send Parameters with a custom event, use the Custom Event Data category instead.
To pass a Parameter with a predefined Criteo Event:
- Event - Select your desired event from this dropdown.
- Parameter - Select a Parameter from this dropdown.
For Custom parameter, enter a name with which to identify it.
- Click +Add.
Full list of Parameters:
| Destination Parameter |
Description |
| Brand |
Brand name |
| Model |
Model name |
| Price |
Price associated with the event |
| UI Client |
User data |
| Custom |
Custom parameter to send with the event |
Custom Event Data
Map to this category if you want to pass a custom parameter with a custom Event.
To map a Custom Event,
- Event Name - Enter the name of the Custom Event exactly as specified in the Events tab.
- Parameter - Enter the name of the Parameter you wish to send.
- Click +Add.
Vendor Documentation
Expand/CollapseMenu
