OpenRTB 2.3
What this release is
OpenRTB 2.3 brought native advertising into the protocol: imp.native, the JSON-encoded native request payload, and the asset negotiation model between supply and demand. The native request's string-in-string encoding decision made here is still the source of the double-encoding bugs validators catch a decade later.
Available coverage
- Release documentation
- Available
- Extracted object catalog
- Available
- JSON Schemas
- Available
- Exact-snapshot validation
- Supported
What changed in 2.3
| Change | Kind | Summary |
|---|---|---|
| imp.native | Added object | OpenRTB 2.3 introduced native ad placements directly on the impression object. |
| imp.native.request | Added field | OpenRTB 2.3 added the native request payload for declaring required assets and fields. |
| native.assets | Added behavior | OpenRTB 2.3 allowed supply and demand to negotiate native asset availability and requirements in the bidstream. |
Validate against 2.3
The tester can pin validation to this exact revision, so deprecated, moved, and not-yet-available findings reflect what 2.3 actually says. The same pin works in the CLI: rtblint validate --version 2.3 request.json.
Adjacent versions
- Previous: OpenRTB 2.2
- Next: OpenRTB 2.3.1
- All versions: version index
- Migrating across the big steps: 2.5 vs 2.6 and 2.6 vs 3.0