On this page
- What it is and how it works
- Versioning and current spec version
- Key dated releases (selected)
- Ecosystem role
- Retail media and commerce media extensions
- Disputes and compliance issues
- Transaction ID dispute
- Privacy and data minimisation
- Compliance gaps
- 2026 standards roadmap
- Key terms
- Benchmarks (as-of 2026-10)
OpenRTB
OpenRTB
OpenRTB is the open technical standard maintained by IAB Tech Lab that governs how a seller of advertising space and a prospective buyer communicate during an automated auction, defining the bid request (exchange to bidder) and bid response (bidder to exchange) field by field. Its core purpose is interoperability: a demand-side platform (DSP) can bid into dozens of supply-side platforms (SSPs) and exchanges without building a separate integration for each. (ppc.land, 2026-09-29)
What it is and how it works
Bid requests and bid responses are carried over HTTP as JSON objects, though binary formats such as Protocol Buffers are also permitted; the HTTP header x-openrtb-version identifies which version is in use. (ppc.land, 2026-09-29)
Only two attributes are strictly required in a bid request: an exchange-assigned id and an imp array holding at least one impression object; all other fields, including site/app/device/user, are recommended rather than mandated. (ppc.land, 2026-09-29)
Key impression-level fields include bidfloor (minimum CPM price) and bidfloorcur (currency, defaulting to USD); the top-level at field encodes the pricing rule (1 = first-price, 2 = second-price-plus); tmax sets the maximum milliseconds an exchange will wait for responses. The Source object carries the transaction ID (tid) and the SupplyChain Object listing every paid intermediary; Regs carries legal flags including GDPR, COPPA, and the Global Privacy Platform string. (ppc.land, 2026-09-29)
Any object may carry an ext (extension) field of undefined structure that each exchange documents itself — meaning one signal can sit in different places across different exchanges. Since OpenRTB 2.6, enumerated lists such as device types have lived in the companion specification AdCOM (Advertising Common Object Model), so they can change without a full protocol release. (ppc.land, 2026-09-29)
Versioning and current spec version
OpenRTB's version number is only incremented on breaking changes; the specification is updated approximately once a month via date-coded releases (e.g., 2.6-202211 = November 2022). (IAB Tech Lab GitHub README, undated/living document)
As of September 2026, the active line is OpenRTB 2.6 with the most recent release being 2.6-202606 (June 11, 2026). OpenRTB 3.0 was released for public comment in September 2018 with a non-backward-compatible rebuild splitting the protocol into four layers (transport, format, transaction, domain) and making HTTPS compulsory; Media.net announced early adoption but the market stayed on 2.x. An April 2026 guide from IAB Spain confirmed most platforms still run OpenRTB 2.5 or 2.6 (as-of 2026-04). (ppc.land, 2026-09-29; IAB Spain SSP guide via ppc.land, 2026-04)
On September 14, 2026, IAB Tech Lab moved GitHub Markdown to be the authoritative reference text for its standards, replacing PDFs. (ppc.land, 2026-09-29)
Key dated releases (selected)
| Release | Date | What it added |
|---|---|---|
| 2.6-202303 | Apr 2023 | Video plcmt field replacing deprecated placement (in-stream vs outstream) |
| 2.6-202409 | Sep 2024 | ID Provenance fields in Object:EID to address ID Bridging — records who inserted an identifier and how it was matched |
| 2.6-202501 | Jan 2025 | Content Taxonomy 3.1 genres/gtax fields in Object:Video; ~3× more categories than CT 1.0 |
| 2.6-202505 | May 2025 | Extended Content Identifiers (ECIDs) — richer CTV content intelligence via Content Data Platforms |
| 2.6-202606 | Jun 2026 | realtime and firstbroadcast in Object:Content (live vs replay); ${AUCTION_DISCOUNT_PCT} and ${AUCTION_DISCOUNT_CPM} macros |
(IAB Tech Lab blog posts 2026-01-14, 2025-01-21; ppc.land 2026-09-29)
Ecosystem role
Exchanges and SSPs including Magnite, PubMatic, and Index Exchange build bid requests; DSPs including The Trade Desk, Display & Video 360, and Amazon DSP parse them; Prebid Server implements the standard on the publisher side. Header bidding is a placement strategy that calls multiple exchanges simultaneously in the browser or server, not a separate protocol — it uses OpenRTB underneath. Google Open Bidding runs the multi-exchange auction inside Google's ad server rather than in the page. (ppc.land, 2026-09-29)
Google operated a proprietary Authorized Buyers protocol as a major exception to universal OpenRTB adoption; Google announced its retirement in March 2024 with a February 2025 deadline, extended to April 30, 2025; the sunset was recorded on May 1, 2025, making Google's exchange a full OpenRTB participant. (ppc.land, 2026-09-29)
PubMatic handles approximately 2.7 trillion bid requests per day (as-of 2026-04) and began charging publishers $0.001 CPM for requests above their caps on April 16, 2026. (ppc.land, 2026-04)
Amazon Publisher Services extended its Signal IQ reporting to the full OpenRTB bidstream in May 2026, benchmarking whether publishers pass fields such as the Global Placement ID and transaction ID. (ppc.land, 2026-05)
Retail media and commerce media extensions
IAB Tech Lab stated in January 2025 that "Commerce Media is the fastest growing sector of digital advertising, yet it lacks implementation of some of the most fundamental industry standards." (IAB Tech Lab "Filling the Cart", 2025-01-24)
Product Listing Ad (PLA) extension (finalized January 24, 2025): A community extension introducing the prodfeed object (bidrequest.ext.prodfeed) was released for public comment in December 2024 and finalized January 24, 2025; its presence in a bid request signals that understanding a retailer's product feed is required to transact on the impression. A new data type '13' (Product ID) was added to the Native Ads API 1.2 to support PLAs, signalling that creative rendering is driven by the retailer's own product feed rather than a buyer-supplied creative. The prodfeed extension does not specify the structure of the product feed itself; future guidance from the working group is expected. (IAB Tech Lab "Filling the Cart", 2025-01-24)
Separate Retail Media Extension: As of January 2025, a separate Retail Media Extension (distinct from the PLA/prodfeed extension) was in Public Comment with a deadline of January 24, 2025; its final adoption/rejection status after that comment period is unconfirmed in public sources. (IAB Tech Lab blog, 2025-01-21)
Pre-standardisation working group (2023): An independent working group led by retail ad tech startup Kevel formed in October 2023 to develop OpenRTB standards for retail media outside the IAB Tech Lab process with greater urgency. Members included The Trade Desk, PubMatic, InMobi, Criteo, CitrusAd, TripleLift, Instacart, Uber, Dunnhumby (Tesco), Farfetch, and Delivery Hero. For retail media OpenRTB to support sponsored listings, both SSP and DSP sides must share product catalog, inventory data, geographic shipping information, live reviews, product descriptions, and click-to-cart functionality; it was unclear in 2023 whether these would require new OpenRTB fields or extensions to existing fields. (AdExchanger, 2023-10-12)
AdExchanger source on the Kevel-led retail media working group is from October 2023. Current working group status and any finalized specs it may have produced between 2024 and 2026 are unconfirmed.
Disputes and compliance issues
Transaction ID dispute
IAB Tech Lab position: On August 27, 2025, when Prebid made transaction IDs (tid) bidder-specific (removing buyers' ability to recognise one impression arriving through several exchanges), IAB Tech Lab declared the change a material violation of the OpenRTB specification. (ppc.land, 2025-08)
Prebid position: Prebid said the setting was opt-in and publisher-enabled, designed to protect publisher yield. (ppc.land, 2025-08)
Status: unresolved governance conflict as of the research date.
Privacy and data minimisation
Under a US settlement approved March 26, 2026, Google must offer users a control stripping encrypted user identifiers, device advertising IDs and IP addresses from OpenRTB bid requests, following a January 2025 complaint by EPIC and the Irish Council for Civil Liberties alleging Google's bidding system broadcast data about US individuals roughly 31 billion times a day. (ppc.land, 2026-03)
Compliance gaps
A HUMAN Security diagnostic from November 2023 found that 79% of bid requests carried a SupplyChain object but only 42% of those objects passed full validation. No equivalent 2025–2026 audit was found; these figures may not reflect current state. (ppc.land citing HUMAN Security, 2023-11)
2026 standards roadmap
OpenRTB is voluntary and nothing certifies compliance; the active in-flight items as of October 2026 include:
- Agentic RTB Framework (ARTF): IAB Tech Lab's framework that lets containerised partner code propose changes to a live bid request was declared final on August 12, 2026; IAB Tech Lab's January 2026 agentic roadmap committed to building Protocol Buffers and gRPC mappings of OpenRTB rather than replacing the protocol. (ppc.land, 2026-09-29)
- SupplyChain v1.1 (proposed June 2026): Would let buyers see not only which companies participate commercially in a transaction but also which entities take technical custody of bid requests (Prebid, ad servers, SSAI platforms), designated with
hp=0. Public comment period closed August 21, 2026; finalization status unconfirmed. (briefglance.com citing IAB Tech Lab, 2026-06) - AAMP 3.0 (Agentic Advertising Management Protocols): An OpenProposal specification passing agreed proposals to OpenRTB 2.6, OpenDirect 2.1, or the Deals API (IAB Tech Lab) for execution; public comment deadline October 22, 2026. (ppc.land, 2026-09-29)
- Programmatic Best Practices 1.0: Asks companies to support the most recent widely deployed OpenRTB version; comment deadline October 16, 2026. (ppc.land, 2026-09-29)
- Deals API (IAB Tech Lab) (sidecar): Standardises deal metadata transmission between advertising systems, including a new
Object:Curationfor curated deals; was in Public Comment until January 31, 2026. Described as a sidecar API, not part of the core spec. (IAB Tech Lab "Essential OpenRTB Updates 2026", 2026-01-14) - Live content attributes: New fields for
realtimeandfirstbroadcastinObject:Contentwere proposed April 28, 2026 (public comment through May 28, 2026); incorporated in 2.6-202606 per ppc.land September 2026.
Key terms
| Term | Meaning |
|---|---|
| Bid request | HTTP message from exchange to DSPs containing impression and context data |
| Bid response | HTTP message from DSP to exchange with price and creative |
imp | Impression object within the bid request; at least one required |
bidfloor | Minimum CPM the exchange will accept |
at | Auction type (1 = first-price, 2 = second-price-plus) |
tmax | Milliseconds the exchange waits for responses |
ext | Extension field; structure exchange-specific |
prodfeed | Community extension signalling product feed context for retail media PLAs |
| AdCOM | Advertising Common Object Model — companion spec holding enumerated lists |
| SupplyChain object | Lists every paid intermediary a bid request has passed through |
| ARTF | Agentic RTB Framework — containerised code that can propose live bid request changes |
Benchmarks (as-of 2026-10)
- PubMatic: ~2.7 trillion bid requests/day (as-of 2026-04) (ppc.land)
- SupplyChain inclusion: 79% of requests; only 42% fully validated (as-of 2023-11, STALE — no 2026 figure found) (HUMAN Security via ppc.land)