Property identity
Provide the app bundle or channel identifier, store or public listing where available, publisher identity and the relationship to the inventory.
Connected TV
AdSelect evaluates connected TV opportunities for publishers, supply partners and demand partners through OpenRTB and VAST. App identity, device environment, placement, geography, scale, supply-path information and quality evidence are reviewed before a controlled test.
CTV context matters
Useful CTV evaluation connects the app or channel, content environment, placement, player or device context, supply path and reporting model. Missing or inconsistent metadata can prevent buyers from evaluating the opportunity correctly.
Provide the app bundle or channel identifier, store or public listing where available, publisher identity and the relationship to the inventory.
Describe where the ad appears, the viewing environment and any slot, pod, duration or creative constraints relevant to delivery.
Share app-ads.txt, sellers.json and SupplyChain information where applicable so the commercial path can be understood before testing.
State the countries or regions actually available for the source. AdSelect confirms market fit per opportunity rather than publishing universal coverage claims.
Provide realistic request volume or QPS guidance, traffic patterns and any limits needed to design a safe and useful test.
Identify the documentation available for this source, the measurement period and what the evidence does—and does not—cover.
Technical fit
AdSelect does not assume one integration is right for every CTV opportunity. The role of each party, supported delivery method and information available in the request or tag determine the test design.
Partners align on supported protocol details, CTV-relevant request fields, examples, timeouts, request scale, identifiers, supply-chain fields and response expectations.
Review the OpenRTB process →Partners review the declared VAST version, HTTPS delivery, macros, wrappers, media requirements, duration, tracking, errors and player or device constraints.
Review the VAST process →Controlled test
The test scope is documented before launch so both parties know what will be sent, how it will be measured and what happens if quality or reporting differs.
Confirm identity, environment, placement, markets, scale and supply path.
Review examples, required fields, tags, timeout expectations and contacts.
Set dates, traffic boundaries, reporting definitions and acceptance checks.
Compare delivery, discrepancies and quality before any expansion.
Quality and transparency
AdSelect reviews app identity, supply-path information, sample traffic and available third-party documentation in the context of the specific CTV source. Evidence for one app, period or measurement provider is not represented as a blanket certification.
See the full inventory quality approachAvailability depends on the specific supply or demand opportunity. Share the markets you need, and AdSelect will confirm whether a source-specific fit exists.
No. Request scale, buyer interest, delivery, quality and performance vary by opportunity. A controlled test is used to establish what is actually available.
Bring your role, app or channel information, device and placement details, target geographies, expected scale, integration preference, supply-path information and any quality documents available.
Tell us whether you are bringing supply or demand, the apps or environments involved, priority markets, integration method and expected scale.
Schedule a CTV Partnership Call