In this section you will learn:

  • How to connect or disable Criteo on your site.
  • How to check the correctness of the integration settings.
  • How to configure the sending of custom segments.

Criteo is a dynamic retargeting system. SegmentStream allows you to send data about the behavior of your users to Criteo.

Page contents


Introduction


With the help of SegmentStream, you can fully integrate Criteo with your site: events, hashed users’ email addresses, deduplication and so on.
Criteo integration guide

To configure integration with Criteo:

  1. Log in on the segmentstream.com website and go to the integration management panel
  2. Click on the “Integration” tab and click on the block with the Criteo logo.
  3. In the panel that opens, configure the integration.
    You can read more details about the settings below.

Required events and variables


For the correct operation of the integration of your site with Criteo - you must configure the filling of certain events in the digitalData.events array. The list of events is as follows:

Required events

It is also necessary to configure the filling of certain variables of the digitalData object. A list of some variables is given below:

  • page.type
  • product - the product object occurs in several places of the digitalData object: directly in digitalData.product, in the items and lineItems arrays of the listing, cart and transaction objects.
  • listing, cart, transaction objects
  • user.email or user.emailHash variables
  • and others

In the case of simultaneous filling of the variables user.email and user.emailHash, SegmentStream will send the value of the user.emailHash variable to Criteo. In the absence of user.emailHash, SegmentStream itself will hash the value of the user.email variable and send it to Criteo.

Criteo Account ID


The ID of your account can be checked with your Criteo account manager. As a rule, this is a five-digit number.

Product feed has grouped products


Criteo receives information about products placed on the site through an XML feed. With a certain interval, the Criteo robot downloads a feed from your server. This feed contains information about all products on the site.

Learn more about the feed format.

For correct integration, Criteo should also receive information about the interaction of users with products on the site - views, additions to the shopping cart, purchases, etc. The system must correctly match what it sees in the incoming events with the XML feed.

More about product groups

-If you use grouping of goods using the item_group_id xml-feed parameter - be sure to activate this setting.

In this case, the product id from your XML feed must match the product.skuCode of the digitalData object. Be sure to fill product.skuCode and product.id in each product.

-If you do NOT use grouping of goods using the item_group_id xml-feed parameter - do not activate this setting.

In this case, the product id from your XML feed must match the product.id of the digitalData object.

User segment


Criteo allows you to send user segments with each event. For example, if you want to completely disable retargeting for a specific segment of users - you need to create a numeric variable in the digitalData object and insert its address into the integration configuration field. For example, for all users on which you want to disable retargeting, you pass the value 1 to the variable digitalData.user.segment.criteoSegment. For the rest, 0. For more information about creating variables, see variables.

Use custom deduplication


Deduplication is an attribution setting that can be sent to Criteo along with the order. By default, this feature is disabled. This means that Criteo uses its own attribution model to set up its own machine learning algorithms.

The attribution model is the rule by which the value of the conversion/(order value) is redistributed between all sources of traffic that led the user to the site before buying. There is a large number of attribution models, the most common of these is last non-direct click. When using this model of attribution - 100% of the conversion value will be assigned to the last indirect source of traffic. For example, if a user first came to the site from a search, then from Criteo, then typed the URL in the browser - the whole value of the order will be assigned to the source of “Criteo”.

If you use “own deduplication”, SegmentStream will remember the source (the value of the GET parameter utm_source). If this value is “criteo”, the transaction will be attributed to the Criteo source.

Criteo deduplication parameter guide

Website has multiple currencies


Enable this feature if your website uses multiple currencies.

Checking the correctness of the integration setup


After configuring the integration in the SegmentStream interface, but before PUBLICATION - go to the site in test_mode, go through the conversion funnel and check for errors. If there are no errors - publish the current version.