VAST-3.0-icon-resource
<Icon> must have at least one resource element
Short answer
Like companions and nonlinear creatives, <Icon> elements must contain at least one renderable resource: <StaticResource>, <IFrameResource>, or <HTMLResource>.
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 3.0, 4.0, 4.1, 4.2, and 4.3.
How to fix
Add <StaticResource>, <IFrameResource>, or <HTMLResource> inside <Icon> to supply the renderable asset.
VAST-3.0-icon-resource and other issues instantly.Open the VAST tag validator →