AdTechToolkit

Local fixtures

VAST 2.0

VAST 3.0

VAST 4.0

VAST 4.1

VAST 4.2

VAST 4.3

VMAP

Errors & Invalid

VAST Inspector

URL or XML
Fetch
HTML5IMA
Req
Load
Start
Q1
Mid
Q3
Done
IMA SDK events
0
No IMA SDK events yet
Test Beacon HTTP
tested
0
ok
0
fail
0
Readiness
Required—
Advisory—
CTV—
Tag
Version-
Type-
Duration-
Redirects-
Categories-
Conditional-
Compatibility
2
3
4.0
4.1
4.2
4.3
Latency
Hops
-
Total
-
Slowest
-
Platform
WebNot checked yet
MobileNot checked yet
DesktopNot checked yet
CTV / SSAINot checked yet
Creative
—Video
—Audio
—VPAID
—SIMID
—Custom
IDs—Reg —

Companion

Measurement
Impression
Error
ClickThrough
ClickTracking
Start
Q1
Mid
Q3
Complete
Companion
Verification
Viewable
Mobile optimizations
-
Desktop optimizations
-
CTV optimizations
-

Video diagnostics

VAST debugging guide

Inspect VAST and VMAP tags without slowing down QA

Use VAST Inspector when you need a fast, practical read on whether a video ad tag is structurally valid, playable, measurable, and likely to behave across web, mobile, CTV, and SSAI workflows.

What it checks

Paste a VAST URL, VAST XML, or VMAP schedule to review XML shape, wrapper hops, schema compatibility, media files, tracking events, click-throughs, VPAID, SIMID, and CTV-related signals.

When it helps

The tool is useful before launch, during tag QA, after a player error, or when a campaign has missing impressions, broken tracking, empty media, wrapper depth problems, or inconsistent playback behavior.

How to read results

Start with validation and triage, then review wrapper resolution, media file availability, tracking events, and player activity. The goal is to separate spec issues from player, network, and creative issues.

FAQ

Can I validate VAST 2.0, 3.0, and 4.x tags?

Yes. The inspector supports the major VAST versions used in production workflows and reports compatibility, schema, and rule-based diagnostics where applicable.

Does VAST Inspector play the ad?

It can load the tag into a browser-based player workflow so you can compare parsed tag data with SDK and playback activity.

Should I use pasted XML or a live URL?

Use pasted XML for isolated structure checks. Use a live URL when you need to test fetch behavior, wrappers, media URLs, redirects, or tracking URLs.

Is this a replacement for final device QA?

No. It is a debugging and validation tool. Final certification should still include the player, device, ad server, and SSAI environment used in production.