Response structure
Confirm that the response is well formed and that the declared version and elements match what the receiving environment supports.
Video tag readiness
AdSelect evaluates compatible VAST opportunities by reviewing the source, playback environment, declared VAST details, tag behavior, media requirements, tracking, errors, expected scale and reporting model before a controlled test.
Compatibility before volume
A tag can return XML and still fail in a real player because the version, media file, wrapper chain, duration, HTTPS delivery, macros, tracking or timeout behavior is incompatible with the environment.
Confirm that the response is well formed and that the declared version and elements match what the receiving environment supports.
Review HTTPS delivery across the tag, wrappers, media and tracking resources to avoid mixed or blocked requests.
Understand wrapper depth, redirects, timeout risk, inherited tracking and the error path if a downstream response is empty or unavailable.
Review media types, dimensions, duration, bitrate or other player constraints that affect whether a creative can render.
Document required macros, encoding expectations and source identifiers so requests and reporting remain attributable.
Align on impression and event tracking, error handling, log fields and who investigates failures during the test.
Environment-specific review
The tag must be evaluated in the environment where it will run. Device, app, player or SDK behavior and placement requirements can change compatibility and measurement.
Review the app or channel, device environment, placement or pod context where applicable, supported media behavior, remote playback constraints and source-level transparency.
CTV partnership details →Review the bundle ID, store listing, operating system, player or SDK context, placement behavior, app-ads.txt status and the quality evidence available for the app.
In-app partnership details →VAST preflight
Preflight reduces avoidable errors and gives both partners the same definition of a working response before live traffic increases.
Confirm source, environment, placement, markets, scale and tag role.
Check structure, HTTPS resources, macros, wrappers, media and tracking.
Test in a representative player or environment and record failures.
Run agreed traffic, dates, timeouts, monitoring and escalation contacts.
Compare delivery, events, errors, filtering and quality before scaling.
When delivery fails, partners collect the response, timestamp, environment, declared error, wrapper path and relevant log evidence. This makes it possible to separate malformed responses, unsupported media, timeout behavior, empty downstream tags and tracking differences.
Ad starts, impressions, quartiles, completes and errors can be recorded at different points by different systems. The test documents which events are compared, the time zone and period, filtering and the threshold that triggers investigation.
Compatibility is confirmed for the specific partner, tag and playback environment during technical review. AdSelect does not publish a universal version promise without that context.
A tag test follows source, environment, placement, compatibility, timeout, reporting and quality review so the result answers a defined question.
No. Delivery also depends on player compatibility, media resources, wrappers, timing, macros, tracking and the live environment.
Share the source, environment, placement, declared version, tag example, media requirements, markets and expected scale.
Schedule a VAST Integration Call