Bid request
Inventory, device, site or app and impression details are expressed in a structured request.
Understand OpenRTB integration, bid requests, bid responses and auction workflows for interoperable real-time bidding across programmatic advertising systems.
OpenRTB standardizes how compatible programmatic systems describe an auction opportunity and respond with eligible bids.
Inventory, device, site or app and impression details are expressed in a structured request.
The receiving bidder evaluates campaign eligibility, pricing and creative compatibility.
Eligible bids return price, creative and required response metadata within the auction timeout.
The exchange applies auction rules, chooses a result and continues delivery and measurement.
OpenRTB gives programmatic systems a shared structure for describing an auction opportunity, evaluating it and returning an eligible bid within a strict time budget.
Represent impression, site or app, device, user/privacy, deal and supply-chain context in a structured object.
The bidder checks campaign, price, creative, policy and timeout eligibility.
Eligible demand returns bid price, creative and response metadata before the auction deadline.
The exchange evaluates valid responses and continues delivery and measurement.
Bid requests processed per second across the integration.
The share of requests that receive a valid demand response.
The maximum response window allowed before a bid becomes unusable.
Completeness and consistency of objects used by downstream decision systems.
Estimate daily bid-request volume, valid responses and rough request-payload transfer from a sustained QPS assumption.
Connect compatible demand and supply platforms through a structured transaction contract.
Evaluate requests, apply campaign logic and return valid responses within timeout.
Carry seller and supply-chain context that supports marketplace trust and quality checks.
Understand OpenRTB integration, bid requests, bid responses and auction workflows for interoperable real-time bidding across programmatic advertising systems.
A bid request describes an eligible impression opportunity using structured fields for inventory, media format, device or app context, deals, supply-chain information and other permitted signals. Buyers should only rely on fields that are present, valid and allowed for the transaction.
A bid response can return a price, creative reference or markup, deal information and tracking-related fields when the buyer chooses to participate. Responses still need to pass the seller's eligibility, policy and auction rules.
OpenRTB 2.x refers to the widely adopted family of OpenRTB 2-series specifications. Production integrations should document the exact version, supported objects, extensions and validation rules rather than assuming universal field support.
RTB describes the real-time auction process. OpenRTB is a standardized protocol used by compatible systems to communicate bid opportunities and responses during programmatic transactions.
An ad exchange can use OpenRTB as an interoperability layer between eligible supply and demand systems while applying its own auction, pricing, privacy, fraud and commercial controls.
OpenRTB standardizes communication, not business outcomes. Integration quality still depends on field validation, timeout handling, privacy signals, supply-chain transparency, creative safety and auction policy.
No. RTB is the auction process; OpenRTB is a protocol for exchanging structured bid-request and bid-response data between compatible programmatic systems.
No. Implementations can differ by specification version, media type, extensions, privacy requirements and platform capability, so supported fields should be documented and validated.