Sorry. This form is no longer available.
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.
On July 24, The IAB Technology Laboratory released for public comment the tech specifications for OpenRTB 3.0, built upon the framework released last September, as the second part of a two-phase introduction to the ecosystem to promote healthy growth digital advertising programmatic marketplace. New specifications designed to support OpenRTB 3.0 are also being made available for public comment, including: ads.cert, AdCOM, and the Ad Management API.
The specifications will have a 60-day public comment period, running through September 24, 2018. Beta testing by the IAB Tech Lab OpenRTB Working Group will be ongoing. Industry members are encouraged to actively participate throughout the beta period, and to get involved with the OpenRTB Working Group. The group will evaluate and incorporate the feedback received, as well as real world insights from beta testing, to produce final specs that will be ready for full industry adoption by the end of the year.
Please reach out to [email protected] with feedback or questions.
READ THE PRESS RELEASE
VIEW THE OPENRTB 3.0 BETA SPEC, INCLUDING ADS.CERT BETA
SUPPORTING OPENMEDIA SPECS: ADCOM 1.0 BETA, AD MANAGEMENT API 1.0 BETA
Note: The new structure of the OpenRTB 3.0 Beta specification requires use of both OpenRTB (transactional specification) AND AdCOM (specification describing objects to be transacted). This layered specification approach is referred to as “OpenMedia.” Previous 2.X versions of OpenRTB were standalone specifications.
Previous Versions | Supporting Resources | Related Documents | OpenRTB Extensions
Real-time Bidding (RTB) is a way of 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 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 API Specification V 2.5
OpenRTB Dynamic Native Ads API Specification Version 1.2
OpenRTB 2.5 includes updates that integrate current trends and allows for improvements in programmatic technology. Release highlights include:
OpenRTB 2.4 introduces a brand new advertising medium to the protocol: digital audio. This is also the largest update to OpenRTB to date which includes improvements to private marketplace transactions, ability to declare skippable video ads, and additional fields in the bid-response allowing for more granular reporting capabilities. Release highlights include:
OpenRTB 2.3.1 provides an update to the specification addressing two typos:
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 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 provided for improved VAST video, tablet and location targeting support. Release highlights include:
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:
Version 1.2 of the OpenRTB Dynamic Native Ads API Specification has been finalized. Some of the added features include support for third-party ad serving, dynamic creative optimization (DCO), privacy flags, and new event tracking options. Any questions or comments for the OpenRTB Native working group can be sent to [email protected].
Download the OpenRTB Dynamic Native Ads API Specification Version 1.2
The Native Ads API 1.1 includes market-demanded improvements and features corresponding to the IAB Deep Dive on In-Feed Ad Units. Release highlights include:
Download the OpenRTB Dynamic Native Ads API Specification V1.1
This spec describes the outer native object, which includes the ad unit (the 6 types of native ads defined by the IAB Native Advertising Playbook) and the layout. While the Native Ads API is designed to be used with OpenRTB, it provides a set of fundamentals that are useful in non-RTB environments like in-app SDK object description.
OpenRTB Security Advisory 15-01, released December 2015
Guidance for DSPs and SSPs to mitigate botnet attack optimization tactics.
For more information or to join the OpenRTB Working Group, contact Jennifer Derke, Senior Manager, Product, at the IAB Tech Lab at [email protected].
Visit IAB Tech Lab’s OpenRTB page for supporting resources and tools.
Be the first to know. Sign up to receive news about the IAB programs, standards, events, classes, and more!