OpenRTB 2.6-202204
What this release is
The base OpenRTB 2.6 release was the largest single update in the protocol's history: CTV ad-pod bidding (pod controls and exact-duration rqddurs), rewarded and SSAI signaling, structured user-agent objects, cattax taxonomy selection, BCP 47 language fields, the AUCTION_MIN_TO_WIN macro, and the promotion of GDPR consent and the supply chain out of ext into core objects, alongside a sweep of removals of long-deprecated fields.
Validation note: The published 2.6-202204 archive has no machine-readable object tables, so RTBlint has no extracted catalog for it. Validation against this exact snapshot reports openrtb.version.unsupported rather than passing payloads silently; validate against 2.6-202210 instead, which is the same generation with a usable catalog.
What changed in 2.6-202204
bid.apisAdded fieldOpenRTB 2.6 added the multi-valued bid.apis field.bid.mtypeAdded fieldOpenRTB 2.6 added bid-level markup-type signaling.bidrequest.cattaxAdded fieldOpenRTB 2.6 standardized taxonomy selection with cattax across request and bid objects.imp.video.sequenceDeprecated fieldOpenRTB 2.6 deprecated legacy sequence, device-ID hash, demographic, and single-api fields.imp.rwddAdded fieldOpenRTB 2.6 added rewarded-inventory and SSAI signaling on impressions.imp.video.maxseqAdded fieldOpenRTB 2.6 added pod-bidding controls for video and audio inventory.imp.video.rqddursAdded fieldOpenRTB 2.6 added exact-duration requirements for video and audio creatives.language.bcp47Added behaviorOpenRTB 2.6 added BCP 47-oriented language signaling, including wlangb-style fields for more precise locale handling.macro.${AUCTION_MIN_TO_WIN}Added macroOpenRTB 2.6 added the AUCTION_MIN_TO_WIN substitution macro.networkAdded objectOpenRTB 2.6 added network, channel, supply-chain, and extended-ID object families.regs.ext.gdprMoved fieldOpenRTB 2.6 moved GDPR signaling out of regs.ext into the core regs object.banner.wmaxRemoved fieldOpenRTB 2.6 removed fields that had already been deprecated in earlier revisions.device.suaAdded objectOpenRTB 2.6 added structured user-agent and brand-version objects.user.ext.consentMoved fieldOpenRTB 2.6 moved the TCF consent string from user.ext into the core user object.Validate against 2.6-202204
The tester can pin validation to this exact revision, so deprecated, moved, and not-yet-available findings reflect what 2.6-202204 actually says. The same pin works in the CLI: rtblint validate --version 2.6-202204 request.json.
Adjacent versions
- Previous: OpenRTB 2.5
- Next: OpenRTB 2.6-202210
- All versions: version index
- Migrating across the big steps: 2.5 vs 2.6 and 2.6 vs 3.0