FAQ

OpenRTB 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.

OpenRTB basics and the bid request

The protocol, the auction, and the structure of a bid request: required fields, objects, and the conventions every integration relies on.

Debugging, no-bids, and validation

Why requests get dropped, why bids lose, what the no-bid codes mean, and how to validate payloads before they cost revenue.

Why is my bidder not receiving bid requests?

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 →

Why does my video bid never win?

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 →

Video, CTV, native, floors, deals, and macros

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.

Privacy, identity, supply chain, and versions

Consent and regulatory signals with their exact paths, schain, ads.txt and sellers.json, and how the 2.x line and 3.0 relate.

What changed in OpenRTB 2.6?

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 →

Which OpenRTB version is most used?

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 →

What is AdCOM?

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 →

Still stuck?

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.