oRTB Bid Request Validator

What this validator checks

Every bid request is checked against the IAB Tech Lab OpenRTB spec for the version you pick, plus the checks DSPs apply in practice before they decide to bid.

• Required fields: request id, a non-empty imp array, a unique imp.id and at least one of banner, video, audio or native.
• Data types: floors as numbers, flags as 0 or 1, currency as ISO-4217 codes, country as ISO-3166 alpha-3.
• Media rules: video mimes and VAST protocols, banner sizes, native request strings, pod fields in 2.6.
• Privacy signals: GDPR flag with a TCF consent string, us_privacy format, GPP string with section IDs, COPPA.
• Supply chain: schain presence, node fields, and whether it sits where your spec version expects it.
• Bidability: missing user agent, IP, advertising ID or publisher ID, the things that quietly cut bid rates.
• Auto-fix: string floors and ids, true/false flags, 2-letter countries, lowercase currencies and schain basics are fixed in one click, and fields are copied to the 2.5 or 2.6 location. Ids, prices and consent are never invented.
• Logs: paste or open a file with one request per line, even with timestamps in front, and see which problems repeat across all of them.

OpenRTB 2.5 vs 2.6: where fields moved

Version 2.6 promoted several fields out of ext. Many exchanges send both locations while their buyers migrate.