Documentation

Consent Management

You can integrate consent management in multiple ways:

  1. By passing consent via query parameters.
  2. By sending opt-out information in bulk (CSV delivery via email).
  3. By pointing your users to our privacy preferences page where they can opt-out of personalization and data sharing as well as make a Data Subject request.

❔Query parameters

You can pass consent through query parameters. In order to do so, you will need to capture and store consent information inside your ESP and pass it as a custom macro value in the image and click URLs.

Query parameterDescription
us_privacyUS privacy string following the IAB standard.

For example, 1YNN for version 1 of the US privacy string, where the user has been provided notice, has not made a choice to opt-out of data sale and where the digital property is not operating under the Limited Service Provider Agreement.
rdp1 if Restricted Data Processing should be enabled for this request, 0 otherwise.
gdpr1 if the user is subject to the GDPR, 0 otherwise. We will perform our own checks and override the value if the user is believed to be subject to the GDPR (although it will never downgrade if you passed 1)
gdpr_consentThe TCFv2 consent string

🚧

GPP Support

We are working on GPP support as a replacement for passing discrete consent signals (US privacy, TCFv2, RDP)

TCFv2 Vendors

In order to acquire consent for Google Ad Manager or Programmatic, you will need to acquire consent from users via your CMP.

Google Ad Manager (if configured for your placements)

  • Google: 755

Programmatic / Direct demand

  • Open Web Technologies Ltd: 280
  • ADYOULIKE SA: 259

Global Privacy Control

In addition to query parameters, we supports GPC signals from the user Browser, via the Sec-GPC header. No additional integration is necessary to support this feature.

AdServe / Google Ad Manager integration

When using the AdServer product, we will pass through all consent signals to GAM:

  • GPC header (Sec-GPC)
  • US Privacy string (us_privacy)
  • Reduced data processing (rdp)
  • TCFv2 consent string (gdpr and gdpr_consent)

Publishers can configure how GAM is using the information or override the defaults to restrict data processing globally.

Preferences pages & bulk delivery

See the information on our opt-out & DSR requests page.

Updated 8 months ago