How interactiveadvertisingbureau/global-privacy-platform works
Project type and purpose
• This is a documentation/specification repository for the IAB Global Privacy Platform (GPP).
• The GPP is a “transport layer” for conveying user consent and preference signaling across the digital advertising supply chain.
File structure
• Top-level “Core” folder: holds the two primary technical specs—Consent String Specification and CMP API Specification.
• Top-level “Sections” folder: subdivided into region- or jurisdiction-specific specification extensions (Canada, EEA, US-National, US-States → CA, CO, CT, … VA).
• A single “implementation.md” file: describes example or reference implementations.
README for architectural clues
• The GPP consists of:
– A Consent Management API (CMP API) that allows CMPs to read/write consent data.
– A Consent String format for serializing user choices.
– A registry of “Sections” which map to region-specific privacy rules.
• GPP messages flow from user agent (browser/app) → CMP → ad tech vendors via bid requests.
Main logical components
a. CMP (Consent Management Platform) – front-end/UI in the user’s browser or app.
b. CMP API (from Core/CMP API Specification.md) – JavaScript (or native) interface exposing getConsent(), setConsent(), etc.
c. Consent String Encoder/Decoder (from Core/Consent String Specification.md) – component that serializes/deserializes the consent string.
d. Section Extensions (from Sections/…) – plugins or modules for jurisdictional rules (e.g., EU-TCF, CCPA, MSPA).
e. Ad Tech Supply Chain (Publishers, SSPs, DSPs, Ad Servers) – external parties that consume the consent string.
f. Storage Mechanism – cookie or localStorage where the consent string is persisted.
g. Implementation Layer – reference code or library (implementation.md).
Relationships and data flows
• User interacts with CMP UI → CMP API calls → Consent String Encoder writes user choices → stored locally.
• On each ad request, the stored consent string is attached to HTTP headers or ad request payload → Ad Tech Supply Chain components.
• Section Extension modules contribute additional bits/fields to the consent string according to jurisdiction.
• Downstream vendors decode the string (Consent String Decoder) to apply regional rules.
Architectural patterns and design principles
• Modular extension pattern: the “Sections” directory defines plug-in modules that extend the core consent string with region-specific fields.
• Client-side focus: The entire GPP logic lives in the user agent (no central server component).
• Stateless transport: each ad request carries the entire consent state.
Relevant technologies/frameworks (even if hypothetical)
• JavaScript/TypeScript library for CMP API and Consent String logic.
• Storage: document.cookie or window.localStorage.
• HTTP ad-tech integration (OpenRTB headers or custom X-GPP-String header).