Osano and the IAB Global Privacy Platform

This is a Premier Only feature. 

What is GPP?

To support vendors, publishers, and advertisers in meeting the updated requirements of the Interactive Advertising Bureau, or IAB, Osano has added support for the IAB's Global Privacy Platform framework. 

"The Global Privacy Platform (GPP) is part of a portfolio of solutions developed by IAB Tech Lab, as part of the Project Rearc initiative, to help the industry solve for the challenges that come with the need to address differing and evolving privacy regulations worldwide. The GPP is a protocol designed to streamline the transmission of privacy, consent, and consumer choice signals from sites and apps to ad tech providers; it enables advertisers, publishers, and technology vendors in the digital advertising industry to adapt to regulatory demands across markets." 

-IAB Tech Lab

Osano's IAB GPP Supported Sections

Within the Global Privacy Platform, there are currently 10 different jurisdiction-related sections that are available for implementation. Within each section, the consent string is created per the individual specification of that section. As more jurisdictions adopt privacy regulations, it is likely that more sections will be added to the GPP framework.

The table below outlines each section in the GPP specifications and whether it is currently supported within the Osano CMP's GPP implementation.

Osano's IAB GPP Implementation

Enabling the IAB GPP framework within Osano is straightforward. To start, flip the “IAB GPP & EU TCF 2.x Frameworks” switch in the “Advanced Settings” of your consent manager configuration. 

Once enabled, go to the new IAB tab and use the search field to find and select any IAB vendors you work with. This action is required to enable the proper creation of the IAB TCF 2.0 and IAB Canada strings.

Once you “Save Changes” and “Publish” these changes, customers who access your site from applicable regions (Regions that fall under the jurisdiction of GDPR or Canada) will automatically receive the TCF, Consent Manager. See Examples of the IAB-Enabled Consent Manager. 

Once set, Osano will automatically signal consent to any included vendor using the IAB framework on your website.

Important: If IAB TCF is enabled while Osano is in Discovery/Listener mode, the consent banner will not display to end users, which means consent signals will not be passed to IAB vendors or downstream ad platforms (such as Google Ads). This can cause ads to stop serving and other unexpected behavior. To avoid this, we recommend only enabling the IAB TCF setting when Osano is running in a live mode (Permissive or Strict).

IAB Vendor Communication  

Osano CMP exposes the standard IAB GPP CMP API specifications.

This allows vendors to access the user’s consent state through the GPP data returned in the object.

Here is an example request using the Global Privacy Platform API specification:

__gpp('ping', (data, success) => {
 if (success) {
   console.log('GPP string:', data.gppString);
   console.log('Applicable sections:', data.applicableSections);
   console.log('Parsed sections:', data.parsedSections);
 }
});

Example Response:

GPP string: DBACNY~CPqG40APqG40AEXABAENC7CwAP_AAH_AACiQHQoB4Cp…AAEAAAAAAAAAAAAAAiAAUAAAABASAAAESEEEAAAIAQAA~1YNY
Applicable sections: [3]
Parsed sections: {
  "tcfeuv2": [
    {
      "Version": 2,
      "Created": "2025-01-01T00:00:00.000Z",
      "LastUpdated": "2025-01-01T00:00:00.000Z",
      "CmpId": 279,
      "CmpVersion": 2913,
      "ConsentScreen": 0,
      "ConsentLanguage": "EN",
      "VendorListVersion": 133,
      "TcfPolicyVersion": 2
      "...": "other fields omitted"
    }
  ]
}