Validate the declared supply path
Cross-check the app store developer URL, app-ads.txt records, sellers.json identity and SupplyChain nodes before sending production traffic.
Read the supply-path guidePublisher Monetization for CTV, Video & Display
AdSelect helps publishers and supply partners structure OpenRTB and VAST connections for CTV, in-app video, in-app banner and web display inventory. We review each source before agreeing on a test.
Source-by-source onboarding
Quality-first review
Format and environment
Quality and verification context
OpenRTB or VAST test scope
A Practical Publisher Partnership
Every opportunity starts with a clear picture of the inventory, integration and quality expectations.
Demand Fit
We map each source's format, geography, traffic profile and expected volume to compatible demand before opening a test.
Source-Level Quality Context
Verification status varies by publisher and source. Where available, we share relevant Pixalate, DoubleVerify or HUMAN context instead of making a blanket quality claim.
Integration Options
Use OpenRTB for bidstream connections or VAST for compatible video workflows. Endpoint details, macros and required fields are agreed during onboarding.
Inventory AdSelect Can Evaluate
Format support and technical requirements are confirmed for each source before traffic begins.
Web & In-App Banner
Banner web and banner in-app opportunities with the site or app identifiers, placement details, sizes and geographies needed to assess demand fit.
In-App Video
Video in-app inventory evaluated with its app context, player and placement details, supported creative requirements and verification information.
CTV Inventory
Connected TV opportunities reviewed at the app or channel level, including device context, geography, content signals and the proposed VAST or OpenRTB path.
Details That Make a Supply Review Useful
A source name and endpoint are not enough to judge a programmatic opportunity. The information below helps AdSelect understand where inventory comes from, how it should be represented in the bidstream and what a responsible test should include.
Identity and Supply Path
Share the legal or commercial relationship to the inventory, relevant seller identifiers, app bundles or domains, store URLs and supply-chain nodes where they apply. Accurate identity information helps demand partners understand whether a source is direct or resold.
Format and Placement Context
Describe the available banner sizes, video player or placement type, CTV environment, supported protocols and the signals included in requests. This prevents a technically valid connection from being mistaken for a compatible opportunity.
Geography and Traffic Profile
Provide the principal geographies, expected request pattern and a realistic volume range for the proposed test. These details help both teams choose a limited starting scope and distinguish normal traffic variation from an integration problem.
Quality and Policy Context
Share available validation reports, known restrictions, consent signals and any brand-suitability or invalid-traffic requirements. A source may have Pixalate, DoubleVerify or HUMAN information; its status should be described precisely and reviewed alongside test data.
AdSelect uses these inputs to identify a compatible demand path, not to promise a particular level of spend or delivery. If the initial details support a test, the parties can then carefully confirm technical ownership, reporting and the criteria for expanding or stopping traffic.
Three Steps to a Controlled Test
01
Review
Share the domain, app or channel identifiers, formats, geographies, expected traffic profile and available verification context.
02
Align
Confirm the integration route, required fields, creative specifications, quality expectations and owners on both technical teams.
03
Test
Begin with limited traffic, compare logs, investigate discrepancies and expand only after both parties have reviewed the results.
What We Bring to Publisher Onboarding
Source Transparency
We ask for accurate ownership or reseller paths, seller identifiers, app or site identifiers and supply-chain information where it applies.
Technical Collaboration
Teams can compare request and response examples, review VAST playback behavior and troubleshoot integration differences with a shared test scope.
Quality Expectations Up Front
Inventory-quality, invalid-traffic and brand-suitability requirements are discussed before traffic starts, with source-level evidence reviewed where available.
Human Coordination
A clear contact coordinates onboarding questions, test status and next steps so technical and commercial decisions stay connected.
What We Review Before Testing
- 01Inventory environment, formats, placements and geographies
- 02OpenRTB endpoint or VAST workflow and required technical fields
- 03Seller, app, site and supply-chain identifiers where applicable
- 04Available Pixalate, DoubleVerify or HUMAN validation context
- 05Reporting, discrepancy and escalation process for the test
Prepare the evidence
Two guides to use before onboarding
A strong publisher conversation starts with a traceable supply path and a shared technical test plan. These AdSelect resources turn both subjects into practical working checklists.
Align the OpenRTB test first
Define roles, inventory context, fields, endpoints, privacy signals, timeouts, reporting and test boundaries before the first request.
Use the OpenRTB preflightHave Supply to Evaluate?
Bring the format, geography, source details and preferred integration path. The AdSelect team will help define a practical next step.
Schedule a Supply Call