The IAB Europe Transparency & Consent Framework (TCF) gives the publishing and advertising industries a common structure to communicate consumer consent for the delivery of online advertising and content in compliance with the EU’s GDPR and ePrivacy Directive.

To learn more:

If you have questions or need more assistant, contact your Customer Success representative.

Support for GDPR Specific Parameters

In response to IAB recommendations, PubMatic's publisher facing APIs now support GDPR specific parameters.

Open RTB API for Publishers

Two new GDPR parameters have been added to Open RTB JSON:

PubMatic’s Proprietary Ad Server API for Publishers

Two new GDPR parameters have been added:

Passing GDPR Parameters to DSPs

PubMatic passes GDPR specific parameters to DSPs as follows.

Open RTB API

Two new GDPR parameters have been added to Open RTB JSON. The parameters differ slightly depending upon your version of Open RTB as follows.

Up to Version 2.2

Versions 2.3 to 2.5

PubMatic’s Proprietary RTB APIs for DSPs

Two new GDPR parameters have been added:

Passing GDPR Parameters for Google Exchange Bidding Publishers

Google Exchange Bidding (EB) follows a slightly different standard for GDPR parameters. PubMatic receives GDPR specific parameters from Google EB and passes them unchanged to DSPs.

The two EB parameters passed are:

Example Google EB parameter that would be passed to DSPs:

{
     "user": {
          "ext": {
               "consented_providers_settings":
               { "consented_providers": [123, 456] }
          }
     },
     "regs": {
          "ext":
          { "gdpr": true }
     }
}‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Changes in User Sync Process for GDPR Compliance

For EEA users, sync with DSPs happens only when both PubMatic and the DSP have user consent. The URL to initiate user sync with DSPs uses the two parameters below:

For DSP initiated sync, again, the sync occurs only when PubMatic and DSPs both have EEA user consent.