OpenRTB 2.0
What this release is
OpenRTB 2.0 is the release that made real-time bidding a shared protocol rather than a pile of exchange-specific APIs. It consolidated the earlier mobile and display efforts into one object model: BidRequest and BidResponse, imp, banner, video, site, app, device, and user. Every later 2.x version is an extension of this shape, which is why 2.0-era payloads still parse recognizably today.
Available coverage
- Release documentation
- Available
- Extracted object catalog
- Available
- JSON Schemas
- Available
- Exact-snapshot validation
- Supported
What changed in 2.0
| Change | Kind | Summary |
|---|---|---|
| device.geo | Added behavior | OpenRTB 2.0 improved geographic data handling across mobile and desktop transactions. |
| device.ifa | Added field | OpenRTB 2.0 added mobile device ID support for attribution and audience handling. |
| imp.video | Added object | OpenRTB 2.0 unified display, mobile, and video bidding around the shared Video object and VAST ad-unit support. |
| user.data | Added field | OpenRTB 2.0 expanded support for third-party audience data segments. |
Validate against 2.0
The tester can pin validation to this exact revision, so deprecated, moved, and not-yet-available findings reflect what 2.0 actually says. The same pin works in the CLI: rtblint validate --version 2.0 request.json.
Adjacent versions
- Next: OpenRTB 2.1
- All versions: version index
- Migrating across the big steps: 2.5 vs 2.6 and 2.6 vs 3.0