#openrtb

Verve publishes loss codes 1, 3, 4, 7, 9, 102, 103, 104, 202, and 206, and fills minimum bid to win on 102 and 103.

The same cat integer validates in JSON and still names a different vertical unless cattax names the taxonomy table OpenRTB should assume.

Xandr loss codes 1, 3, 4, 5, 6, 7, 8, 9, 100, and 102 are the response and price failures in its public lurl table.

Google creative statuses 14, 189 through 193, and 200 through 203 cover sensitive categories, SDK ids, OMSDK, COPPA, and GDPR vendor consent.

Google creative status codes 168 through 176 and 180 name the VAST media file, the document, or the VAST version that failed.

AdCP closes deals over MCP; exchanges and players still read OpenRTB and VAST. Success on the agent layer does not prove those payloads exist or match what was sold.

Google Authorized Buyers uses loss reason 501 for a mediation loss. Creative status codes such as 79, 166, and 195 are a different field.

AAMP Agentic Deals can finish a programmatic video line while the forwarded OpenRTB imp still misses the deal id, duration window, or AdCOM placement the buy assumed, and both JSON layers can validate clean.

Digital Turbine maps timeouts, bad domains, SKAdNetwork, and bundle format onto specific loss codes, including 1010.

Native 1.2 hides its contract inside imp.native.request and adm strings. Each side can look valid alone and still lose the auction or render blank.

Chartboost redefines 211, keeps 206 as a bundle exclusion, and adds 502 plus 1000 through 1003.

Equativ 1001 through 1007 cover currency, native markup, SKAdNetwork, creative error rate, and publisher blocks.