OpenRTB

OpenRTB is the open, industry-standard protocol that governs REAL-TIME-BIDDING — the structured, common language in which programmatic ad transactions happen. When a page loads and an ad slot becomes available, OpenRTB defines the format of the 'bid request' (the message describing the impression — the page, the user context, the ad slot, the constraints) that the publisher's supply-side platform sends out, and the format of the 'bid response' that advertisers' demand-side platforms send back, all in the ~100 milliseconds before the page renders. Maintained by the IAB Tech Lab, it's the shared protocol that lets the thousands of companies in programmatic advertising transact with each other automatically and at massive scale.

What the bid request carries and why standardization matters: the OpenRTB bid request is a structured message (JSON) describing everything a bidder needs to decide whether and how much to bid — the impression (the ad slot: size, format, position, whether it's video/display/native), the context (the site or app, the page, the content category), the user (whatever identity and audience signals are available — and increasingly constrained by privacy: the cookie/ID, or its privacy-preserving replacements, the consent signals like the IAB-TCF string, geo, device), and the constraints (floor price, allowed ad types, restrictions) — and the bid response carries the bid (the price and the ad to serve). Standardization is the entire point: without a common protocol, every DSP would need a custom integration with every SSP (an impossible n-by-n mess), so OpenRTB is the shared language that makes the programmatic ecosystem interoperable — any compliant DSP can bid on any compliant SSP's inventory because they speak the same protocol, which is what enabled programmatic to scale to billions of impressions across thousands of companies. How the auction works on top of it: the SSP sends the OpenRTB bid request to multiple DSPs simultaneously, each DSP evaluates the impression against its advertisers' campaigns and targeting (in milliseconds), the DSPs return bids, the auction resolves (the FIRST-PRICE-AUCTION that programmatic largely moved to), and the winning ad is served — all before the page finishes loading, billions of times a day. Where OpenRTB sits in the stack: it's the protocol layer beneath the players (DSPs, SSPs, ad exchanges, the HEADER-BIDDING wrappers) — the standard they all implement, the 'TCP/IP of programmatic' — and its evolution tracks the industry's (newer versions handle new formats, new privacy signals, supply-chain transparency objects like the ads.txt/sellers.json/SupplyChain that combat the DOMAIN-SPOOFING and fraud the INVALID-TRAFFIC entry covers). The honest framing for marketers: OpenRTB is infrastructure most marketers never touch directly but should understand exists — it's why programmatic works (the standardization that makes the ecosystem interoperable and scalable), it's where the impression's context and the privacy signals live (so the privacy changes reshaping advertising show up as changes to what the bid request can carry — the deprecation of the third-party-cookie identifier, the addition of consent and supply-chain objects), and it's the plumbing whose existence explains how a billion ad auctions resolve in milliseconds; understanding OpenRTB is understanding the machinery beneath programmatic, even if you buy through a DSP's interface rather than touching the protocol itself.

OpenRTB matters as the foundational protocol of programmatic advertising — the standard that makes the ecosystem interoperable and enables real-time bidding at scale — so it matters to anyone working in programmatic to understand as the machinery beneath the DSP and SSP interfaces they actually use. It matters most when understanding how programmatic actually works (the bid request, the auction, the millisecond resolution), how privacy changes propagate (as changes to what the bid request carries — the cookie deprecation, the consent and supply-chain objects), and how fraud and transparency efforts work (the SupplyChain and sellers.json objects in the protocol). The discipline for most marketers is understanding OpenRTB exists and what it does (the interoperability standard, the bid-request context, the privacy-signal carrier) rather than implementing it directly — recognizing it as the plumbing that explains programmatic's scale, interoperability, and the way privacy and fraud changes show up in the machinery beneath the buying interfaces.

OpenRTB was created to standardize real-time bidding as programmatic advertising emerged, replacing the impossible tangle of custom point-to-point integrations with one open protocol every DSP and SSP could implement; maintained by the IAB Tech Lab, it became the foundational standard - the 'TCP/IP of programmatic' - and its evolution tracks the industry's, carrying new formats, privacy signals, and supply-chain-transparency objects as the ecosystem changed.

Etymology: source.

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

Areas of marketing where openrtb is a core concern: