Criteo Destination

Segment makes it easy to send your data to Criteo (and lots of other destinations). Once you've tracked your data through our open source libraries we'll translate and route your data to Criteo in the format they understand. Learn more about how to use Criteo with Segment.

Getting Started

Currently this destination supports events originating from Mobile or Web sources (not Server). You can read more about how define a source here.

Our web integration with Criteo is currently in public beta. Please use carefully andcontact us if you are having any issues.

To get started with Criteo and Segment, you’ll need:

  1. An existing account with Criteo.
  2. A data source integrated with either one of our mobile SDK’s (iOS or Android) or Javascript library (Analytics.js)

Assuming both of these criteria are met, you can add Criteo as a destination for your desired source in your Segment account.

If you are using our mobile integration with Criteo please ensure your app is properly registered with them.


Track

Criteo is built to help you track key purchase funnel events and details. To accomplish that, you’ll want to track your user’s actions using the following spec’d events to ensure you’re following Criteo’s best practices.

We use the context fields that we capture with our SDKs automatically to populate Criteo’s tag with the app’s name, user’s language, locale, userId, deviceType and deviceId so you just need to make sure that the event names and properties match up! Please refer to our common fields guide to identify which context fields we collect automatically for each of our client-side libraries (analytics.js, analytics-ios or analytics-android).

Product Viewed

When a user views a particular product or offering inside your application, you should call our Product Viewed event and we’ll map that to Criteo’s viewProduct tag. You’ll need to make sure that the products on your Product List Viewed event have a productId property. As with all our integrations, casing does not matter! Your properties can be camelCase or snake_case, both will work.

On web, the above Javascript example would result in the firing of the following Criteo tag:

window.criteo_q.push({ event: 'viewItem', product: '507f1f77bc' })

Product List Viewed

When a user views a list of products inside your application, you should call our Product List Viewed event and we’ll map that to Criteo’s viewListing tag. Same as above, make sure you have your item’s productId or product_id on the event!

On web, the above Javascript example would result in the firing of the following Criteo tag:

window.criteo_q.push({ event: 'viewList', product: ['1', '2'] })

Cart Viewed

When a user views their Cart or Order details inside your application, you should call our Cart Viewed event and we’ll map that to Criteo’s viewBasket tag.

You will need to have a products array of product objects in your Segment Cart Viewed event with at least id, price and quantity properties on each product object in that array.

On web, the above Javascript example would result in the firing of the following Criteo tag:

window.criteo_q.push({ event: 'viewBasket', product: [
    {
        productId: 1,
        price: '19',
        quantity: 6
    },
    {
        productId:2,
        price: '3',
        quantity: 2
    }
]})

Order Completed

When a user completes an order or purchase inside your application, you should call our Order Completed event and we’ll map that to Criteo’s trackTransaction tag.

You will need to have a products array of product objects in your Segment Order Completed event with at least id, price and quantity properties on each product object in that array. You also must pass an orderId.

On web, the above Javascript example would result in the firing of the following Criteo tag:

window.criteo_q.push({ event: 'trackTransaction', id: '098dsf098f', product: [
    {
        productId: '507f1f77bcf86cd799439011',
        price: '19',
        quantity: 1
    },
    {
        productId: '505bd76785ebb509fc183733',
        price: '3',
        quantity: 2
    }
]})

Application Opened

This is only relevant if you are using this integration for mobile. For the equivalent on web, see below.

Our Application Opened event will map to Criteo’s viewHome tag. This event is automatically collected by the latest versions of our SDKs so update if you haven’t already!

Page

Criteo’s viewHome tag tracks top of funnel visits to your site’s home page. We integrate with this functionality on web via the use of our .page method.

There are two ways of letting Segment know which .page event should trigger this tag:

  1. You can define the name argument in the .page method as ‘Home’:
analytics.page('Home')
  1. You can give us the URL of your home page as an integration setting. Please reference the settings section for more info.

Other Features

Extra Data

This functionality is currently only available via our web integration with Criteo. We are working on adding it for mobile.

