VAST-2.0-ctv-portfolio-mediafiles-required
<Extension type="ctv_ad_portfolio"> carries no <MediaFiles>
Short answer
The extension exists to supply the media delivery model VAST 2.0 <NonLinear> never had. When the bound creative also has no native <StaticResource>, <IFrameResource> or <HTMLResource> to fall back to, nothing renders. Signalling-only use of the container is fine when the creative renders natively.
Why this matters in production
This rule is usually a delivery blocker. Many players, SDKs, and ad servers will discard the response or skip the affected creative once this condition is hit. The CTV Ad Portfolio standardises Pause, Screensaver, Overlay, Squeezeback and In-Scene ads, which ran for years on bespoke per-publisher integrations. These rules cover the VAST side of that contract: the NonLinear MediaFiles delivery model, the AdCOM signals round-tripped into Extensions so stitchers can validate the experience without the bid object, and the QR code block. The signaling guidance is final; the VAST 4.4 schema that accompanies it is still a working-group draft, so anything sourced only from the schema is reported as a warning or a note. Affected scope: VAST 2.0 and later (all versions).
VAST-2.0-ctv-portfolio-mediafiles-required and other issues instantly.Open the VAST tag validator →