The redirect cookie sync method is initiated from your traffic and is the most optimal approach for cookie syncing — and is required for oRTB implementations. Because the sync fires on every request (not just when Sovrn wins an impression), your partner always holds the user ID mapping and match rates stay as high as possible.
How it works
You initiate the sync by sending a request to Sovrn's cookie sync endpoint, including a redirect URL with the $UID macro placeholder. Sovrn replaces $UID with a Sovrn Reader ID and redirects accordingly.
Sovrn sync pixel
Sovrn will provide you with a sync pixel pre-configured with custom parameters. The base format is:
https://ap.lijit.com/pixel?gdpr=${GDPR}&gdpr_consent=${GDPRString}&redir=URLEncodedRedirectString
Before using this pixel, you must update the redir parameter with your URL-encoded redirect pixel.
Parameters
|
Parameter |
Description |
|
|
GDPR flag — pass |
|
|
TCF 2.0 consent string |
|
|
URL-encoded redirect pixel from the partner. Append |
The gdpr and gdpr_consent parameters are populated by the publisher. Only redir needs to be configured by Sovrn before the pixel is sent.
Server-side macro
|
Macro |
Description |
|
|
Populates the Sovrn Reader ID (Sovrn cookie) |
Cookie sync response behavior
Once the sync request is received, Sovrn handles it as follows:
-
Successful match — the redirect fires with
$UIDreplaced by Sovrn's user ID for that reader. -
New reader (no cookie yet) — Sovrn will attempt a self-redirect to set the reader cookie before completing the sync.
-
DNT enabled — the redirect fires with
$UIDreplaced by an empty string. -
Match failure — the redirect fires with
$UIDreplaced by an empty string. -
Missing or empty redirect URL — Sovrn returns a
204response. -
Unexpected error — Sovrn returns a
204response.
Questions? Concerns? Our team would be more than happy to help. Reach out to our Support Team here.