A planned inspector for OpenRTB bid requests and responses. The first version will focus on deterministic checks for OpenRTB 2.6, AdCOM lists, privacy fields, supply chain objects, and CTV video pods.
OpenRTB debugging guide
OpenRTB Inspector is planned as a deterministic debugging tool for bid requests and bid responses, with a focus on practical checks that help ad ops, marketplace quality, solutions, and engineering teams find integration issues quickly.
The planned inspector will check core OpenRTB objects such as site, app, device, user, source, regs, imp, video, banner, audio, native, and private marketplace fields.
Planned diagnostics include consent, privacy regulation fields, schain shape, sellers.json-adjacent signals, identity fields, and other request details that often explain bid filtering.
The roadmap includes checks for video pod fields, placement details, rewarded and instream context, duration ranges, MIME types, protocols, and fields used by CTV demand partners.
Not yet. The route is published as a coming-soon page while the validator, examples, and report model are built out.
The initial roadmap focuses on OpenRTB 2.6 and related AdCOM list validation, then can expand as more version coverage is needed.
The planned first version is an inspector and validator, not a live bidder traffic generator. The goal is to analyze payload structure and debugging context safely.
VAST Inspector focuses on video ad responses and playback diagnostics. OpenRTB Inspector will focus upstream on bid request and response quality before the ad response is served.