Quick Help

The knowledgebase is a categorized collection of answers to frequently asked questions (FAQ) and articles. You can read articles in this category or select a subcategory that you are interested in.



 Prebid Server cookie sync integration

Solution

Cookie Sync User Manual — PixFuture
User Manual Cookie Sync PixFuture

Cookie Sync User Manual

How to integrate with the PixFuture /cookiesync endpoint for PBS adapter synchronization and optional demand-partner synchronization.

Production URL: https://sync.pixfuture.com/cookiesync

Methods: GET, HEAD (OPTIONS for CORS)

Related auction: https://pbs-pix.pixfuture.com/pixservices

Contents

  1. What it does
  2. Mode A — Adapter redirect sync
  3. Mode B — Partner sync
  4. Privacy rules
  5. Cookie written
  6. Status codes
  7. Quick tests
  8. How this ties to auctions
  9. Recommendations

1. What it does

Sets a first-party Pixfuture user id cookie (pixfuture_uid on .pixfuture.com) and either:

  1. Adapter redirect sync — returns the user to publisher PBS /setuid (this is what pixfuture.yaml uses), or
  2. Partner sync — returns HTML that fires demand-partner sync pixels for a given pix_id.

2. Mode A — Adapter redirect sync (primary / PBS)

Used by Pixfuture PBS userSync:

userSync:
  redirect:
    url: "https://sync.pixfuture.com/cookiesync?gdpr={{.GDPR}}&consent={{.GDPRConsent}}&us_privacy={{.USPrivacy}}&redirect={{.RedirectURL}}&gpp={{.GPP}}&gpp_sid={{.GPPSID}}"
    userMacro: "${UID}"

Required parameters

ParamDescription
redirect (or redir)Publisher PBS setuid URL; must contain ${UID} (or a supported UID macro)

Optional privacy parameters

ParamDescription
gdpr0 or 1
consent (or gdpr_consent)TCF 2.x string (required when gdpr=1)
us_privacyCCPA string
gpp, gpp_sidGPP privacy strings

Flow

Browser → GET /cookiesync?gdpr&consent&redirect=<PBS /setuid?...&uid=${UID}> → Set-Cookie: pixfuture_uid=<uuid> → 302 Location: <PBS /setuid?...&uid=<same uuid>>

Example

curl -sS -D - -o /dev/null \
  "https://sync.pixfuture.com/cookiesync?gdpr=0&consent=&us_privacy=&redirect=$(python3 -c 'import urllib.parse; print(urllib.parse.quote("https://pbs-dev.pixfuture.com/setuid?bidder=pixfuture&uid=${UID}"))')"
Success: 302 + Set-Cookie: pixfuture_uid=… + Location with a real UUID (no ${UID} left).

3. Mode B — Partner sync (pix_id)

Optional helper for matching demand partners for a publisher zone. Not the PBS adapter userSync from pixfuture.yaml.

Required parameters

ParamDescription
pix_id (or pixid)Publisher zone ID assigned by PixFuture

Same privacy parameters as Mode A (gdpr, consent, us_privacy, gpp, gpp_sid).

Flow

Browser → GET /cookiesync?pix_id=62623&gdpr=0 → Identify eligible demand partners for the publisher zone → Generate partner synchronization requests → 200 HTML with hidden iframe/img partner pixels → Set-Cookie: pixfuture_uid

Example

curl -sS -D - \
  "https://sync.pixfuture.com/cookiesync?pix_id=62623&gdpr=0" | head
Success: 200 text/html titled “Partner Cookie Sync”, with partner iframes/images.

4. Privacy rules

ConditionResult
gdpr=1 and missing/invalid consent400 / 403 — no cookie, no redirect
gdpr=1 and TCF lacks Purpose 1 or Vendor 839403
gdpr=0 or gdpr omittedGDPR check skipped
us_privacy=1YYN403 CCPA opt-out

Consent query aliases: consent, gdpr_consent (partner mode also accepts adsync).

Pixfuture IAB GVL vendor ID: 839.

AttributeValue
Namepixfuture_uid
Domain.pixfuture.com
Path/
FlagsHttpOnly, Secure, SameSite=None
Lifetime1 year

If the browser already has a valid UUID cookie, it is reused; otherwise a new UUID is created.

6. Status codes

CodeMeaning
302Adapter redirect sync OK
200Partner sync HTML OK
204CORS preflight (OPTIONS)
400Missing redirect/pix_id, bad URL, or missing GDPR consent when gdpr=1
403TCF / CCPA blocked
405Method not GET/HEAD
5xxTemporary service error (partner sync)

7. Quick tests

Adapter sync (expect 302)

curl -sS -o /dev/null -D - \
  "https://sync.pixfuture.com/cookiesync?gdpr=0&redirect=https%3A%2F%2Fpbs-dev.pixfuture.com%2Fsetuid%3Fbidder%3Dpixfuture%26uid%3D%24%7BUID%7D"

Missing params (expect 400)

curl -sS "https://sync.pixfuture.com/cookiesync?gdpr=0"

Partner sync (expect 200 HTML)

curl -sS "https://sync.pixfuture.com/cookiesync?pix_id=62623&gdpr=0" | head -c 200

8. How this ties to auctions

After synchronization, the publisher's PBS can associate the PixFuture user ID using /setuid. During subsequent auctions sent to https://pbs-pix.pixfuture.com/pixservices, this mapping can be used for buyer identification through OpenRTB fields such as user.buyeruid or user.ext.prebid.buyeruids, when applicable.

9. Recommendations

  • Use Mode A for normal PBS Pixfuture userSync.
  • Use Mode B only when you explicitly want partner-pixel HTML for a zone.
  • For GDPR traffic, ensure the TC string grants Purpose 1 and vendor 839.
  • Use the production synchronization endpoint https://sync.pixfuture.com/cookiesync.
Note: Adapter redirect sync is image/redirect style (302). Partner sync returns HTML with iframes/images for demand partners — that is a different path from the Pixfuture PBS userSync config.
PixFuture · Cookie Sync User Manual