Help Center

General How To

Gamoshi Cookie Sync Integration Guide

This document outlines the required information and format for cookie synchronization between Gamoshi and demand/supply partners. Gamoshi cookie sync is based on the prebid.org cookie syncing methodology.

For Demand and Supply Partners

Cookie syncing allows Gamoshi and its partners to recognize the same user across platforms. This enables better match rates, improved targeting, and accurate tracking for demand and supply integrations.

PART 1: Syncing a Demand Partner (DSP)

What You Need from the DSP

Field	Description
Bidder Name	Internal identifier (prebid.org bidder name) used in Gamoshi (e.g., `adnxs`, `pubmatic`). If the bidder is not part of Prebid, ask your account manager to add it manually.
Partner Cookie Sync URL	The URL Gamoshi should redirect users to for syncing. Example: `https://ib.adnxs.com/getuid`
User ID Macro	The macro the partner uses to insert their user ID (e.g., `$UID`, `%USER_ID%`, `{uid}`)

The complete list of supported bidders is here.

Gamoshi Cookie Sync Endpoint

To be used by the DSP to redirect users to Gamoshi:

https://[yourbidderdomain]/setuid?bidder=<BIDDER_NAME>&gdpr=[GDPR]&gdpr_consent=[CONSENT]&uid
=<PARTNER_USER_ID_MACRO>

Example (AppNexus):

https://[yourbidderdomain]/setuid?bidder=adnxs&gdpr=[GDPR]&gdpr_consent=[CONSENT]&uid=$UID

Full DSP Sync URL

This is the final redirect URL the partner uses:

<PARTNER_COOKIE_SYNC_URL>?<URL_ENCODED_GAMOSHI_SYNC_URL>

Example (AppNexus):

https://ib.adnxs.com/getuid?https%3A%2F%2F[yourbidderdomain]%2Fsetuid%3Fbidder%3Dadnxs%26gdpr%3D[GDPR]%26gdpr_consent%3D[CONSENT]%26uid%3D%24UID

Special Note for DSP Partners

If a partner platform only wants Gamoshi to store their user IDs—meaning they do not intend to return Gamoshi’s user ID in their RTB bid requests—they must explicitly request that Gamoshi enable this behavior for their bidder name.

This ensures that Gamoshi retains the mapping between user IDs, even if the partner does not pass Gamoshi’s ID back during programmatic bidding.

Please coordinate with your Gamoshi account manager to activate this setting during integration.

Alternative User Sync Method (Client-Side Integration)If you have access to the web page or are running client-side JavaScript, an easier alternative for syncing your demand partners is to use the User Sync iframe that we provide.

This solution follows the standard practices established by the Prebid Server community and offers a simple, efficient way to initiate cookie syncing directly from the user’s browser.

PART 2: Syncing a Supply Partner (SSP)

Gamoshi-Initiated Cookie Sync

Gamoshi can initiate syncing by calling:

https://[yourbidderdomain]/user_sync?bidder=&gdpr=<0_or_1>&consent=&us_privacy=&rurl=<ENCODED_REDIRECT_URL>

Optional: Redirect URL (`rurl`)

Use rurl If you’d like Gamoshi to redirect back to your system after syncing.
The URL can contain the placeholder [gusr], which will be replaced with Gamoshi’s internal user ID.

Example:

https://[yourbidderdomain]/user_sync?bidder=openx&gdpr=0&consent=&rurl=https%3A%2F%2Fwww.openx.com%2Fcallback%3Fuid%3D%5Bgusr%5D

This results in:

https://www.openx.com/callback?uid=<GAMOSHI_USER_ID>

Parameters Reference

Parameter	Description
`bidder`	The name used internally by Gamoshi,(Prebid.org bidder name)
`gdpr`	`0` (not subject) or `1` (subject)
`consent`	GDPR consent string (TCF v2)
`us_privacy`	CCPA string (optional)
`rurl`	(Optional) redirect URL with `[gusr]`

SSP-Initiated Sync to Gamoshi

If your SSP platform wants to trigger the sync:

https://[yourbidderdomain]/user_sync?bidder=&rurl=<encoded_url_with_[gusr]></encoded_url_with_[gusr]>