Cookie sync settings: Source Level

Adtelligent supports cookie syncing with publishers to ensure users are identified and matched before bid requests are made. This configuration helps maximize bid eligibility and reduce traffic loss due to missing user IDs.

Cookie syncing with a publisher is handled through two coordinated mechanisms:

1. Cookie Sync Settings – defines how and where we send user ID syncs.

2. Cookie Sync Warmup Settings – provides a preloading mechanism to initiate the sync from the publisher’s site.

🔧 Cookie Sync Settings

This section determines how Adtelligent shares its user ID with the publisher.

1. CookieSync Initiator

Set this to:

• ✅ Adtelligent – this means Adtelligent will initiate the sync call to the publisher.

⚠️ This should always be set to Adtelligent for syncing with publishers.

2. CookieSync URL

Enter the publisher’s sync endpoint. This is the URL where we will send the sync call, including our user ID.

• The URL must include the {uid} macro, which Adtelligent replaces with our actual cookie ID. 

⚠️ This URL doesn't need to be encoded. 

• Example:

https://sync.publisherdomain.com/user_sync?ssp_id=adtelligent&user_id={uid}

Click Reset to clear the field.

3. Enable NBR response for unsynced request

Optional. If enabled, Adtelligent will return a No Bid Reason (NBR) when the user ID has not been synced with the publisher. This helps diagnose why certain impressions did not receive bids due to missing cookie sync.

🔄 Cookie Sync Warmup Settings

This section defines how the sync is triggered from the publisher’s site before the ad request is sent, also known as warmup syncing.

1. Sync type

Choose the mechanism used on the publisher’s site:

• ✅ iFrame – (recommended) uses an invisible iframe to preload the sync

• ⬜ Script – alternate method using JavaScript (less common)

2. Integration Script

This field provides a ready-to-use iframe snippet that the publisher must place on their website:

<script type="text/javascript" src="https://s.adtelligent.com/sync.js?aid=xxxxxx"></script>

<iframe src="https://s.adtelligent.com/sync.html?aid=xxxxxx" style="display:none;visibility:hidden"></iframe>

🔄 Full Cookie Sync Flow with Publisher

1. The publisher integrates the Integration Script from Cookie Sync Warmup Settings into their page.

2. When the page loads:

   • The iframe sends a request to:

https://s.adtelligent.com/sync.html?aid=xxxxxx or https://s.adtelligent.com/sync.js?aid=xxxxxx

• Adtelligent then redirects to the CookieSync URL, replacing {uid} with our actual cookie ID.

2. The publisher receives the call and stores our UID on their side.

✅ Adtelligent is always the initiator in this process. This must be the default behavior for publisher integrations.

✅ Summary