ORTB
中 / EN
Chapter navigation

GPP overview

live

The Global Privacy Platform (GPP) is the container: the whole string is Header ~ Section ~ Section, with the Header declaring which sections travel in this bid. This chapter expands into three sub-pages: string structure, section registry and gpp_sid.

Lede

This page will cover

  • Entry cards to the three sub-pages
  • Short mental-model lede on the GPP container and its section payloads (the full version stays in the legacy page §1, not migrated this round)

Group

GPP String structure & encoding

Overall layout of the Global Privacy Platform (GPP) string, the three Header fields (Type / Version / Sections), modified base64 encoding rules, and the first-character recognition convention (D = GPP, C = the standalone TC String of the Interactive Advertising Bureau (IAB) Europe Transparency & Consent Framework (TCF) v2).

  • Overall [Header]~[Section]~[Section] layout with the ~ / . dual delimiters
  • The three Header fields (Type Int(6) / Version Int(6) / Sections Range(Fibonacci))
Enter chapter

Section registry

The registry of all 27 official Global Privacy Platform (GPP) Section IDs, rendered dynamically from the GitHub registry with no hard-coded upper bound; high-frequency sections (§2/§5/§6/§7/§8/§9/§10) can expand into payload summaries.

  • The complete registry of Section IDs 1–27 (apiPrefix / jurisdiction / status / specUrl)
  • Payload expansion entries for high-frequency sections (linking to their own chapters)
Enter chapter

gpp_sid semantics & multi-section use

gpp_sid declares which Global Privacy Platform (GPP) Section IDs are in force for this transaction; it is an integer[] in OpenRTB and a string in URL macros (${GPP_SID}), and never includes §3 / §4. When several sections coexist each is parsed independently.

  • Semantics: declaring which Section IDs are in force for this transaction
  • Carriage type delta: OpenRTB regs.gpp_sid = integer[]; URL macro ${GPP_SID} = string (comma-separated)
Enter chapter