What is OpenRTB?
Also known as: OpenRTB 2.6, Real-Time Bidding protocol
Quick definition
OpenRTB is the IAB Tech Lab specification that standardizes how an exchange or SSP sends a bid request describing an impression to DSPs and how DSPs answer with a bid response, so thousands of buyers and sellers can trade in real time through one common JSON message format.
How it works
- User opens a page or app; an ad slot becomes available
- SSP/exchange builds a bid request (imp, site/app, device, user, regs objects)
- Request fans out to DSPs, usually with a ~100–300 ms timeout
- DSPs return bid responses with price, creative markup and deal ID
- Exchange runs the auction and fires win / billing / loss notices
Key points
- Steward
- IAB Tech Lab. 2.x is the version deployed at scale; 2.6 added CTV pod bidding, richer supply chain and loss-reason signals.
- Core objects
- BidRequest → Imp (banner/video/audio/native) → Site or App → Device → User → Regs; response is BidResponse → SeatBid → Bid.
- Extensions
- Vendors use the ext object for non-standard fields, which is where most integration drift happens.
Benefits
- One integration pattern reaches many partners
- Supports deals, floors and supply-chain transparency (schain)
Trade-offs
- Heavy use of ext fields fragments implementations
- Version adoption lags; many endpoints still run partial 2.5
FAQ
What is the difference between OpenRTB 2.6 and 3.0?
2.6 is an incremental update of the widely deployed 2.x line. 3.0 restructured the model into layers (transport, OpenRTB, AdCOM), but saw limited adoption, so most of the market extended 2.x instead.
Who uses OpenRTB?
SSPs, ad exchanges, DSPs, ad networks and header bidding wrappers use it to exchange bid requests and responses.
Explore on AdTech Radar
Official sources
Last reviewed 2026-10-27. Explanations are written by AdTech Radar; consult the official specification for implementation.