VAST Error 200: Trafficking error
The player received an ad type it was not expecting and cannot display — the ad is valid, but wrong for the slot.
Error 200 is the general trafficking mismatch: the ad server returned a creative that doesn't fit what the player asked for. The tag may be perfectly valid VAST — it's just the wrong kind of ad for this placement.
Specific mismatches have their own codes (201 linearity, 202 duration, 203 size); 200 covers everything else, including players that don't bother reporting the specific variant.
Why error 200 happens
Wrong ad format trafficked to the placement
A display or rich-media creative was assigned to a video slot, or a VPAID unit was sent to a placement that only accepts plain video.
Placement targeting misconfigured on the ad server
Line items targeted at the wrong inventory type end up serving formats the placement never supports.
Player capability flags out of sync
The ad request advertises capabilities (e.g. VPAID support) the player doesn't actually have, so the ad server responds with an unplayable format.
How to fix VAST error 200
- 1
Compare the ad response to the placement spec
Validate the tag and look at what the creative actually is — linear video, VPAID, interactive — then check the placement's accepted formats.
- 2
Audit line item targeting
Confirm the campaign's line items target the intended inventory type and that no catch-all targeting sweeps video slots into display campaigns.
- 3
Align ad request parameters with real player capabilities
Make sure the request only advertises formats the player supports, so upstream decisioning can filter correctly.
Seeing error 200 on a live tag?
Paste the tag URL or XML — the validator resolves the full wrapper chain, validates the schema, downloads every media file, and shows exactly which stage fails.
Validate your VAST tagVAST error 200 — frequently asked questions
Is error 200 a broken creative?+
Usually not. The creative is typically fine — it was just served to a placement that can't display that format. Fix the trafficking, not the file.
Why do I see 200 instead of the specific 201–203 codes?+
Many players only implement the general code. Treat 200 as "some expectation mismatch" and diagnose by comparing the response against the placement spec.