This article describes the requirements for enabling a cookie sync between Criteo's 3rd-party "userid" and AudienceStream (AS). The cookie sync is a pixel tag that will be configured in Tealium iQ (TiQ).
In this article:
Please note cookie-sync tags will cause events to be sent to AudienceStream. If you have not configured the tag correctly this can cause a surge of events.
if you are concerned that you have not set this up correctly please reach out to our support team to assist you before going live.
The cookie sync tag will cause a chain of redirects (described later) where AS will eventually receive the Criteo "userid". This will be in the form of a parameter called "userid". This variable needs to added in Tealium iQ so that you can leverage it for Rules and Attributes in AS.
The utag_main_dc_event cookie must be declared so that later we can create a Load Rule for the cookie sync tag.
Note: the Criteo One Tag must exist in the TiQ profile before the cookie sync tag can be configured.
Publish to Production so that the Criteo "userid" is available to AS and the functionality can be tested.
If the AS Visitor ID equals
014c0997b79e00152f6525804ed915078002e07000fb8 a sample call in the browser will look like:
The above call will hit Criteo's server where it will perform a redirect to AudienceStream's server. The redirect will grab the
tealium_vid parameters and append them to the URL. The redirect will also grab the Criteo userid and pass it along in the "userid" parameter. Here is a sample call: