vastlint
SIMID-1.0-simid-url-https

SIMID-1.0-simid-url-https

<InteractiveCreativeFile apiFramework="SIMID"> URL must use HTTPS

ErrorLinearIAB SIMID 1.0 §3.1

Short answer

SIMID creatives are loaded into a sandboxed cross-origin iframe by the video player. An HTTP URL will be blocked by mixed-content policies in all modern browsers and CTV web views. SIMID is built with security as a core tenet (§3 intro: "built with strong security from the ground up") — an HTTP URL will result in a blank interactive layer with no error surfaced to the player.

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.

SIMID creatives are loaded into a sandboxed cross-origin iframe by the video player. An HTTP URL will be blocked by mixed-content policies in all modern browsers and CTV web views. SIMID is built with security as a core tenet (§3 intro: "built with strong security from the ground up") — an HTTP URL will result in a blank interactive layer with no error surfaced to the player.

How to fix

Change the SIMID creative URL to HTTPS. Ensure your ad server and CDN serve the creative over TLS.

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.

Invalid

<InteractiveCreativeFile type="text/html" apiFramework="SIMID">
  <![CDATA[http://example.com/creative.html]]>
</InteractiveCreativeFile>

Valid

<InteractiveCreativeFile type="text/html" apiFramework="SIMID">
  <![CDATA[https://example.com/creative.html]]>
</InteractiveCreativeFile>
Check your VAST tag for SIMID-1.0-simid-url-https and other issues instantly.Validate a tag →