VAST-2.0-ctv-portfolio-no-renderable-asset
<Extension type="ctv_ad_portfolio"> has a SIMID file but no <MediaFile> fallback
Short answer
A SIMID-only payload renders nothing on a player without SIMID support, which on CTV is most of them. Ship a <MediaFile> in the extension, or a native <NonLinear> resource on the bound creative, so the impression is not lost on devices that cannot execute the interactive file.
Why this matters in production
This rule is a strong risk signal. Tags with this issue often still parse, but they become brittle across SDKs, SSAI resolvers, and CTV environments. 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-no-renderable-asset and other issues instantly.Open the VAST tag validator →