VAST-2.0-companion-resource
<Companion> must contain at least one StaticResource, IFrameResource, or HTMLResource
Short answer
A <Companion> element must carry at least one resource that can actually be rendered: <StaticResource>, <IFrameResource>, or <HTMLResource>. An empty companion is not valid.
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 <StaticResource>, <IFrameResource>, or <HTMLResource> inside each <Companion> to supply the renderable asset.
Invalid
<Companion width="300" height="250">
<!-- no resource -->
</Companion>Valid
<Companion width="300" height="250">
<StaticResource creativeType="image/png">
<![CDATA[https://cdn.example.com/companion.png]]>
</StaticResource>
</Companion>VAST-2.0-companion-resource and other issues instantly.Validate a tag →