- Published
- Oct 29, 2026
- Updated
- Oct 31, 2026
- Reading time
- 11 min read
CTV VAST Trafficking: What to Check After Disabling VPAID
CTV delivery still low after disabling VPAID? Check serving mode, placement overrides, publisher renditions, tracking ownership and acceptance evidence.

In this guide (12 sections)
Disabling VPAID can remove an unsupported component from a CTV creative, but it does not establish that the remaining campaign is eligible to serve. Check the actual serving path, effective placement settings, available renditions, publisher approval and measurement agreement separately. Verify the response the publisher receives after the change.
If the serving layer assembles a new document from upstream responses, use the mixed-version response acceptance workflow to separate schema conformity from publisher playback support.
Do not assume that publisher-hosted video with tracking pixels is always preferable to a VAST tag, or that every VAST tag is accepted by every CTV publisher. The useful decision is which supported arrangement satisfies this publisher's delivery and measurement requirements.
An older public ad-operations question about CTV delivery after a “No VPAID” change describes exactly that uncertainty. The campaign remained underdelivered, and the operator asked whether publisher-hosted assets plus trackers would work better than third-party VAST serving. A separate archived question about CTV tagging asks whether standard tags or publisher-hosted files are required. These are real operational questions, not evidence that one arrangement universally performs better.
Start by identifying where delivery stops#
Before changing the creative again, ask the buying and publishing teams which stage is failing. Is the campaign receiving eligible opportunities? Is it bidding? Is the creative approved? Are wins followed by ad starts? Does video play while a measurement recipient receives nothing?
These observations point to different owners. A creative rejected before eligibility needs a support or approval investigation. A selected ad failing at playback needs a runtime trace. A playing ad with absent trackers needs a measurement handoff review. A low impression total alone cannot identify which occurred. For an IMA/Video.js integration where content and a linear ad overlap, audit the pause/resume handoff and application callbacks. Creative eligibility alone cannot establish exclusive playback.
Use the VAST errors and timeouts guide when a trace already identifies wrapper resolution or media loading as the failure. This guide focuses on getting the trafficking configuration and publisher handoff right before treating a timeout as the whole explanation.
Trace the CTV serving path.
Use the checklist to record the placement, creative response and player outcome for one test.
Use the tracking QA checklistOpens a practical guide. No email required.
Separate three things often called “the tag”#
Write down what each party actually receives. A media asset, a VAST response and a tracking URL have different jobs.
| Arrangement | What needs an explicit owner | What acceptance must establish |
|---|---|---|
| Video served through an accepted VAST path | Ad selection, assets, supported response and any intermediary | Publisher can use that exact serving path and receive suitable media |
| Publisher hosts the video and implements tracking | Asset version, insertion, event triggers and tracking delivery | Correct video and agreed measurement events are implemented together |
| Additional verification or measurement component | Component format, support, purpose and failure behavior | The integration supports the required measurement in the actual environment |
The table describes responsibilities, rather than guaranteed platform options. Obtain approval for the specific arrangement. A publisher accepting an MP4 does not automatically accept arbitrary JavaScript, an additional wrapper or every measurement component.
Also distinguish video from display. Advice about a standard image or iframe tag does not automatically apply to in-stream video. Keep the creative type, placement type and exported tag format together in the handoff record.
Check the creative type before treating every VAST URL alike#
Read the current documentation for the platform and creative type being trafficked. Similar-looking URLs can belong to materially different workflows.
For example, Campaign Manager 360's in-stream redirect documentation describes a creative with no assets that redirects to another VAST URL. It specifically says that its in-stream video redirect creatives are not supported in Display & Video 360. That restriction should not be generalized into a claim that Display & Video 360 rejects all externally hosted VAST creatives.
Google's separate CTV creative guidance includes supported hosting arrangements, publisher-specific creative checks and cautions about VPAID and tag wrapping. It recommends working with the publisher on its specifications. An extra measurement wrapper that worked on web video therefore needs its own CTV support check.
Describe the proposed path by creative type and platform, rather than saying “third-party tag.” Ask the receiving team to confirm the exact supported configuration before rebuilding the campaign around it.
Audit the effective placement settings#
A screenshot of the creative is not enough when the placement can change what is served.
In Campaign Manager 360's in-stream video settings, placement controls can override corresponding creative settings for companions, skipping and transcodes. The same creative can consequently produce different placement responses.
For an affected placement, record the assigned creative and ad, effective rendition selection, orientation, duration requirements and applicable publisher profile. Inspect the placement that is actually used, rather than an apparently identical test placement.
Next separate the measurement vendor's configuration from the ad server's adapter configuration. A change described as “No VPAID” in one system does not establish the state of another system. Google's placement reference describes its own VPAID adapter options and notes that changes can take two to three hours to appear in tags. That is a scoped platform timing statement, not a delay to apply to every vendor change.
Record what changed, where, when and which placements it affects. After the applicable propagation period, retrieve the response under the intended test conditions and verify the effective result. Do not claim the existing tag updated successfully from the settings screen alone.
Disabling an adapter can affect measurement availability. Ask which metrics remain supported before approving the change; restoring delivery by silently losing a required measurement is an incomplete repair.
Match the included renditions to the publisher#
Keep the uploaded source asset separate from the files actually included in serving. A suitable source does not establish that the outgoing response contains a suitable rendition.
Campaign Manager 360's serving-file documentation describes creative serving files, placement transcode controls and publisher eligibility checks. The practical consequence is to audit both the asset and the configuration selecting its renditions.
Build a short acceptance sheet containing the publisher's current requirements, the asset inspected and the file included for serving. Include format/codec, dimensions, aspect ratio, bitrate, duration and any required source or mezzanine treatment. Obtain the requirements from the actual publisher or platform guidance; do not copy one publisher's values across the whole buy.
Turning every transcode on is not a substitute for this check. Nor is disabling all but the smallest file. Select the versions required by the supported integration, then verify the response and processing state. If a required rendition is unavailable or still being prepared, record that specific hold.
For a MediaTailor insertion path, trace MediaTailor NEW_CREATIVE readiness with the affected request and preparation evidence. An eligible source file and a later successful play do not by themselves settle why an earlier personalized session had no prepared ad.
For publisher-hosted assets, ask who owns the uploaded version, replacement procedure and creative-to-campaign mapping. A corrected file sent by email is not proof that the publishing system replaced the original. Keep an identifiable version and acceptance confirmation.
Give each tracker a job and a sender#
If the publisher serves the asset, measurement becomes an explicit implementation responsibility. Agree which event triggers each URL, which system sends it and which recipient should record it. Separate impression tracking from start, quartile, completion and click tracking. Where one event has several legitimate recipients, audit the VAST event URIs and responsible sender. Multiple recipient notifications do not automatically represent multiple exposures, while duplicate dispatch is a separate finding.
Google's third-party video URL reference defines distinct interaction types. Its tracking guidance also explains that event tags included in video pre-fetch responses depend on the publisher firing them at the appropriate time. Presence in the configuration is therefore only one stage of verification.
For a small authorized test, preserve the configured URL, its location in the delivered response, the observed outgoing request and the recipient's matching record where available. Keep identifiers and tokenized URLs in restricted evidence.
Avoid attaching the same tracking obligation through several routes without documenting it. Ask whether a URL is already included by the ad server, supplied by a measurement component or separately added by the publisher. An inventory of senders helps prevent both missing implementation and accidental repeated reporting.
A received impression or completion request does not independently establish viewability, attention or suitability. For absent viewability signals, use the VAST ViewableImpression investigation. For server-side insertion, use the SSAI verification guide to document the actual event producer.
Add VAST Icons to the player acceptance test#
A playing video does not establish that its required disclosure interface works. Google's 19 October 2026 Ad Manager release notes, reviewed on 30 October, announce deprecation of the &wta parameter for in-stream video and audio by the end of 2026. The announcement says disclosures and badging will use standard VAST <Icons> and that no immediate tag changes are necessary: existing tags continue serving. Do not treat that scheduled change as proof that every production request already ignores the parameter, or as a reason to rewrite every tag now.
Google's parameter reference documents automatic ad-badging support with IMA. Without IMA, it says players must implement VAST Icon and IconClickFallbackImage support. A custom parser that extracts a media URL therefore needs a separate disclosure acceptance check; a parameter in the request cannot implement a missing interface.
An older archived Android TV developer question explicitly describes a custom VAST parser where IMA is unavailable and asks how to verify correctness. It does not concern the 2026 announcement or prove an icon defect. It illustrates why player responsibilities need acceptance evidence beyond successful playback.
Use IAB Tech Lab's VAST 4.3 specification, sections 2.3.7 and 3.11, for the icon resources, display and interaction contract. Its IconViewTracking notification concerns display of the icon. It is not an ad-impression, completion or independent viewability measurement.
Add these checks to a representative publisher/player test:
| Test branch | Acceptance evidence to retain |
|---|---|
Response contains <Icons> | Delivered response and wrapper context, parsed icon resources and selected display behavior |
| Icon display | Device recording showing the supplied icon in the actual ad experience, with its timing and placement checked |
| Disclosure interaction or fallback is supplied | Authorized interaction trace and the supported disclosure/fallback behavior, including how the viewer returns to playback |
| IMA integration | Exact SDK and application versions plus the representative runtime result; automatic support is not a substitute for checking the released integration |
| Test response contains no icon | Mark the branch unexercised; request a suitable authorized fixture rather than inventing an icon or claiming support from an absent test case |
Keep the app/player build, device/OS, SDK if used, insertion path, test time and response reference together. If an intermediary handles VAST before the player, identify who preserves the disclosure information and who renders it. Record unsupported behavior as a named acceptance hold with the publisher or implementation owner.
Verify that the tested build is the released build. An inspector result or an unreleased parser fix does not establish disclosure support across production TV apps. Keep this evidence separate from campaign delivery counts and from the measurement coverage affected by disabling VPAID.
Validate approval and eligibility before interpreting reach#
Ask for an explicit publisher acceptance result for the trafficked asset and path. Identify any required creative review, registration or reapproval after a material change. Record the approval's scope and date instead of interpreting a general platform status as publisher-wide acceptance.
Then inspect ordinary campaign eligibility alongside creative support: active assignments, dates, relevant targeting and any approval holds. Google's tag-testing guidance includes active creative/ad assignments and targeting conditions among the prerequisites for a useful test.
A desktop inspector can help establish that a response renders in that inspector. It cannot establish compatibility across all TV apps or prove that a publisher approved the creative. Preserve both the preliminary test and the publisher's representative acceptance evidence.
Do not disable safety or quality controls simply to make the tag deliver. Identify a failing requirement and propose a supported alternative with its measurement limits documented.
A hypothetical handoff audit with explicit holds#
Suppose a hypothetical campaign has ten intended publisher-placement paths after an adapter change. These are invented teaching figures, not customer results. The team assigns each path one initial review status:
| Initial review status | Paths |
|---|---|
| Configuration and publisher acceptance evidenced | 4 |
| Required serving rendition absent | 3 |
| Publisher creative approval still pending | 2 |
| Measurement support unresolved | 1 |
| Total reviewed | 10 |
Four of ten paths, or 40%, have the evidence required by this review. The other six need named actions. This is a path-readiness ratio, not an impression-weighted delivery rate, a reach estimate or a measure of money wasted.
The team first resolves the three rendition holds, then repeats the asset and publisher checks. It does not declare seven paths ready merely because files were uploaded. Processing, response inclusion and acceptance still need verification.
The remaining approval and measurement holds retain separate owners. After release, the team compares campaign delivery with the approved configuration and a comparable reporting interval. Increased impressions could have several causes; a configuration repair alone does not establish a causal reach improvement.
Close the handoff with a reviewable change request#
A useful request names one affected path and one proposed change. For example: “This placement excludes the rendition required by the publisher profile. Please confirm the correct effective setting and return a test response containing the approved file.”
Attach a concise record:
- Campaign, placement, ad and creative references, with dates and timezone.
- Proposed serving mode and publisher requirements.
- Original and proposed effective settings, plus change timestamps.
- Asset/rendition version, processing state and relevant approval.
- Tracking responsibilities, required metrics and unsupported behavior.
- Acceptance test, owner and unresolved holds.
Retest after each material change without replacing the original evidence. If delivery then occurs but parties report different totals, switch to the CTV impression reconciliation workflow. That count investigation has different denominators from this pre-launch acceptance review.
Frequently asked questions#
Does disabling VPAID automatically fix CTV underdelivery?
No. Confirm that the intended change reached the actual placement response, then check serving support, renditions, approval and campaign eligibility. A measurement vendor setting and an ad server adapter setting may be separate configurations.
Should every CTV campaign use publisher-hosted video plus pixels?
No universal preference follows. Use the arrangement accepted for the publisher, buying platform and measurement requirements. Publisher hosting also needs explicit asset-version, event-trigger and tracker-delivery ownership.
Should I enable every transcode to improve compatibility?
Check the required included renditions and effective placement controls. The goal is an accepted asset set for the actual publisher, rather than the largest number of files. Preserve evidence of processing, response inclusion and acceptance.
Does a successful VAST inspector test prove the CTV campaign is ready?
It proves an outcome in that test environment. Publisher acceptance, effective production configuration and representative device/insertion-path support still require evidence. Record missing measurement support as a limitation rather than silently treating it as success.
Connect acceptance evidence to campaign measurement#
For campaigns sending relevant events to AdProof, prepare a campaign-scoped export using matching dates, timezone and supported inventory filters. Bring the available delivery and video-stage counts to the publisher review alongside the trafficking and acceptance record.
AdProof's received measurements support reconciliation; they do not replace the publisher's creative approval, transcode inspection or runtime evidence. The anonymized streaming-publisher case study provides campaign-review context. Request an AdProof measurement review with the affected placement scope and the evidence needed to distinguish a serving hold from a tracking gap.
Trace the CTV serving path.
Use the checklist to record the placement, creative response and player outcome for one test.
Use the tracking QA checklistOpens a practical guide. No email required.
