Privacy & Consent

The Nexx360 Instream Player supports GDPR/TCF v2 and US Privacy (CCPA) consent signals. When provided, these values are included in the OpenRTB bid request sent to the auction endpoint.

GDPR / TCF v2

Pass the GDPR flag and the TCF v2 consent string via the init() configuration:

nexx360InstreamPlayer.init({
  tagId: 'your-tag-id',
  container: 'video-ad',
  gdpr: '1',
  gdprConsent: 'CPceAEAPceAEAAHABBENCgCsAP_AAH_AAAAAIhtf_X__b3...'
});
Property
Type
Description

gdpr

string

'1' if GDPR applies, '0' if not

gdprConsent

string

TCF v2 consent string from your CMP

How It Flows into the Bid Request

When gdpr is '1' and gdprConsent is provided, the library sets:

{
  "regs": {
    "ext": {
      "gdpr": 1
    }
  },
  "user": {
    "ext": {
      "consent": "CPceAEAPceAEAAHABBENCgCsAP_AAH_AAAAAIhtf_X__b3..."
    }
  }
}
circle-info

If gdpr is not '1' or gdprConsent is not provided, the user.ext.consent field is omitted from the bid request.

US Privacy (CCPA)

Pass the US Privacy string via the init() configuration:

Property
Type
Description

usPrivacy

string

US Privacy string (e.g. '1YNN')

How It Flows into the Bid Request

When usPrivacy is provided, the library sets:

Combined Example

Both GDPR and US Privacy can be passed together:

This produces the following in the bid request:

Last updated

Was this helpful?