Why does the tool warn about usnat and a state section together?

Under the MSPA a publisher signals either the National approach (usnat) or the specific state section for a transaction, not both; sending both leaves bidders to guess which one governs.

What is gpp_sid and why check it?

regs.gpp_sid lists the section ids that apply to the request (e.g. 7 for usnat, 2 for TCF EU). Only listed sections are supposed to be honoured, so a string that encodes a section not in gpp_sid — or a gpp_sid that names a section missing from the string — is a real integration bug.

Is uspv1 still valid?

The legacy us_privacy string (section 6) is deprecated; OpenRTB 2.6 replaces regs.us_privacy with regs.gpp + regs.gpp_sid and the usca / usnat sections.

Is my string sent anywhere?

No. Decoding and encoding run in your browser with the IAB reference library; nothing is uploaded.

IAB GPP Decoder

Paste a GPP string (or a URL with gpp= and gpp_sid=, or an OpenRTB bid request with regs.gpp) to see every section decoded: US National (MSPA) and all state sections (CA, VA, CO, UT, CT, FL, MT, OR, TX, DE, IA, NE, NH, NJ, TN, MN) are rendered as labelled rows with the IAB value legends (not applicable / opted out / did not opt out, no consent / consent), named sensitive-data and known-child categories, MSPA modes and the GPC sub-section, plus a one-line summary per section. The TCF EU section is decoded with the TCF engine and can be opened in the TCF decoder. The tool checks gpp_sid against the sections actually present, flags contradictory combinations (usnat plus a state section, both MSPA modes), keeps the last good decode while you type, and includes a per-section editor that re-encodes with the reference library.

Runs locally in your browser

Decode a GPP string with human-readable US legends, check it against gpp_sid, and edit / re-encode sections — ⌘Enter decodes now

GPP string

186 chars · 1 line

Sections

—

Section IDs

—

Applies to

—

Valid

—

String length

—

IAB TCF Consent Decoder

Decode TCF v2.2 consent strings with vendor names from the Global Vendor List, a purpose × vendor matrix and an encoder.

OpenRTB Inspector

Validate & annotate OpenRTB 2.6 BidRequest and BidResponse JSON.

ads.txt / app-ads.txt Validator

Fetch any domain's ads.txt or app-ads.txt, validate it against the IAB 1.1 spec, follow SUBDOMAIN pointers, and cross-check every line against exchange sellers.json files.

How to use IAB GPP Decoder

1Paste the GPP string, an ad-request URL containing gpp= (gpp_sid= is picked up too), or a bid request with regs.gpp / regs.gpp_sid.
2Read each section card: every field shows its meaning, a colored Yes / No / N-A chip and, for sensitive-data and known-child fields, the named category per index.
3Check the warnings and the "Header & gpp_sid" tab to confirm the declared applicable sections match what the string encodes.
4For the TCF EU section, click "Open in TCF decoder" to resolve vendor names and see the purpose × vendor matrix.
5Use the Editor tab to change any US field (or add / remove a section), then copy the re-encoded string or a single section segment.

About IAB GPP Decoder

IAB GPP Decoder is part of FizzKit — a collection of focused developer and ad-tech tools. Because everything runs locally, it works offline once loaded and never exposes your data to a remote server.

Frequently asked questions

It depends on the field kind. Notices: 0 not applicable, 1 provided, 2 not provided. Opt-outs: 0 not applicable, 1 opted out, 2 did not opt out. Consents (sensitive data, known child, secondary use): 0 not applicable, 1 no consent, 2 consent. MSPA fields: 0 N/A, 1 yes, 2 no. The tool labels every value accordingly.

Related tools