VPAID-simid-type-mismatch
SIMID <InteractiveCreativeFile> has VPAID-style type (application/javascript)
An element has . This is a migration mistake — it applies the VPAID MIME type to a SIMID element. SIMID creatives are HTML documents loaded into a sandboxed iframe; they must have . A JavaScript file alone is not a valid SIMID creative: it needs an HTML wrapper that implements the SIMID postMessage API.
Why this matters in production
Treat this as a hard compatibility failure. A VPAID rule that rises to error level is usually the difference between a runnable creative and a blank slot. Migration rules exist to get legacy interactive tags onto supported primitives such as SIMID and OMID before platform support gets even narrower.
How to fix
Change type to "text/html" on the <InteractiveCreativeFile> element. Wrap your JavaScript logic in an HTML document that implements the SIMID postMessage protocol.
Invalid
<!-- VPAID type copied to a SIMID element -->
<InteractiveCreativeFile type="application/javascript" apiFramework="SIMID">
<![CDATA[https://example.com/vpaid-style.js]]>
</InteractiveCreativeFile>Valid
<InteractiveCreativeFile type="text/html" apiFramework="SIMID">
<![CDATA[https://example.com/simid-creative.html]]>
</InteractiveCreativeFile>VPAID-simid-type-mismatch and other issues instantly.Validate a tag →