ID5 Help Center

Initiate a Cookie Sync to ID5

Process Overview

ID5 will provide you with a pixel that you can drop along side other code you may deliver to publisher pages, such as a creative or other pixels. The ID5 pixel will call us with your UID included in the querystring and then initiate a synchronisation process with other platforms that you have allowed.

  1. When you have access to a user’s browser (via client-side tags, delivering a creative, etc.), you drop our pixel on the page
  2. ID5 servers receive the request, store your UID, and determine the best platform to sync with (respecting your preferences and optimised by our algorithms)
  3. ID5 redirects the request to this platform who in turn redirects back to ID5 with their UID
  4. ID5 repeats steps (2) and (3) until we have no more platforms to sync with or the number of cascades you have allowed is reached
  5. If you specify a callback url, ID5 will then call the URL provided

ID5 Cookie Sync Pixel URL

URL Parameters

Parameter
Type
Description
id5AccountNum
Integer
Your ID account number, provided by ID5
numCascadesAllowed
Integer
Number of additional platform calls allowed on the back of the initial synchronisation call to ID5 (step (4) above). We recommend setting this value to 9.
puid
String
Your unique ID for the user, encoded as a url parameter
gdpr
Integer (optional)
Whether or not GDPR applies to this request. Accepted values are 0 or 1.
gdpr_consent
String (optional)
A valid IAB TCF consent string. If the string is missing, misconstructed, or otherwise invalid, we will treat the request as if it has no consent string and process accordingly.
callback
String (optional)
A URL-encoded url that we will return back to at the end of the cascade chain. If you would like to receive the ID5 ID in this callback, include the macro {ID5UID} (properly encoded as %7BID5UID%7D) in your url where you’d like to receive it).

Pixels with a Callback

If you would like to use the callback feature or if you would like to retrieve the ID5 ID, please let your ID5 representative know so we can configure your account accordingly. When executing usersync with a callback url, ID5 will first cascade to available partners like usual, before issuing a 302 redirect back to the url you provided. However, there are a few cases when ID5 will NOT redirect back to the url provided, and instead, issue a 204 response.

Cases when ID5 will issue a 204 instead of calling the callback url:

  1. You did not have a proper legal basis to process user data (ex: in Europe, you provided a consent string but you did not have consent for Purpose 1)
  2. The user has opted out of ID5 (by visiting our Privacy Preferences Center)
  3. We detected that the user is blocking third party cookies