VAST-2.0-inline-impression
<InLine> must contain at least one <Impression>
Short answer
Every inline ad must fire at least one <Impression> beacon. Without it, the impression cannot be measured, violating both the VAST spec and standard ad-ops contracts.
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 <InLine>.
VAST-2.0-inline-impression and other issues instantly.Open the VAST tag validator →