openrtb.2.6.user.consent

What it means

In OpenRTB 2.6-202204, user.ext.consent moved to user.consent.

OpenRTB 2.6 moved the TCF consent string from user.ext into the core user object.

Why it matters

A consumer on 2.6-202204 reads this value from user.consent. Send it at the old location and it is silently ignored, so whatever it governs (consent, restrictions, targeting) never takes effect.

How to fix it

Write the value at user.consent instead of user.ext.consent. While you still serve older partners, you may need to populate both during the transition.

Paste your bid request into the tester and select OpenRTB 2.6-202204 to see whether this rule fires against your payload.

Reference

• Specification section: Section 3.2.20
• Source: OpenRTB 2.6 Appendix B: Version 2.5 to 2.6

Back to the full rule catalog.