# Supply Cookie Sync

### Overview

The **Supply Cookie Sync** mechanism allows **Quantive** to map user identifiers between supply partners (publishers) and Quantive's demand partners to enable personalized advertising and measurement. This process is privacy-compliant and supports major consent frameworks such as GDPR and CCPA.

### Sync URL

To perform a sync, the following URL should be called via an `<iframe>` on the publisher's page:

```url
https://static.qntv.io/sync.html?gdpr=[GDPR]&gdpr_consent=[GDPR_CONSENT]&us_privacy=[US_PRIVACY]&gpp=[GPP]&gpp_sid=[GPP_SID]&redi=[REDIRECT_URL][XUID]
```

### URL Macro Reference

| Parameter      | Description                                                                   |
| -------------- | ----------------------------------------------------------------------------- |
| `gdpr`         | Indicates if GDPR applies (`0` = No, `1` = Yes).                              |
| `gdpr_consent` | Encoded IAB TCF consent string (if GDPR applies).                             |
| `us_privacy`   | CCPA/US Privacy string, typically in IAB format (e.g., `1YNN`).               |
| `gpp`          | Global Privacy Platform (GPP) encoded string.                                 |
| `gpp_sid`      | GPP Section ID, indicating applicable consent frameworks (e.g., `7` for TCF). |
| `redi`         | **URL-encoded redirect URL** which will be called after sync completes.       |
| `[XUID]`       | Placeholder that will be replaced with the **user ID** during the sync.       |

#### Example&#x20;

```url
https://static.qntv.io/sync.html?gdpr=1&gdpr_consent=CONSENT_STRING&us_privacy=1YNN&gpp=GPP_STRING&gpp_sid=7&redi=https%3A%2F%2Fpartner.com%2Fsetuid%3Fuid%3D[XUID]
```

#### Notes

* The `redi` parameter **must be URL-encoded** before being inserted into the sync URL.
* The `[XUID]` macro should be included within the encoded redirect URL and will be replaced dynamically with the user ID during the sync.

***

### Providers

#### List of already approved providers

* Sovrn
* Inmobi
* Magnite
* AdpatMx
* Xandr (Microsoft Monetize)
* Nexxen (Unruly)

#### Adding a new provider

To add a new provider contact your account manager to approve the provider name.\
Once the provider name is approved share the following URL for the provider redirect:&#x20;

```url
https://sync.qntv.io?provider=[PROVIDER_NAME]&uid=[USER_ID]
```

***

### Publisher Requirements

To complete the cookie sync, **publishers are required to host the user ID matching table** on their end. \
This table is used to map between **Quantive's** user ID and the publisher’s internal user ID system.

**Requirements:**

* The matching table must be up-to-date and served from a reliable endpoint.
* The redirect URL should include a dynamic placeholder (`[XUID]`) which Quantive will replace during the sync.
* Proper CORS and caching policies should be applied to ensure efficient and secure delivery.

### OpenRTB Integration

Once the sync is complete, the **user ID provided by Quantive** must be included in the OpenRTB request payload under the following field:

```json
"user": {
  "buyeruid": "QUANTIVE_USER_ID"
}
```

This ensures Quantive can identify and target the user appropriately in programmatic transactions.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.privateadserver.com/ssp/supply-cookie-sync.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.