Process Overview

---

While third-party cookies are still in use, ID5 can synchronize with ad tech vendors to enhance user recognition, improving audience addressability and monetization.

ID5 can provide a pixel that can be added to publisher or advertiser pages or dropped alongside other code, like creatives or additional pixels. It can be deployed by a media owner or any ad tech vendor with access to a publisher's page. The pixel sends a request to ID5 with your UID (optional) to initiate a cookie synchronization with approved platforms. ID5 takes user consent into account when determining whether to initiate a cascade and in choosing which platforms to sync cookies with.

1. When you have access to a user’s browser (via client-side tags, delivering a creative, etc.), drop our pixel on the page
2. ID5's servers receive the request, store your UID (optional), and determine the best platform to sync with (respecting user privacy choices and your preferences, and optimized 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 with a User ID

---

https://id5-sync.com/s/[id5AccountNum]/[numCascadesAllowed].gif?puid=[encodedPlatformUid]&gdpr=[gdprFlag]&gdpr_consent=[tcfConsentString]&gpp=[gppConsentString]&gpp_sid=[gppApplicableSection]&us_privacy=[usPrivacy]&callback=[callbackUrl]

URL Path Parameters

Querystring Parameters

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

Example Implementations

In all examples below, we use AABBC12345 as the user ID that you would like to send to ID5.

Standard pixel

Pixel with callback

Callback URL: https://dummyimage.com/600x250&text=HelloWorld

Pixel with callback receiving the ID5 ID

Callback URL: https://dummyimage.com/600x250&text=%7BID5UID%7D

Initiate by Cookie Sync Pixel URL without a User ID

If you have access to the page you can simply add a pixel tag with URL:

or add an iframe with URL:

This endpoint will drop an initial pixel and allows the inclusion of additional pixels, configurable in the ID5 console. For more details or assistance with configuring additional pixels, please contact your ID5 Account Manager or reach out to support at [email protected].

URL Path Parameters

Querystring Parameters

Pixel URL

https://id5-sync.com/i/113/9.gif

Standard Pixel

<img src="https://id5-sync.com/i/113/9.gif" style="display:none;" height="0" width="0" id="id5-pixel"/>

See a working example on the sample page.

Adding a pixel with JavaScript

    function firePixel(url) {
    let img = new Image();
    img.src = url;
    }

    (function () {
    let syncUrl = "https://id5-sync.com/i/113/9.gif"
    if (document.readyState !== 'loading') {
      firePixel(syncUrl);
    } else {
        document.addEventListener('DOMContentLoaded', function () {
        firePixel(syncUrl);
      });
    }
    })();
		

See a more advanced example with GDPR consent collecting on the sample page

Adding a pixel as an iFrame

<iframe src="https://id5-sync.com/iwp/113/9.html"/>

Initiate by ID5-API.JS (Publisher)

If you have integrated our id5-api.js on your page, user syncing will automatically initiate user syncing once the ID5 ID has been provisioned to the page. No additional user sync integration is required. You can configure the maximum number of syncs using the maxCascades property. If you have your own proprietary user ID, you can pass it to the ID5 API via the partnerUserId configuration property. More details can be found here.