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.
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:
- Log in on the segmentstream.com website and go to the integration management panel
- Click on the “Integration” tab and click on the block with the Criteo logo.
- In the panel that opens, configure the integration.
You can read more details about the settings below.
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:
- Viewed Page
- Viewed Product Detail
- Viewed Product Listing
- Searched Products
- Viewed Cart
- Completed Transaction
It is also necessary to configure the filling of certain variables of the
digitalData object. A list of some variables is given below:
product- the product object occurs in several places of the
digitalDataobject: directly in
digitalData.product, in the
lineItemsarrays of the
- and others
In the case of simultaneous filling of the variables
user.emailHash, SegmentStream will send the value of the
user.emailHashvariable to Criteo. In the absence of
user.emailHash, SegmentStream itself will hash the value of the
user.emailvariable and send it to Criteo.
The ID of your account can be checked with your Criteo account manager. As a rule, this is a five-digit number.
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.
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.
Activate this setting the product id from your XML feed matchs the
product.skuCode of the
digitalData object. Be sure to fill
product.id in each
Do not activate this setting if the product id from your XML feed matches the
product.id of the
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.
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.
Enable this feature if your website uses multiple currencies.
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.