Criteo supports the ability to send extra data with events about a page or user to supply your events with more context (This is a feature that is set up with the assistance of your Crtieo Account Manager).

To enable this functionality, you will need to provide us with the names of the Criteo data parameters you would like us to pass along as well as the name of the properties or traits of the Segment .page or .identify events that you would like us to map them from.

This is setup via the Supporting User Data and Supporting Page Data settings in your Criteo integration settings. In each of these, you can provide us with a list of key/value mappings designating the name of the Segment property/trait on the left and the corresponding Criteo parameter it should map to on the right.

Here is an example of Supporting Page Data:

supporting page data screenshot

Here is an example of Supporting User Data:

supporting user data screenshot

Once this is complete, we will do the following:

We will compare the properties of any .page events you invoke with the Supporting Page Data mappings. If a match is found, we will set the values of those properties as the values of Criteo data parameters you defined and pass them along with any future events that occur on the page. If you are using this functionality, please ensure the .page event is being invoked on the page before any subsequent .track events.

For example, if you set the page event mappings defined above and triggered a page event like this:

analytics.page('Team Page', { team: 'New York Giants' })

And then on that same page triggered one of the .track events documented above (Product Viewed for example) the subsequent Criteo tag would look like this:

window.criteo_q.push({ event: 'viewItem', product: 'PRODUCT-ID', team_page: 'New York Giants' })

Because identify events cache any user traits you’ve specified in localstorage, we can do a similar lookup as above with the Supporting User Data mappings. If there are any matches, we will pass that data along as their corresponding Criteo data parameters.

For example, if you set the trait mappings defined above and had, at some point, previously triggered an identify event like this:

analytics.identify('userId', { subscriptionStatus: 'trial' })

Any future .track events documented above would have sub_status as an extra data parameter (assuming the user had not cleared their localstorage). Here’s the same viewItem event as an example:

window.criteo_q.push({ event: 'viewItem', product: 'PRODUCT-ID', sub_status: 'trial' })

Note: Of course if you later change the user’s subscriptionStatus to be a different value via the use of another identify call, the sub_status value will also be updated.

Setting Emails

It’s easy to associate emails with a user, if there’s an email property in a track call, we’ll include the setHashedEmail event to Criteo along with your event. We’ll take care of hashing it for you

Criteo Data Centers

Criteo has multiple data centers to better serve global companies and we will automatically infer from your users’ devices which data center to send the data to for you so you don’t need to worry about it!

Troubleshooting

Sending Dates

Criteo can receive dates in a specific format, in order for us to pass along dates to Criteo, make sure you follow the spec laid out in our Spec

FAQ

Is the mobile integration bundled?

Even though we don’t support integrating with Criteo via Segment from a server source, it’s still not necessary for you to bundle the Criteo SDK into the Segment SDK! This is because while our mobile integration with them is powered from our servers, the integration requires metadata that can only be supplied by the user’s mobile device (which is collected and passed along automatically by the Segment mobile SDK).


Supported Sources and Connection Modes

WebMobileServer
📱 Device-based
☁️ Cloud-based

To learn more about about Connection Modes and what dictates which we support, see here.

Settings

Segment lets you change these destination settings via your Segment dashboard without having to touch any code.

Account ID

Criteo Account ID

Home Page URL

The full URL of your website’s Home page. This settings is only necessary if the path of your home url is not the standard root path (ie. ‘/‘). Navigation to this page will trigger Criteo’s viewHome tag.

Supporting Page Data

Specify the property names of your Segment page event on the left and the corresponding Criteo data parameter you would like us to map it to on the right. Please reference our documentation for more info on this feature. Please note, this setting is only applicable if you are using our web integration with Criteo which is currently in beta.

Supporting User Data

Specify the Segment trait names on the left and the corresponding Criteo data parameter you would like us to map it to on the right. Please reference our documentation for more info on this feature. Please note, this setting is only applicable if you are using our web integration with Criteo which is currently in beta.


If you have any questions or see anywhere we can improve our documentation, please let us know or kick off a conversation in the Segment Community!