Supplier User Matching
Adagio and Suppliers rely on user matching to help Buyers assess user value, enabling more relevant ad placements and optimised monetisation. Effective cookie syncing can boost CPM and media spend, benefiting both parties. Follow the guidelines in the sections below to optimize user matching.
Requirements
Only works with users who have enabled cookie storage.
The publisher should provide a redirection URL.
The publisher needs to load the Adagio user matching URL into an iframe.
User Sync URLs
The Supplier initiates user syncing by creating an iframe with one of the following URLs.
Adagio provides one URL per region. For legal reasons, Users IDs are not shared between regions, so the User Sync and the Auctions must happen in the same region.
Example: User syncing for a Canadian user's device would be done via the Adagio AMER data center. All Auctions for this same user would be done via the Adagio AMER data center.
Parameters
r
Yes
The redirect URL provided by the Publisher
domain
Highly Recommended
The website domain where the user sync is initiated. (example: a.domain.com)
gdpr
Yes if applicable
GDPR status
gdpr_consent
Yes if applicable
GDPR Consent string
us_privacy
Yes if applicable
US Privacy string
gpp
Yes if applicable
GPP string
gpp_sid
Yes if applicable
GPP section id(s) in force for the current transaction
For instance, the final URL for EMEA including the different parameters set should look like this:
https://u-ams.4dex.io/ortb/usync.html?publisher_id=1000&domain=my.domain.com&gdpr=0&gdpr_consent=&us_privacy=1YYN&r=https://yourendpoint.com/setuid?us_privacy=1YYN&uid={UID}
User ID Macro
Insert a User ID macro in the redirect URL for Adagio to substitute with the final User ID.
The User ID macro is:
{UID}
Sample URL with macro:
https://yourendpoint.com/setuid?gpdr=0&gdpr_consent=&us_privacy=1YYN&uid={UID}
Sample URL with macro replaced:
https://yourendpoint.com/setuid?gpdr=0&gdpr_consent=&us_privacy=1YYN&uid=QHJ1Ok0yOFZLTUg4LU0tQzBSUjoyMDA0M3xwdToyQTM1RTg2OS0wQTM5LTQ4QTItQUM0NS1DNjkzOThBOUQ0OEE6MjAwNDM=
Cookie Expiration
The cookie remains valid for 30 days. To keep the identifiers up to date, renew it before it expires. Adagio will disregard expired user IDs.
Passing the User IDs in the Bid Request
Adagio User ID
If user matching succeeded and the user id is not expired, the bid request must include the user ID in the User
object's buyeruid
attribute.
Example:
{
"user": {
"buyeruid": "QHJ1Ok0yOFZLTUg"
}
}
Other bidders' User IDs
Cookie matching is done asynchronously and must be done incrementally to optimise devices' resources. It's therefore imperfect.
If you already have the User ID of bidders monetising through the Adagio Demand Library, then it is recommended adding them to your Bid Request.
{
"user": {
"ext": {
"eids": [
{
"source": "openx.com",
"uids": [
{
"id": "6f492e90-621e-45a3-8f71-bcc9721a4279",
"atype": 1
}
]
}
]
}
}
}
Below you'll find the source that must be set for each of Adagio's Demand Library's bidder:
Magnite / Rubicon
rubiconproject.com
Pubmatic
pubmatic.com
OpenX
openx.com
or openx.net
Sovrn
sovrn.com
TripleLift
triplelift.com
Equativ / Smart
smartadserver.com
ImproveDigital
improvedigital.com
Freewheel
freewheel.com
OneTag
onetag.com
RTB House
rtbhouse.com
Aidem
aidem.com
Nexxen / Unruly
unrulymedia.com
33Across
33across.com
ConnectAd
connectad.io
E-Planning
e-planning.net
Illumin / AcuityAds
acuityads.com
Insticator
ingage.tech
Last updated
Was this helpful?