Criteo is a popular online display advertising platform that offers various solutions to increase your website traffic, generate brand awareness, and boost sales.

RudderStack supports Criteo as a destination to which you can send your event data directly.

Getting started

RudderStack supports sending event data to Criteo via the following connection modes:

Connection ModeWebMobileServer
Device modeSupported--
Cloud mode---
In a web device mode integration, that is, using JavaScript SDK as a source, the Criteo native SDK is loaded from domain. Based on your website's content security policy, you might need to allowlist this domain to load the Criteo SDK successfully.

Once you have confirmed that the source platform supports sending events to Criteo, follow these steps:

  1. From your RudderStack dashboard, add the source. Then, from the list of destinations, select Criteo.
  2. Assign a name to the destination and click Continue.

Connection settings

To successfully configure Criteo as a destination, you need to configure the following settings:

Criteo connection settings Criteo connection settings Criteo connection settings
  • Criteo Account ID: Enter your Criteo Account/Partner ID.
Refer to the FAQ section below for more information on getting your Account/Partner ID.
  • Home Page URL: Enter the complete URL of your website’s homepage.
This field is required when you need to fire the homepage tag to add visitors to your target audience, in cases where the event name of the page call is anything other than home.
  • Email Hashing Method: Criteo lets you use the email addresses in both hashed and non-hashed formats. If you choose MD5, RudderStack will hash-encode the email address before sending it to Criteo.
  • Map Specific Fields to Criteo Fields: Enter the payload fields and the corresponding mapped fields that will be used to send the event data to Criteo.
Criteo allows you to send any extra data about a page or a user to add more context to the events. You can set this feature in Criteo with the assistance of your Criteo Account Manager. You can then use the Map Specific Fields to Criteo Fields field mapping feature to send extra data through RudderStack.
  • Client-side Events Filtering: This setting lets you specify which events should be blocked or allowed to flow through to Criteo.
For more information on this setting, refer to the Client-side Events Filtering guide.
  • Mapping RudderStack events to the Criteo standard events: Enter the Event Name and the corresponding Standard Event from the dropdown. This standard event will be triggered when the mapped RudderStack event is called.
You can specify multiple Standard Events for one Event Name and vice versa.
  • Use device mode to send events: As this is a device mode-only destination, this setting is enabled by default and cannot be disabled .
  • OneTrust Cookie Categories: This setting lets you map OneTrust cookie /consent groups to RudderStack's consent purposes.


The page call lets you track the user's home page along with its associated properties.

Use this call only to track the home page and add the users to your target audience.

The home page tag will be fired in the following three scenarios:

  • When the name of the page call is home.
  • When the current URL of the web page is same as the Home Page URL specified in the RudderStack dashboard.
  • When the URL mentioned in the properties of the page call is same as the Home Page URL specified in the RudderStack dashboard.
The home page tag will not be fired in any other scenario.

A sample page call is as shown below:"category", "home", {
path: "path",
url: "url",
title: "title",
search: "search",
referrer: "referrer",
testDimension: "true",


The track call lets you capture different user events and the properties associated with them.

A sample track call is as shown:

rudderanalytics.track("Product Viewed", {
product_id: "Prod12345",
quantity: 1,
price: 19.99,
name: "my product",
category: "categ 1",
sku: "p-666",
list: "Gallery",
testDimension: true,
testMetric: true,

In the above example, RudderStack captures the information related to the Product Viewed event and the associated details such as quantity, price, category, etc.

The following table details the mapping of the RudderStack ecommerce events and the Criteo OneTag events.

RudderStack ecommerce eventCriteo OneTag eventOneTag Event Name Used By Criteo
Product ViewedProduct tagviewItem
Cart ViewedBasket/cart tagviewBasket
Order CompletedSales TagtrackTransaction
Product List ViewedCategory/keyword search/listing tagviewList
If the Category/keyword search/listing tag needs to be fired with the filters, enter it within the filters field of the event properties inside the Product List Viewed tag.

The filters field is an array of objects that consists of each filter category in every single object. Criteo expects name, operator, and value fields for every filter that needs to be passed to Criteo.

For example, a simple Product List Viewed event that fires a Category/keyword search/listing Tag is as shown:

rudderanalytics.track("Product List Viewed", {
email: "",
zipCode: "12345",
category: "abc",
keywords: "key",
page_number: 1,
filters: [
name: "processor",
operator: "eq",
value: "snapdragon",
products: [
product_id: "223344ffdds3ff3",
product_id: "343344ff5567ff3",


How do I get my Criteo Account/Partner ID?

To get your Criteo account/partner ID, follow these steps:

  1. Log into your Criteo account.
  2. In the left navigation bar, go to Event Tracking under Assets, as shown:
  1. Click Setup, followed by Direct Implementation.
  2. In the resulting loader file, you can find your 5-digit partner ID in the src key, as shown:

Contact us

For more information on the topics covered on this page, email us or start a conversation in our Slack community.

On this page