What is OpenRTB?
OpenRTB is the IAB Tech Lab standard that defines the JSON messages ad exchanges and bidders use to buy and sell impressions in real time. Read the full explanation →
FAQ
93 questions ad ops and integration engineers actually ask about OpenRTB. Each one shows the first line of the answer here and links to the full answer, which names the exact field, version, and default. Where a guide or reference page already covers the question in depth, the link goes there.
The protocol, the auction, and the structure of a bid request: required fields, objects, and the conventions every integration relies on.
OpenRTB is the IAB Tech Lab standard that defines the JSON messages ad exchanges and bidders use to buy and sell impressions in real time. Read the full explanation →
A user loads a page or app, the publisher's ad system asks an exchange to sell the impression, and the exchange sends an OpenRTB BidRequest over HTTP POST to many bidders at once. Read the full explanation →
OpenRTB is a wire protocol; Prebid.js is a piece of software. Read the full explanation →
From the protocol's point of view there are only two roles: the supply side sends OpenRTB bid requests and runs the auction, and the demand side receives them and bids. Read the full explanation →
A bid request is the JSON message an exchange sends to bidders to offer one or more impressions for sale. Read the full explanation →
A bid response is the JSON message a bidder returns with its bids. Read the full explanation →
Only two: id, the exchange's unique ID for the request, and imp, an array containing at least one Imp object, each with its own required id. Read the full explanation →
Check BidRequest.at: 1 means first price, 2 means second price plus, and 2 is the default when the field is omitted. Read the full explanation →
The Imp object describes a single ad placement being auctioned, and the imp array can hold several of them; a single bid request may offer every ad position on a page, for example. Read the full explanation →
Include a site object for website inventory or an app object for non-browser application inventory; OpenRTB 2.6 adds a third option, dooh, for digital out-of-home screens. Read the answer →
Set BidRequest.test to 1. Read the full explanation →
Three fields control currency, all using ISO 4217 alpha codes. Read the answer →
They are the publisher's blocklists, applied request-wide. Read the answer →
cattax is an integer telling bidders which category taxonomy the category arrays use, per the AdCOM Category Taxonomies list; it defaults to 1, meaning IAB Content Category Taxonomy 1.0. Read the full explanation →
Device describes the hardware and software the impression will be delivered to, and it drives targeting, fraud detection, and identity. Read the full explanation →
The user object describes the human on the other side of the impression: user.id (the exchange's identifier), buyeruid (the bidder's mapped identifier from a cookie sync), eids for standardized identity providers, consent for the TCF consent string when GDPR applies, plus geo, data segments, and keywords. Read the full explanation →
ext is a placeholder object for exchange-specific extensions, and by convention it may appear on any OpenRTB object. Read the answer →
wseat is an allowlist and bseat a blocklist of buyer seats (advertisers or agencies) permitted to bid on the impressions in the request. Read the full explanation →
allimps is a flag saying whether the impressions in the request represent every impression available in the context, such as all placements on a page or all video spots in a pod, to support roadblocking. Read the full explanation →
There is no fixed size: a bid request is usually a few kilobytes of JSON, growing with eids arrays, supply chains, and multi-format impressions, and the spec does not set a limit. Read the answer →
OpenRTB payloads are JSON sent over HTTP POST with Content-Type application/json, and the response must use the same representation as the request. Read the answer →
IAB Tech Lab maintains OpenRTB. Read the full explanation →
Target OpenRTB 2.6 at its latest dated snapshot. Read the answer →
Why requests get dropped, why bids lose, what the no-bid codes mean, and how to validate payloads before they cost revenue.
Work the path from the exchange inward: confirm the endpoint the exchange has on file matches what you deployed (scheme, host, path), that your endpoint returns a well-formed response or HTTP 204 quickly enough to stay under the exchange's timeout, and that traffic filters on the exchange side (geo, media type, QPS caps, pretargeting) are not excluding you. Read the answer →
Start by separating deliberate no-bids from failures. Read the answer →
Ask for loss reasons via the loss notice URL. Read the full explanation →
If the bidder returns a BidResponse with nbr set, the code tells you where to look: nbr 2 is Invalid Request, which means the bidder could not parse or accept your bid request, so run the request through a validator before anything else. Read the full explanation →
HTTP 204 No Content is the spec's preferred way for a bidder to say it has no bid: no body, cheapest possible round trip. Read the full explanation →
Paste it into a validator that checks against the actual spec catalog, not just JSON syntax. Read the full explanation →
Keep your bid request fixtures in the repo and lint them on every build. Read the full explanation →
Set test to 1 on the bid request. Read the answer →
The usual suspects, in order: JSON that does not parse (trailing commas, unescaped quotes, truncation), a missing top-level id or imp array, an empty imp array, integers sent as strings (at, tmax, w, h, the flag fields), both site and app present, and fields that moved in 2.6 still sitting at their 2.5 paths. Read the answer →
Check the contract fields first: BidResponse.id must echo the request id, every bid.impid must exactly match an imp.id from the request, price must be a JSON number (CPM), and the bid must carry markup in adm or a win-notice URL in nurl. Read the answer →
Measure against tmax, not against your server clock. Read the full explanation →
Different counting points. Read the answer →
Sample and log raw request bodies at your edge (before any normalization), strip or hash user identifiers, and store them as fixtures. Read the answer →
seatbid is the array grouping bids by bidder seat: each SeatBid carries an optional seat identifier and a bid array with at least one bid. Read the answer →
First confirm you actually won: nurl fires on win, and depending on the exchange that can be the auction win or the final render decision. Read the answer →
Most exchanges review creatives before letting them win, either pre-bid (submit for approval) or post-bid (first bids lose while the creative is in review). Read the answer →
Video adds media constraints on top of the usual auction filters, and any mismatch disqualifies the bid: your creative's MIME type must be in imp.video.mimes, the VAST version you return must map to a value in protocols, duration must sit between minduration and maxduration (or match rqddurs exactly when present), and dimensions should fit w and h. Read the answer →
Look at the x-openrtb-version HTTP header on their requests; the spec has exchanges declare the version there (for example x-openrtb-version: 2.6). Read the answer →
It is the custom HTTP header OpenRTB defines for version signaling on the wire: the sender of a bid request declares the protocol version it speaks, for example x-openrtb-version: 2.6. Read the answer →
Usually tolerated, occasionally fatal, always worth knowing about. Read the answer →
Run the validator with machine-readable output and filter on rule IDs. Read the answer →
Options are thinner than you would expect for a protocol this central. Read the answer →
Media-type specifics: the video object and ad pods, the native request string, bid floors and PMP deals, and the substitution macros in win and loss notices.
Add an imp.video object to the impression; its presence is what marks the impression as video. Read the full explanation →
imp.video.plcmt declares the video placement subtype using AdCOM's Plcmt Subtypes list, which follows the updated IAB digital video guidelines. Read the full explanation →
Send imp.video.plcmt = 1 (instream) for CTV. Read the answer →
Send both during the transition, but treat plcmt as authoritative. Read the full explanation →
Each slot in the pod is its own imp, and a shared imp.video.podid ties them together. Read the full explanation →
Set imp.ssai, an integer added in OpenRTB 2.6 with default 0. Read the answer →
Set imp.rwdd = 1. Read the answer →
Set imp.video.skip = 1 to say the player allows skipping, then qualify it with skipmin and skipafter (both default 0). Read the answer →
imp.video.protocols uses AdCOM's Creative Subtypes Audio/Video list. Read the full explanation →
imp.audio mirrors imp.video for the core fields (mimes required, minduration, maxduration, protocols, startdelay, full pod support with podid, poddur, rqddurs) but drops the visual ones: no w, h, plcmt, linearity, skip, or playbackmethod. Read the full explanation →
Add imp.native with two fields that matter: request and ver. Read the full explanation →
Because the Native Ads API is a separate specification that versions independently of OpenRTB, the request payload is carried as an opaque JSON-encoded string. Read the full explanation →
Set imp.bidfloor, a float expressed as CPM, with imp.bidfloorcur naming the currency as an ISO-4217 code (default USD). Read the full explanation →
The usual cause is a currency mismatch: imp.bidfloorcur defaults to USD, so a floor of 200 intended as JPY but sent without bidfloorcur reads as a 200 USD CPM and nothing clears it. Read the answer →
The seller attaches imp.pmp to the impression, containing private_auction and a deals array of Deal objects. Read the full explanation →
Deal.at = 3 means the value in Deal.bidfloor is the agreed fixed deal price, not a floor to bid above. Read the answer →
durfloors lets sellers price video and audio by creative duration: an array of DurFloors objects on imp.video, imp.audio, or Deal, each with mindur or maxdur (at least one is required, an unbounded end is omitted) and a bidfloor in CPM. Read the full explanation →
The exchange replaces ${AUCTION_PRICE} with the clearing price, in the same currency and units as the bid and reflecting any discount, wherever the macro appears: in the nurl, burl, and lurl notice URLs and inside the adm markup itself. Read the full explanation →
Three notice URLs on the Bid object, each fired by the exchange for a different event. Read the full explanation →
nurl fires on auction win; burl fires later, when the win becomes billable under the exchange's business policy, which the spec describes as typically delivered or viewed. Read the answer →
${AUCTION_MIN_TO_WIN}, added in OpenRTB 2.6, is replaced with the minimum bid that would have tied the decisive competing price, in the bid's own currency and units, and is the standard bid-shading feedback signal. Read the full explanation →
bid.mtype declares the type of the creative markup so the exchange can associate it with the right sub-object of the impression: 1 = banner, 2 = video, 3 = audio, 4 = native. Read the full explanation →
Put the VAST XML document directly in bid.adm as a JSON-escaped string and set mtype = 2. Read the full explanation →
eventtrackers is the Native 1.2 mechanism for declaring and returning ad tracking, replacing the older imptrackers and jstracker fields, which the spec marks as to be deprecated. Read the answer →
Consent and regulatory signals with their exact paths, schain, ads.txt and sellers.json, and how the 2.x line and 3.0 relate.
Set regs.gdpr to 1 when the request is subject to GDPR and put the TCF consent string in user.consent. Read the answer →
Put the Global Privacy Platform consent string in regs.gpp and list the applicable section IDs in regs.gpp_sid. Read the answer →
Send GPP (regs.gpp plus regs.gpp_sid) where your partners support it; the US Privacy signal was deprecated by IAB Tech Lab on January 31, 2024 in favor of GPP. Read the full explanation →
Put the US Privacy string in regs.us_privacy, which is a first-class field in OpenRTB 2.6; on 2.5 and earlier it travels as regs.ext.us_privacy per the IAB extension. Read the answer →
Set regs.coppa to 1 when the request is subject to the COPPA regulations established by the US FTC, and 0 when it is not. Read the answer →
The DSA transparency extension carries EU Digital Services Act ad-transparency data through OpenRTB 2.x ext blocks. Read the answer →
device.dnt is the browser Do Not Track header flag, while device.lmt is the OS-level Limit Ad Tracking signal from mobile platforms such as iOS and Android. Read the answer →
When the user denies tracking, the OS advertising API returns an all-zero identifier, so device.ifa arrives as 00000000-0000-0000-0000-000000000000 or is omitted entirely, and device.lmt should be 1. Read the answer →
user.eids is an array of EID objects, each carrying one or more identifiers from a single ID source or technology provider. Read the full explanation →
user.id is the exchange's own identifier for the user (typically from the exchange's cookie), while user.buyeruid is the buyer's identifier for that same user, as mapped by the exchange for that specific bidder. Read the answer →
Cookie matching (ID syncing) is how an exchange and a DSP link their separate cookie IDs for the same browser so bid requests can carry a buyer-usable ID. Read the answer →
Put a SupplyChain object at source.schain in OpenRTB 2.6; on 2.5 it lives at source.ext.schain. Read the full explanation →
complete=1 asserts that the nodes array contains every entity in the payment chain back to the owner of the site, app, or other medium; complete=0 means the chain starts at the first known node and earlier hops are missing. Read the answer →
They are the verification layer for the path schain describes. Read the full explanation →
source.tid is a transaction ID that must be common across all participants in the bid request, so multiple exchanges auctioning the same impression (header bidding, for example) can be correlated and deduplicated. Read the answer →
Move the promoted ext fields to their first-class paths, switch enum references to AdCOM, and adopt the new video fields. Read the full explanation →
OpenRTB 2.6 added CTV pod bidding (podid, poddur, podseq, maxseq, rqddurs, slotinpod, mincpmpersec on video and audio), made SupplyChain, EID/UID, gdpr, and consent first-class objects and fields, and moved all enumerated lists out of the spec into AdCOM 1.0. Read the full explanation →
For most integrations, not yet: OpenRTB 3.0 has displaced very little 2.x traffic, and the 2.x line remains under active development, with IAB Tech Lab shipping regular 2.6 updates. Read the full explanation →
Since 2.6, IAB Tech Lab ships the spec as dated releases (2.6-202204, 2.6-202210, 2.6-202211, 2.6-202303, and onward through 2.6-202505) instead of new minor version numbers. Read the full explanation →
OpenRTB 2.5 and 2.6 carry the overwhelming majority of real-time bidding traffic; there are no reliable public numbers splitting the two, but 2.6 adoption keeps growing as CTV pod bidding and first-class privacy fields pull integrations forward, while plenty of production endpoints still speak 2.4 or 2.5. Read the answer →
Within the 2.x line, largely yes: revisions are mostly additive, so a 2.4 request is generally still parseable by a 2.6 endpoint. Read the answer →
AdCOM (Advertising Common Object Model) is the IAB Tech Lab spec that defines the domain objects of an ad transaction: media (the ad and its assets), placement (where it can run), and context (site, app, user, device, regs). Read the full explanation →
The authoritative sources are IAB Tech Lab's GitHub repositories, no PDF hunting required. Read the full explanation →
If the question is about a specific payload, paste it into the bid request tester: it validates against the exact OpenRTB 2.6 snapshot you pick, client-side, and each finding names the rule and the JSON path. The same checks run from the CLI in CI.