VAST-2.0-wrapper-impression
<Wrapper> must contain at least one <Impression>
Short answer
Wrapper-level impression beacons are fired in addition to those in the eventual <InLine>. At least one is required so the intermediary ad server can record its impression.
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. Required-field failures usually stop validation early because the platform cannot determine the basic shape of the ad, the creative metadata, or the mandatory tracking payload. Affected scope: VAST 2.0 and later (all versions).
How to fix
Add <Impression><![CDATA[https://track.example.com/impression]]></Impression> inside <Wrapper>.
VAST-2.0-wrapper-impression and other issues instantly.Open the VAST tag validator →