Global Privacy Platform (GPP)
GPP consolidates consent and privacy signals from all major global regulations into a single standardized string, dramatically reducing integration complexity for publishers, CMPs, and ad tech vendors operating across multiple jurisdictions.
Last updated Sep 26, 2026 by ATDb automated enrichment · Connections updated Sep 28, 2026
AI-drafted from public sources2 sources cited
At a glance
About
The dominant open industry standard for multi-jurisdictional privacy signal transmission in programmatic advertising, maintained by IAB Tech Lab
The Global Privacy Platform (GPP) is an open technical standard developed and maintained by IAB Tech Lab designed to streamline the communication of user privacy preferences and consent signals across the programmatic advertising ecosystem. Rather than requiring separate integrations for each regional privacy regulation, GPP provides a unified container string that can carry consent and opt-out signals for multiple jurisdictions simultaneously — including GDPR (via TCF), CCPA/CPRA (via the US Privacy String and US National Privacy Technical Specification), and other regional frameworks. GPP was introduced to address the growing complexity of global privacy compliance as regulations proliferated across the US states and internationally. Publishers, CMPs (Consent Management Platforms), DSPs, SSPs, and ad servers can implement a single GPP integration and receive structured, machine-readable privacy signals regardless of the user's jurisdiction. The framework uses a modular architecture where each regulatory section is encoded as a discrete 'section' within the GPP string, allowing new regulations to be added without breaking existing integrations. As a technical standard rather than a commercial product, GPP is freely available and open-source, governed by IAB Tech Lab's working groups with input from major industry stakeholders including publishers, ad tech vendors, and privacy advocates. Its adoption is considered critical infrastructure for privacy-compliant programmatic advertising, and it is increasingly required by major DSPs and SSPs as a condition of doing business. GPP effectively supersedes and extends earlier frameworks like the IAB US Privacy String and works alongside TCF 2.x for European consent.
Business model
Open-source industry standard / Non-profit trade body initiative
Target market
Enterprise
What they offer
GPP String
A standardized, encoded container string that carries privacy and consent signals from multiple regulatory frameworks in a single payload, transmitted via the ad request or JavaScript API
GPP JavaScript API
A standardized browser-side API (similar to __tcfapi and __uspapi) that CMPs implement to expose GPP signals to ad tech vendors on the page
US National Privacy Technical Specification
A GPP section covering US state-level privacy laws (CPRA, VCDPA, CPA, CTDPA, etc.) with a unified opt-out signal structure for US multi-state compliance
TCF Section Integration
Native support for embedding IAB Europe's Transparency and Consent Framework (TCF 2.x) signals as a discrete section within the GPP string for GDPR compliance
GPP Header Field
A standardized field for passing GPP strings in OpenRTB bid requests, enabling downstream buyers to parse and honor privacy signals programmatically
Key features
Use cases
Customer segments
Tech & specs
Technology stack
Security & compliance
Deployment
API
Yes
- 2022 · Founded