OpenRTB

OpenRTB
Name	OpenRTB
Developer	IAB Technology Lab
Initial release	2011
Programming language	JSON
Operating system	Cross-platform
License	Open specification

OpenRTB OpenRTB is an open specification for automated online advertising transactions that standardizes bid requests and responses used in real‑time bidding exchanges. It defines JSON‑based message formats and semantics for interaction among demand‑side platforms, supply‑side platforms, ad exchanges, and ad servers, enabling interoperable marketplaces among entities such as Google, Facebook, The Trade Desk, AppNexus, and PubMatic. The protocol underpins programmatic advertising workflows connecting inventory sources like DoubleClick, OpenX, Rubicon Project, Index Exchange, and publishers including The New York Times and Hearst Corporation.

Overview

OpenRTB provides a common vocabulary and message model to express ad impressions, user signals, device context, and bidding metadata in a machine‑readable fashion. Major ecosystem participants such as Amazon (company), Microsoft, Verizon, Comcast, and WPP (company) rely on the specification to integrate demand and supply. The specification supports formats for native ads, video, audio, and display, allowing interoperability between platforms like YouTube, Spotify, Hulu, The Guardian, and CNN. Governance by industry bodies including IAB (Interactive Advertising Bureau), IAB Tech Lab, and collaboration with vendors such as Adobe Systems, Oracle Corporation, and Sizmek has promoted adoption across exchanges and agencies such as Omnicom Group, Publicis Groupe, and IPG (company).

Protocol and Message Structure

OpenRTB uses JSON schemas to represent core objects: the bid request, impressions, device, user, site, app, and bid response. Key fields map to ad inventory attributes used by platforms like DSP (advertising) vendors such as MediaMath, DataXu, and Criteo, and exchanges like LiveIntent and SMAData. The protocol defines nested objects for geo‑location with references to services like MaxMind, and user identifiers interoperable with identity providers such as ID5, The Trade Desk Unified ID, and LiveRamp. For video and native ads, OpenRTB aligns with media specifications from VAST, VPAID, and OM SDK to ensure compatibility with players from JW Player, Brightcove, and ThePlatform. Message-level features include auction type, bid floor, currencies aligned with standards from ISO 4217, and ad markup formats compatible with creative management systems from Celtra and Sizmek.

Adoption and Implementations

OpenRTB is implemented in major ad tech products and exchanges including Google Ad Manager, Xandr (formerly AppNexus), Rubicon Project, Index Exchange, and header bidding wrappers from vendors like Prebid.js and Amazon Transparent Ad Marketplace. Agencies and advertisers from groups such as GroupM, Dentsu, and Havas use DSPs integrated via OpenRTB to reach publishers such as Vox Media, BuzzFeed, and Condé Nast. Open source implementations and SDKs are available in ecosystems like GitHub and supported by cloud providers including AWS, Google Cloud Platform, and Microsoft Azure, facilitating deployment by ad ops teams at companies like The Trade Desk and integrators like Accenture Interactive.

Privacy, Security, and Regulatory Considerations

The OpenRTB flow carries personal data and identifiers, implicating regulatory regimes such as General Data Protection Regulation and California Consumer Privacy Act. Privacy frameworks like IAB Europe Transparency and Consent Framework and identifiers from Interactive Advertising Bureau initiatives intersect with OpenRTB fields to express user consent and signal suppression for vendors such as DoubleClick for Publishers. Security practices include TLS encryption choices recommended by authorities including NIST and integration with fraud detection services from Integral Ad Science, DoubleVerify, and Moat (company). Industry responses to regulatory actions by institutions such as European Commission and enforcement by bodies like Federal Trade Commission influence how exchanges, SSPs, and DSPs implement consent strings, data minimization, and auction rules tied to OpenRTB.

Performance and Scalability

OpenRTB implementations must meet sub‑100 millisecond latency targets for bid responses in real‑time auctions conducted by exchanges like Rubicon Project, Index Exchange, and platforms run by Google and Xandr. Scalability patterns employ load balancing from vendors such as F5 Networks, caching techniques popularized by Varnish Software, and stream processing frameworks like Apache Kafka, Apache Flink, and Apache Storm to handle high throughput. Latency optimization involves compact JSON payloads, use of HTTP/2 and QUIC protocols promoted by IETF, and edge deployment strategies using content delivery networks such as Akamai Technologies and Cloudflare. Observability and instrumentation often rely on tools from Datadog, New Relic, and Prometheus to monitor bid win rates, auction dynamics, and system health under traffic patterns seen during events like Black Friday and Super Bowl ad surges.

History and Governance

The specification emerged from the Interactive Advertising Bureau with stewardship by the IAB Tech Lab, evolving through revisions to address video, native, and mobile contexts influenced by players such as Admeld, Right Media, and early exchanges like OpenX. Governance is maintained by working groups composed of representatives from companies including Google, Facebook (company), The Trade Desk, AppNexus, and agency bodies like IAB UK and IAB Australia. Major version updates responded to market shifts driven by the rise of mobile platforms like iOS, Android (operating system), and the proliferation of connected TV vendors such as Roku, Samsung Electronics, and LG Electronics, while compliance adjustments tracked actions by regulators such as European Data Protection Supervisor and industry initiatives like the Ads.txt project.

Category:Advertising