Browse the documentation

Header Bidding — Cookie Sync

Hosts: {rtb_domain} is your network's RTB domain, used by the bidder endpoints; a network without a dedicated RTB domain uses its ad domain there. {ad_domain} is the network's ad-serving domain. Inside the panel both are filled in for you.

Persistent user identifier so DSP-side targeting can match the same visitor across auctions. Two endpoints: /openrtb2/sync drops our own cookie; /setuid is the standard Prebid bidder-cookie set.

/openrtb2/sync#

GET request. Drops a goadserver_uid cookie (UUIDv4, max-age 1 year, SameSite=None + Secure). Subsequent OpenRTB requests we send to downstream DSPs include this id as user.id. Macros: {gdpr} / {gdpr_consent} / {us_privacy} are passed through from Prebid's sync chain.

URL

GET https://{ad_domain}/openrtb2/sync?gdpr={gdpr}&gdpr_consent={gdpr_consent}&us_privacy={us_privacy}

/setuid#

GET request. Standard Prebid Server setuid endpoint — DSPs redirect users here with their bidder code + uid so we can map their cookie to ours. Returns a 1×1 GIF.

URL

GET https://{ad_domain}/setuid?bidder={bidder_code}&uid={dsp_uid}&gdpr={gdpr}&gdpr_consent={gdpr_consent}