Privacy signal locations carry conflicting values
A canonical privacy field and its legacy extension disagree.
What it means
Privacy checks use the selected version's location when it is present, including an empty or null value. If that location is absent, the alternate is inspected. Conflicting values are never merged.
Why it matters
Readers using different field locations could reach different decisions about the same request.
How to fix it
Reconcile the original values with the sender. Use the selected contract's location and remove a duplicate only after confirming that it carries the same value.
Example that trips it
{ "regs": { "gdpr": 0, "ext": { "gdpr": 1 } } }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.