SIMID-1.0-simid-url-data-html
SIMID data: URI must declare text/html
Short answer
VAST 4.3 allows data: URIs on resource URLs. SIMID §3.1 still requires an HTML document loaded in an iframe, so a data: URI must declare text/html. data:text/javascript (a VPAID leftover) is rejected.
Why this matters in production
This is usually an interaction blocker. When a SIMID error reaches error level, the creative iframe or handshake typically never completes. Linear SIMID issues affect the handshake between the primary video creative and the interactive layer. When these break, the ad often falls back to plain video or fails interaction entirely.
VAST 4.3 allows data: URIs on resource URLs. SIMID §3.1 still requires an HTML document loaded in an iframe, so a data: URI must declare text/html. data:text/javascript (a VPAID leftover) is rejected.
How to fix
If you inline the creative, use a data:text/html URI. If the payload is JavaScript, wrap it in an HTML document that implements the SIMID postMessage API.
Broader troubleshooting
If this rule is one part of a bigger SIMID delivery issue, start with the SIMID troubleshooting guide for a checklist covering iframe URLs, HTTPS, fallback media, and player support. If the XML is already clean, test the live tag: a JS file, frame headers, or a missing createSession will not show up in the catalog.
Invalid
<InteractiveCreativeFile type="text/html" apiFramework="SIMID">
<![CDATA[data:text/javascript,alert(1)]]>
</InteractiveCreativeFile>Valid
<InteractiveCreativeFile type="text/html" apiFramework="SIMID">
<![CDATA[data:text/html,<html><body></body></html>]]>
</InteractiveCreativeFile>SIMID-1.0-simid-url-data-html and other issues instantly.Open the VAST tag validator →