OpenRTB 3.0 Draft Framework Open for Public Comment
OpenRTB 3.0 is the largest overhaul of the OpenRTB protocol since its inception in 2010. The purpose of this major update is to meet the market’s demand for security, transparency, authentication, and trust in programmatic advertising. Specifically, three major changes are being proposed:
- A new process of cryptographically signed bid requests to view the inventory path, enabling the demand side to validate many of the fields in the bid request
- A more flexible object model in the specification with the new AdCOM (Advertising Common Object Model)
- New ways to transmit display demand to enable safer creative controls for publishers with Ad Management API Standard
This document, OpenRTB 3.0 Framework, released in early September for a 3-month public comment period is not a full specification yet. We encourage the industry to provide feedback on workflows and technical implementation of 3.0 as soon as possible. Readers will find accompanying resources and some companion specifications also available for public comment. Comments and feedback may be submitted using this form. Public comments are open until December 15, 2017.
|Previous Versions||Supporting Resources||Related Documents||OpenRTB Extensions|
Real-time Bidding (RTB) is a way transacting media that allows an individual ad impression to be put up for bid in real-time. This is done through a programmatic on-the-spot auction, which is similar to how financial markets operate. RTB allows for Addressable Advertising; the ability to serve ads to consumers directly based on their demographic, psychographic, or behavioral attributes.
The Real-Time Bidding (RTB) Project, formerly known as the OpenRTB Consortium, assembled by technology leaders from both the Supply and Demand sides in November 2010 to develop a new API specification for companies interested in an open protocol for the automated trading of digital media across a broader range of platforms, devices, and advertising solutions. At the time Programmatic had only accounted for 4% of the display advertising market. By 2017, RTB is expected to account for 29% of the digital mix. *Source: eMarketer March 2013. This group continues to create open industry standards that ensure all parties, buy and sell side alike, can transact RTB at scale and build future industry innovation.
| OpenRTB 2.5 (PDF)
OpenRTB 2.5 includes updated that integrate current trends and allows for improvements in programmatic technology. Release highlights include:
| OpenRTB 2.4 (PDF)
OpenRTB 2.4 main improvements:
| OpenRTB 2.3.1 (PDF)
Provides an update to the specification addressing two typos:
| OpenRTB 2.3 (PDF)
The OpenRTB 2.3 specification provides support for native ads. This is one of the most significant updates to OpenRTB as it allows for native ads to be targeted, optimized, and transacted on programmatically, reducing workload on publishers and advertisers alike. Release highlights include:
| OpenRTB 2.2 (PDF)
OpenRTB 2.2 provided for improved PMP and non-intentional traffic support. With bot traffic becoming an increasing concern to both the buy and sell sides, OpenRTB 2.2 allows for all parties to be able to provide real-time feedback on ads to determine and block non-human traffic. Release highlights include:
| OpenRTB 2.1 (PDF)OpenRTB 2.1 provided for improved VAST video, tablet and location targeting support. Release highlights include:
| OpenRTB 2.0 (PDF)OpenRTB 2.0 provided unified support for display, mobile, and video capabilities. This was a significant step forward for programmatic as allows for the harmonization of mobile and desktop advertising. Release highlights include:
OpenRTB Advisory – GDPR
Tech Lab CodeBank: OpenRTB
Tech Lab Tool: OpenRTB Bid Validator
OpenRTB Security Advisory 15-01 (PDF) Released December 2015
Guidance for DSPs and SSPs to mitigate botnet attack optimization tactics.
Extensions to OpenRTB
The new version 1.2 of the OpenRTB Dynamic Native Ads API Specification is in public review. Some of the added features include support for third-party ad serving, dynamic creative optimization (DCO), privacy flags, and new event tracking options. Please review and send your questions or any feedback to email@example.com by May 17, 2017.
IAB Tech Lab Releases Protocols For OpenRTB (Press Release)
Developed by the OpenRTB Working Group
IAB Tech Lab Contact
Director of Product, Programmatic & Data