
Before launch
OpenRTB Partnership Preflight Checklist
Align roles, inventory context, protocol details, fields, privacy signals, endpoints, timeouts, reporting and test boundaries before production traffic begins.
Use the preflight checklistAdSelect resource desk
Prepare a cleaner OpenRTB test, trace a VAST failure without guesswork, and connect the transparency signals behind an app or CTV supply path. These resources are written for the operational conversation between publishers, supply platforms, demand platforms and buyers.
Three field guides
Each resource focuses on a distinct stage of a partnership: alignment before traffic starts, diagnosis when video delivery breaks, or verification of the declared selling path.

Before launch
Align roles, inventory context, protocol details, fields, privacy signals, endpoints, timeouts, reporting and test boundaries before production traffic begins.
Use the preflight checklist
When delivery breaks
Work through transport, XML, InLine and Wrapper logic, media compatibility, macros, tracking, player or SSAI behavior, latency and a controlled retest.
Follow the diagnostic sequence
Before buying or selling
Understand what app-ads.txt, sellers.json and the OpenRTB SupplyChain each answer, then cross-check their domains and seller identifiers together.
Validate the supply pathFrom article to action
Programmatic issues become difficult when each party is looking at a different request, time window, inventory description or definition of success. These guides are designed to help teams agree on the evidence before they interpret it.
A guide is not a substitute for the IAB Tech Lab specifications, player documentation, privacy requirements or the actual commercial agreement. It is a practical layer between those references and the working session: which questions to ask, which artifacts to retain, and how to limit the next test so its result can be explained.
Send the relevant checklist before the call and mark unknown details as unknown. That makes the gaps visible without filling them with assumptions.
Preserve request-level examples, timestamps and the full technical path. Change one variable at a time during the controlled retest.
Compare the agreed evidence, document remaining risks, and expand only when both teams can describe what the initial test established.
Related AdSelect pages
The resource explains the working method. The service and integration pages explain where that method fits within an AdSelect partnership discussion.
Review the information AdSelect asks for when scoping an endpoint and test.
See how a compatible video tag workflow is prepared and evaluated.
Understand how source evidence is mapped to the inventory being discussed.
Review the app, device, placement and supply-path context needed for CTV.
Bring the format, environment, markets, integration path and expected test scope. The AdSelect team will use the first conversation to determine whether there is a practical fit.
Schedule a Partnership Call