How do I validate an Innovid VAST tag?

Fetch the live Innovid tag in the VAST tester or inspector, then paste the resolved XML into the validator. Innovid is a third-party ad server, so the request URL and the final inline response can disagree until the chain is resolved.

Does Innovid support VAST and VPAID?

Innovid's own ad-tech brief says Innovid supports both VAST and VPAID. The same brief describes VAST as the tag that works on desktop, laptop, mobile, and CTV, and VPAID as limited to players that can run it.

Which VAST versions does Innovid support?

Innovid does not publish a public VAST version matrix or wrapper-depth cap in the sources used for this guide. Validate the resolved response instead of assuming a version.

Innovid VAST validator guide

Short answer: Innovid is a third-party ad server. Its published brief says it supports both VAST and VPAID, and that VAST is the tag which carries video files and tracking to desktop, mobile, and CTV. Innovid does not publish a public version matrix or wrapper-depth cap, so validate the live tag and the resolved XML before the creative ships.

Need an Innovid VAST validator?

Start with the live tag URL. Resolve the chain, then validate the XML that the player would actually execute.

Test a live Innovid tag →Validate resolved XML →Inspect wrapper hops →

Quick reference

Role	Third-party ad server, with CTV called out in Innovid's platform description
Published tag types	VAST and VPAID
Where VAST is described	Desktop, laptop, mobile, and CTV
Where VPAID is described	Players that accept VPAID
Public version matrix	Not published in the sources for this guide

What Innovid publishes about VAST and VPAID

Innovid's ad-tech brief treats VAST as the common video tag: one response that carries the media files and the tracking pixels, and that can be rendered on desktop, laptop, mobile, and connected TV. The same brief treats VPAID as the interactive layer, and it says those tags only play on video players that support VPAID.

Innovid also says it supports both tag types, and that a certification team checks which publishers will accept them. That split is the practical check. A VPAID creative that is fine on a certified desktop publisher can still fail on CTV inventory that never executes VPAID. For a new CTV campaign, prefer a VAST response with a playable media file, and read the VPAID migration guide if the tag still depends on an interactive API framework.

Validate the live tag, then the resolved XML

Innovid sits in the chain as the advertiser-side ad server. The URL a trafficker pastes is often a wrapper or a dynamic endpoint, and the inline creative shows up only after that request resolves. Macros left in the request, a hop that returns an empty ad, or a media file the downstream player cannot fetch will not show up in a static copy of an old inline.

Open the live Innovid URL in the VAST tag tester or the inspector.
Read each hop. Confirm the chain ends in an inline creative with a usable media file.
Paste that final XML into the validator.
If the tag still carries VPAID, confirm the target publisher is one Innovid has certified for that tag type.

Pre-flight checklist

The live Innovid URL resolves to inline XML.
The resolved response passes the validator.
Media and tracking URLs are present and use HTTPS.
CTV and OTT placements are VAST with a playable media file.
VPAID remains only on publishers certified to run it.

What this guide does not assume

The sources used here do not publish an Innovid VAST version list, a wrapper-depth cap, a required codec, or a bitrate ladder. Those limits, when they exist, come from the publisher player or from the account's trafficking setup. Confirm them there, and use vastlint on the resolved response in the meantime.