VASTlint
Validate
VMAP-1.0-display-break-no-companions

VMAP-1.0-display-break-no-companions

breakType includes "display" but the inline VAST has no <CompanionAds> to fill the break

InfoVMAPIAB VMAP 1.0.1 §2.3.1VMAP 1.0 (all VMAP documents)

Short answer

An <AdBreak> whose breakType includes display requests display/companion ads, which VAST delivers through <CompanionAds>. The inline <VASTAdData> in this break contains no companions, so the break has nothing to display. Add <CompanionAds> to the embedded VAST, or drop display from breakType if the break is video-only. Breaks that reference ads via <AdTagURI> are not checked, since the ad response is fetched at play time.

Why this matters in production

This rule is advisory rather than fatal, but it still matters for portability, debugging speed, and keeping tags predictable across different buyers and playback stacks. VMAP rules validate the ad break schedule envelope. Malformed break timing, wrong namespace declarations, or invalid AdSource content prevent players from resolving any of the ads in the playlist. Affected scope: VMAP 1.0 (all VMAP documents).

Check your VAST tag for VMAP-1.0-display-break-no-companions and other issues instantly.Open the VAST tag validator →

Other VMAP rules

VMAP-1.0-root-versionRoot `<VMAP>` element must have a version attributeVMAP-1.0-root-version-value`<VMAP>` version attribute should be `"1.0"` — the only published VMAP versionVMAP-1.0-root-namespace`<VMAP>` should declare the VMAP namespace URI http://www.iab.net/videosuite/vmapVMAP-1.0-root-unknown-child`<VMAP>` may only contain `<AdBreak>` and `<Extensions>` elementsVMAP-1.0-adbreak-timeoffset`<AdBreak>` must have a timeOffset attributeVMAP-1.0-adbreak-timeoffset-format`<AdBreak>` timeOffset must be hh:mm:ss[.mmm], n%, `"start"`, `"end"`, or #mVMAP-1.0-adbreak-breaktype`<AdBreak>` must have a breakType attributeVMAP-1.0-adbreak-breaktype-value`<AdBreak>` breakType must be a comma-separated list of `"linear"`, `"nonlinear"`, or `"display"`