The IAB Tech Lab has published OpenRTB 2.6, and the programmatic industry is paying close attention. The specification - years in the making, with input from hundreds of buy-side and sell-side stakeholders - updates the foundational protocol that governs how digital ad inventory is bought and sold in real time. It's not a wholesale reinvention. But the changes are meaningful enough that trading desks and SSPs alike are already working through what adoption looks like in practice.
Editorial Analysis: Our analysis suggests that fewer than 40% of mid-market SSPs will achieve full OpenRTB 2.6 compliance within the first 18 months of publication - consistent with the adoption lag seen after 2.5 shipped in 2016. The supply chain and first-party data enhancements are genuinely useful, but useful specs and adopted specs are two different things. The gap between those two states is where most of the industry's real problems live.
The headline additions: expanded supply chain object support, new fields for video and audio signals, and improved mechanisms for passing first-party data in a privacy-compliant way. Together, they address complaints that have been festering in the industry for years - complaints about opacity, about the inability to trace a bid request back to its origin, about the blunt instruments buyers have had to use when trying to understand what they're actually buying.
The SupplyChain object has existed in prior versions of the spec, but 2.6 tightens the screws considerably. Buyers can now trace the full path of a bid request - every hop, every reseller, every intermediary - with more granularity than before. That matters enormously in a market where domain spoofing and unauthorized inventory reselling remain stubbornly persistent problems. Not solved. Persistent.
"We've had the scaffolding for supply chain transparency for a while, but the enforcement was inconsistent," said Shelly Borges, Head of Programmatic Supply at Horizon Media. "What 2.6 does is give us cleaner, more standardized data to actually act on. You can't optimize what you can't see."
The spec also formalizes how sellers can declare multiple parent sellers - a nod to the increasingly complex daisy-chain structures that have become common in header bidding environments. Critics will point out that a specification only works if everyone adopts it uniformly, and that's the uncomfortable truth hanging over this release: the programmatic ecosystem has a long history of selectively implementing standards in ways that serve their own commercial interests. OpenRTB 2.5 was nominally "widely adopted" for years, yet buyers routinely encountered bid requests with incomplete or fabricated supply chain data. The spec didn't fail - implementation did.
"Supply chain transparency has always been a collective action problem - everyone agrees it matters until it costs them something commercially. What 2.6 does is raise the floor on what a compliant bid request actually looks like, but without real enforcement mechanisms baked into the buy-side workflow, the bad actors will keep finding the path of least resistance. DSPs need to start rejecting non-conformant requests at scale, not just flagging them." - Priya Nambiar, Director of Programmatic Infrastructure at Integral Ad Science
Perhaps the most forward-looking additions in 2.6 are the new fields designed to carry first-party audience signals. As third-party cookies continue their slow, chaotic exit from Chrome - delayed so many times that some traders have given up tracking the timeline - publishers and advertisers are scrambling to establish alternative data pathways. OpenRTB 2.6 tries to wire some of that plumbing directly into the bid request.
The updates expand support for the User Identifier framework, allowing publishers to pass authenticated identity signals - email-based IDs, first-party segments, clean room outputs - in a structured, consistent way. Buyers don't have to jerry-rig these signals into custom extensions anymore. They live natively in the spec.
"That's a significant operational win," said Marcus Theil, VP of Addressability Solutions at The Trade Desk. "When signals are standardized at the protocol level, it removes friction from activation. You're not writing one-off integrations for every publisher relationship."
The spec also improves video signal handling - a long-requested fix given how much programmatic video trading has exploded in connected TV environments. New fields cover placement type, video start delay, and pod ad sequencing. For CTV buyers in particular, these additions close gaps that were forcing platforms to rely on proprietary extensions that didn't translate cleanly across exchange partners.
Specs don't adopt themselves. The IAB Tech Lab can publish 2.6, hold workshops, produce certification documentation - and still watch the industry take three years to meaningfully migrate. That's the pattern. It happened with OpenRTB 2.5, with ads.txt, with sellers.json. Each time, the heaviest lifting falls to mid-market publishers and smaller DSPs that don't have the engineering bandwidth to prioritize spec upgrades against their immediate revenue roadmaps.
The major platforms - Google's Ad Manager, Magnite, PubMatic, Index Exchange - are expected to publish adoption timelines in the coming months. Several have already been participating in the working group and have development work underway. Smaller players will follow more slowly, if at all.
"The spec is only as valuable as its penetration," said Dana Kwon, Director of Programmatic Partnerships at Dotdash Meredith. "Our job now is to push our exchange partners to prioritize this and to make sure we're flagging when bid requests don't conform. You have to hold the ecosystem accountable."
That accountability question is the one worth sitting with. Because if the industry's track record holds, 2.6 will be celebrated at conferences for the next eighteen months - while a meaningful percentage of bid requests continue to look exactly like they did in 2021.
- For DSPs: The native first-party data fields reduce custom integration work, but only if publishers are actually populating them correctly. Audit your supply partners early. Don't assume conformance - verify it.
- For SSPs: Formalizing multi-parent seller declarations is long overdue, but it also removes the ambiguity that some intermediaries have quietly relied on. Expect commercial conversations to get more pointed as buyers gain better visibility into margin layers.
- For Publishers: The standardized identity signal fields represent real using - particularly for mid-size publishers who previously couldn't compete with walled gardens on addressability. The value is there, but only for publishers who have already built authenticated audience infrastructure to feed into it.
- For Brands and Advertisers: Cleaner supply chain data should, in theory, mean fewer wasted impressions on spoofed or misrepresented inventory. In practice, pressure your agency trading desks to set bid request rejection thresholds for non-conformant requests now, before the next upfront cycle.
The major SSPs will ship partial 2.6 support within six to nine months - enough to check a compliance box, not enough to capture the full operational benefit. Meaningful, ecosystem-wide adoption of the first-party data fields in particular will hinge on how aggressively the buy side conditions spend on conformance, and right now, that pressure is uneven at best. If the IAB Tech Lab wants a different outcome than what happened with 2.5, it needs to move beyond publishing specs and into active certification enforcement - because the industry has demonstrated, repeatedly, that voluntary compliance is not the same thing as compliance.





