VAST-4.1-verification-no-resource
<Verification> should have JavaScriptResource or ExecutableResource
Short answer
A <Verification> element with no resource child cannot actually execute the verification script. At least one <JavaScriptResource> or <ExecutableResource> is expected.
Why this matters in production
This rule is a strong risk signal. Tags with this issue often still parse, but they become brittle across SDKs, SSAI resolvers, and CTV environments. 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 4.1, 4.2, and 4.3.
How to fix
Add <JavaScriptResource apiFramework="omid"><![CDATA[https://cdn.example.com/omid.js]]></JavaScriptResource> inside <Verification>.
VAST-4.1-verification-no-resource and other issues instantly.Validate a tag →