vastlint

SIMID validation: how to check InteractiveCreativeFile correctly

Short answer

SIMID validation is not just "does the tag contain an <InteractiveCreativeFile>?" You need the right type, the right apiFramework, an HTTPS URL, and a normal <MediaFile> fallback alongside the interactive layer.

Why this happens

Most SIMID failures are migration mistakes from VPAID: teams copy the old application/javascript MIME type, forget the HTML wrapper, leave the URL empty, or remove the standard video media file because they assume the interactive layer controls playback. That is not how SIMID works.

The player still owns media playback. SIMID adds a secure interactive layer around a normal VAST media setup, not a replacement for it.

Copyable fix example

<MediaFiles>
  <MediaFile delivery="progressive" type="video/mp4" width="1280" height="720">
    <![CDATA[https://cdn.example.com/ad.mp4]]>
  </MediaFile>
  <InteractiveCreativeFile type="text/html" apiFramework="SIMID">
    <![CDATA[https://cdn.example.com/simid-creative.html]]>
  </InteractiveCreativeFile>
</MediaFiles>

VAST XML fragment only. This excerpt belongs inside a complete VAST document, so standalone validation will fail until it is wrapped in a full <VAST>response.

Exact rule pages

Use the right tool for this failure

If you already have the resolved XML, run a pure spec check. If you only have a live tag URL, test that endpoint first. If the failure happens in the wrapper chain, inspect each hop.

Validate this XML →Test this live URL →Inspect this wrapper chain →

Further reading