Prebid.org is working on updates that will enable support for reading and parsing TCF 2.0 consent strings. See the blog post for timelines.
This consent management module is designed to support the EU General Data Protection Regulation (GDPR)
This module works with supported Consent Management Platforms (CMPs) to fetch an encoded string representing the user’s consent choices and make it available for adapters to consume and process.
Prebid functionality created to address regulatory requirements does not replace each party’s responsibility to determine its own legal obligations and comply with all applicable laws. We recommend consulting with your legal counsel before determining how to utilize these features in support of your overall privacy approach.
This base EU GDPR consent management module performs these actions:
The optional GDPR enforcement module adds on these actions:
In the case of a new user, CMPs will generally respond only after there is consent information available (i.e., the user has made their consent choices). Making these selections can take some time for the average user, so the module provides timeout settings.
If the timeout period expires or an error from the CMP is thrown, one of these actions occurs:
Please start by understanding the IAB’s TCF Implementation Guide.
To utilize this module, a Consent Management Platform (CMP) compatible with the IAB TCF v1.1 spec or IAB TCF v2.0 spec needs to be implemented on the site to interact with the user and obtain their consent choices. It’s important to understand the details of how the CMP works before integrating it with Prebid.js
In general, implementation details for CMPs are not covered by Prebid.org, but we do recommend to that you place the CMP code before the Prebid.js code in the head of the page in order to ensure the CMP’s framework is loaded before the Prebid code executes. In addition, the community is collecting a set of CMP best practices.
Once the CMP is implemented, simply include this module into your build and add a
consentManagement object in the
setConfig() call. Adapters that support this feature will then be able to retrieve the consent information and incorporate it in their requests.
Here are the parameters supported in the
Note that versions of Prebid.js before 2.43.0 had a different GDPR configuration. The module is backwards-compatible, but we recommend migrating to the new config structure as soon as possible.
||The CMP interface that is in use. Supported values are ‘iab’ or ‘static’. Static allows integrations where IAB-formatted consent strings are provided in a non-standard way. Default is
||Length of time (in milliseconds) to allow the CMP to obtain the GDPR consent string. Default is
||Defines what the
||(TCF v1.1 only) Determines what will happen if obtaining consent information from the CMP fails; either allow the auction to proceed (
||An object representing the GDPR consent data being passed directly; only used when cmpApi is ‘static’. Default is
||(TCF v2.0 only) Base64url-encoded TCF v2.0 string with segments.|
||(TCF v2.0 only) Additional consent string if available from the cmp TCData object|
||(TCF v2.0 only) Defines whether or not this pageview is in GDPR scope.|
||(TCF v2.0 only) An object representing the user’s consent status for specific purpose IDs.|
||(TCF v2.0 only) An object representing the user’s legitimate interest status for specific purpose IDs.|
||(TCF v2.0 only) An object representing the user’s consent status for specific vendor IDs.|
||(TCF v2.0 only) An object representing the user’s legitimate interest status for specific vendors IDs.|
||(TCF v1.1 only) Defines whether or not this pageview is in GDPR scope.|
||(TCF v1.1 only) True if consent data is global, false if it’s publisher specific.|
||(TCF v1.1 only) Encoded TCF v1.1 string.|
||(TCF v1.1 only) Encoded TCF v1.1 string.|
allowAuctionWithoutConsent parameter supported for TCF v1.1 refers to the entire consent string, not to any individual consent option. Prebid.js does not parse the GDPR consent string, so it doesn’t know if the user has consented to any particular action.
vendor objects are required if you are using the
gdprEnforcement module. If the data is not included, your bid adpaters, analytics adapters, and/or userId systems will likely be excluded from the auction as Prebid will assume the user has not given consent for these entities.
A related parameter is
deviceAccess, which is at the global level of Prebid.js configuration because it can be used GDPR, CCPA, or custom privacy implementations:
||If false, Prebid.js will prevent adapters and modules from reading and setting cookies and HTML local storage. Defaults to
Example 1: IAB CMP using custom timeout and setting GDPR in-scope by default
Example 2: Static CMP using custom data passing.
Example 1: IAB CMP using custom timeout and cancel-auction options.
Example 2: Static CMP using custom data passing.
Follow the basic build instructions in the GitHub Prebid.js repo’s main README. To include the consent management module, an additional option must be added to the gulp build command:
You can also use the Prebid.js Download page.
Prebid.js adapters don’t need to change to support TCF v2.0 if they already support TCF 1.1 – the consent string is passed through the same bidrequest location. The bidder’s endpoint, however, will need to change to support TCF v2.0. Once the endpoint supports TCF2, you can update the documentation.md file as described below above the table showing the list of TCF2-compliant bidders.
If you are submitting changes to an adapter to support this approach, please also submit a PR to the docs repo to add the
gdpr_supported: true variable to your respective page in the bidders directory. This will ensure that your adapter’s name will automatically appear on the list of adapters supporting GDPR.
To find the GDPR consent information to pass along to your system, adapters should look for the
bidderRequest.gdprConsent field in their
Here is a sample of how the data is structured in the
gdprConsent Data Fields
This field contains the user’s choices on consent, represented as an encoded string value. In certain scenarios, this field might come to you with an
undefined value; normally this happens when there was an error during the CMP interaction and the publisher had the config option
allowAuctionWithoutConsent set to
true. If you don’t want to pass
undefined to your system, you can check for this value and replace it with a valid consent string. See the consent_required code in the example below (under “gdprApplies”) for a possible approach to checking and replacing values.
If the CMP responds with additional consent data as proposed at https://support.google.com/admanager/answer/9681920?hl=en then the corresponding string is stored here.
This field contains the raw vendor data in relation to the user’s choices on consent. This object will hold a map of all available vendors for any potential adapters that want to read the data directly. One use-case for reading from this field would be when an adapter wants to be omitted from a request where they were not given consent. Adapters are able to read through the object to find their appropriate information.
This boolean field represents whether the user in question is in an area where GDPR applies. This field comes from the CMP itself; it’s included in the response when a request is made to the CMP API. On the rare occasion where this value isn’t defined by the CMP, each adapter has the opportunity to set their own value for this field.
One of two general approaches can be taken by the adapter to populate this field:
The following is an example of how the integration could look for the former option:
The implementation of the latter option is up to the adapter, but the general premise is the same. You would check to see if the
bidderRequest.gdprConsent.gdprApplies field is undefined and if so, set the derived value from your independent system.
If neither option are taken, then there is the remote chance this field’s value will be undefined. As long as that’s acceptable for the given system, this could be a potential third option.
gdprConsent object is also available when registering
The object can be accessed by including it as an argument in the
Depending on your needs, you could include the consent information in a query of your pixel and/or, given the consent choices, determine if you should drop the pixels at all.
Here are some things that publishers can do to control various activities:
Prebid.js and much of the ad industry rely on the IAB CMP standard for GDPR support, but there might be some publishers who have implemented a different approach to meeting the privacy rules. Those publishers can utilize Prebid.js and the whole header bidding ecosystem by building a translation layer between their consent method and the IAB method.
At a high level, this could be done as follows:
window.__cmp()function, which will be seen by Prebid.
Below is sample code for implementing the stub functions. Sample code for formatting the consent string can be obtained here.
For instructions on how to generate the IAB consent string see the IAB CMP 1.1 Spec and IAB Consent String SDK.
Use the following values in the gdprApplies field:
This should be set to true if consent data was retrieved from global “euconsent” cookie, or it was publisher-specific. For general purpose, set this to false.
This should be false if there was some error in the consent data; otherwise set to true. False is the same as calling the callback with no parameters.
This should be be set to true once the parameters listed above are processed.
Bidders on this list have self-declared their GDPR support in their https://github.com/prebid/prebid.github.io/tree/master/dev-docs/bidders md file by adding “gdpr_supported: true”.