VAST-4.0-mediafile-apiframework
<MediaFile apiFramework> is deprecated in VAST 4.0+ — use <InteractiveCreativeFile>
Short answer
In VAST 4.0+, interactive creatives should use <InteractiveCreativeFile> instead of setting apiFramework on a <MediaFile>. The latter approach is deprecated and may not be recognised by 4.0+ players.
Why this matters in production
This rule is advisory rather than fatal, but it still matters for portability, debugging speed, and keeping tags predictable across different buyers and playback stacks. Deprecated features are a long-tail compatibility problem: they may appear to work in one legacy stack and fail silently in newer players, SSAI chains, or device ecosystems. Affected scope: VAST 4.0, 4.1, 4.2, and 4.3.
How to fix
Move the interactive creative to <InteractiveCreativeFile apiFramework="SIMID"> inside <MediaFiles> and remove the apiFramework attribute from <MediaFile>.
VAST-4.0-mediafile-apiframework and other issues instantly.Validate a tag →