GPP header sections do not match gpp_sid or the payload count
The section ids encoded in the GPP header disagree with regs.gpp_sid, or the number of '~' payloads does not match the header.
What it means
The GPP header's Fibonacci range is the table of contents. gpp_sid must list the same ids in the same order, and there must be one payload after '~' per id. A header that says section 2 with gpp_sid [7] is two different stories.
Why it matters
A buyer that trusts gpp_sid will decode the wrong payload as US National or TCF. Privacy decisions then run on the wrong framework.
How to fix it
Generate header, payloads, and gpp_sid from one encoder pass. If you add a section, rebuild the header; do not append '~' and forget the range.
Example that trips it
{ "regs": { "gpp": "DBABM~CPXxRfAPXxRfAAfKABENAPCgAAAAAAAAAAAYgAAAAAAAA", "gpp_sid": [7] } }DBABM encodes section 2 (TCF EU). gpp_sid claims 7 (US National).
Check your payload
Paste a bid request or response into the tester to see whether this code fires against it, or gate on the id in CI with the CLI: the id is stable, wording is not.
Back to the full diagnostic code reference.