Skip to content
Home Publishers Advertisers Solutions Resources About Contact Schedule a Call

AdSelect resource desk

Practical guides for programmatic partnerships

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

Start with the problem in front of you

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.

OpenRTB bid-request flow between two validated endpoints

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 checklist
VAST diagnostic path resolving through wrappers into video playback

When delivery breaks

VAST Troubleshooting Guide

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
Authenticated app inventory supply path with connected seller nodes

Before buying or selling

Supply-Path Transparency Guide

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 path

From article to action

Use one shared fact pattern

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.

Prepare

Send the relevant checklist before the call and mark unknown details as unknown. That makes the gaps visible without filling them with assumptions.

Diagnose

Preserve request-level examples, timestamps and the full technical path. Change one variable at a time during the controlled retest.

Decide

Compare the agreed evidence, document remaining risks, and expand only when both teams can describe what the initial test established.

Have a live opportunity behind the question?

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