In-app video
Describe the placement type, player or SDK context, declared VAST details where relevant, supported creative requirements, duration constraints, tracking expectations and how users encounter the placement.
Programmatic video overviewApp inventory partnerships
In-App Advertising for Video and Banner Partnerships
AdSelect evaluates in-app video and banner opportunities for supply and demand partners. App identity, placement details, operating environment, markets, expected scale, integration requirements and available quality evidence are reviewed before testing.
Supported opportunity types
Video and banner require different inputs
The app is only the starting point. Placement behavior, creative requirements, delivery method and measurement determine whether a source and demand opportunity are compatible.
In-app banner
Describe supported sizes, placement location, refresh behavior if any, device orientation, creative limitations, interaction model and the information present in the OpenRTB request.
OpenRTB integration overviewApp transparency
What AdSelect reviews before a test
Reviewable app inventory connects the public app identity, the entity selling it and the request or tag that represents the placement.
App identity
Bundle ID, store URL, publisher or developer identity, category and the operating systems involved.
Authorized selling path
app-ads.txt, sellers.json and SupplyChain information where applicable, plus a clear statement of the source relationship.
Placement truth
Format, placement behavior, device context and creative constraints that match what is represented in the request.
Market and scale
Countries or regions actually available, expected request volume or QPS, traffic patterns and safe test limits.
Quality evidence
The document, dashboard extract or assessment available for the source, including its period and scope.
Measurement alignment
Definitions for requests, bids, impressions, video events, errors, filtering, time zone and discrepancy review.
Integration fit
OpenRTB for app opportunities; VAST where video delivery requires it
The exact integration depends on the role of each party and the app placement. Supported protocol and tag details are confirmed during technical review rather than assumed from the format label.
OpenRTB review
Share supported protocol details, app and impression objects, examples, request scale, timeouts, identifiers, privacy fields, supply-path data and response expectations.
See the OpenRTB workflow →VAST review for video
Share the declared version, HTTPS delivery, macros, wrappers, media requirements, duration, tracking, errors and player or SDK constraints.
See the VAST workflow →Controlled onboarding
How an in-app test is structured
- 01
Identify
Confirm the app, publisher relationship, placement, format, markets and scale.
- 02
Validate
Review app-ads.txt, supply path, samples, quality evidence and technical compatibility.
- 03
Test
Agree dates, traffic boundaries, reporting definitions, success checks and contacts.
- 04
Review
Compare delivery, discrepancies and quality signals before deciding whether to scale.
Quality evidence stays source-specific
A quality assessment for one app, publisher, period or source is not applied to unrelated inventory. AdSelect records what documentation is available and what it covers, then uses test data to review the live opportunity.
Inventory quality and transparencyAvailability and results are not guaranteed
Format, geography, request scale, demand, delivery and performance vary by opportunity. The purpose of a controlled test is to establish whether the source and partner are a fit using agreed evidence.
Discuss a test scopeHave in-app video or banner to evaluate?
Share the app identity, placement, format, markets, expected scale, integration method and quality documentation available.
Schedule an In-App Partnership Call