Build a server-to-server trading relationship with explicit inventory, auction and reporting requirements.
Explore traffic & setup examplesIdentify inventory formats, geographies, volumes and partner responsibilities.
OpenRTB is a protocol for exchanging advertising bid requests and responses. It allows compatible supply and demand systems to participate in real-time auctions.
OpenRTB carries bid requests and responses between systems. The inventory described in the request determines which kind of advertising experience can follow.
A supply partner describes an available banner placement, including its dimensions and allowed creative requirements. A demand partner evaluates that opportunity and can return a bid for an ad that fits the publisher’s page.
A bid response, an auction win and a rendered impression are separate events. Reconcile them using the agreed notification flow.
A video publisher describes an ad opportunity with player and media requirements. Eligible demand responds through the auction; the selected video creative then needs a compatible player and delivery path to reach the viewer.
Check duration, media types and placement context. Winning the auction does not establish that playback started or that the viewer completed it.
A publisher requests native assets such as a title, image and destination for a recommendation unit. The bid response supplies the required assets, and the publisher’s renderer assembles them within the surrounding page design.
Agree required assets and click or impression tracking. The ad should remain recognisable as sponsored content within its native layout.
Example inventory types, not a live supply catalogue. The protocol version, creative requirements and reporting events are agreed for each connection.
Identify inventory formats, geographies, volumes and partner responsibilities.
Validate request fields, responses, creative handling and notifications.
Increase volume after latency, delivery and reporting reconciliation checks.
Keep requests, bids, wins, delivery events and reconciled revenue distinct. Compare both partners’ records using an agreed timezone and event definition.
Protocol version, formats and notification support are agreed per connection. We validate partner compatibility before production traffic.
Share your supported versions and inventory types. The integration team will agree and test a compatible specification.
Yes. Include your supply or demand role, expected volumes and technical contact when requesting an integration review.
Tell us about your website, audience and current setup. We’ll map the next step together.