Video Ads Learning Hub
Master the ecosystem. From VAST basics to programmatic mastery.
Quick explainers
Read one card, try one action, then move on.
Why do VAST trackers matter?
They prove the ad played. If Impression or start 404s, reporting shows zero.
Try it: click a tracker URL in your tag and check it returns 200.
Client vs SSAI?
Client = player fires trackers; SSAI = server stitches and fires. Mismatch? Look at the manifest for ad markers.
Try it: open the HLS manifest and search for EXT-X-CUE.
Common playback miss
Wrong MIME or codec. The player rejects the creative and you see blank. Keep MP4 (h.264 + AAC) as default.
Try it: check the type field in the VAST MediaFile.
Dynamic Ad Insertion Playground
Controls
Upload your own MP4 video file
Ad Configuration
How many ads to play in a row
Play ads every X minutes
Ads will play automatically based on interval
Video Advertising Fundamentals
1. What are Video Ads? (Simple Explanation)
Video ads are ads that play before, during, or after online videos on websites, apps, or CTV.
Think of YouTube:
- Pre-roll plays before the content
- Mid-roll plays in the middle
- Post-roll plays at the end
Video ads need a common "language" so the ad server, video player, and advertiser can communicate properly. That common language is where VAST and VPAID come in.
2. What is VAST? (Video Ad Serving Template)
VAST = A standard XML template that tells the video player how to run a video ad.
Why do we need VAST?
Without VAST, different video players (YouTube, Hotstar, SonyLiv, in-app players) and different ad servers would "speak different languages." VAST creates a universal format.
How it works (simple flow)
- Video player requests a VAST tag
- Ad server returns XML with ad metadata
- Player reads the XML
- Player downloads & plays the video
- Player fires tracking pixels
What does VAST contain?
A VAST tag is an XML URL that includes:
- Video file URL (MP4, WebM, etc.)
- Duration of the ad
- Impression tracking URL
- Click-through URL
- Event trackers (start, first quartile, midpoint, third quartile, complete)
- Companion banners (optional)
Easy Analogy
VAST is like a recipe — it gives instructions to the player on how to cook (play) the ad.
Evolution of VAST
VAST 2.0 (The Old Reliable)
The most widely used version for years. It standardized XML for video ads but lacked support for ad pods and advanced tracking.
VAST 3.0 (The Game Changer)
Introduced Skippable Ads (skipoffset), Ad Pods (sequence of ads), and better error reporting codes.
VAST 4.x (The Modern Era)
Designed for Server-Side Ad Insertion (SSAI). Separated the media file from interactive files, added Mezzanine files (high quality for stitching), and introduced OMID (Open Measurement) for verification.
VAST 2.0 - Real XML Example
Let's look at an actual VAST 2.0 XML file to understand how it works:
Sample VAST 2.0 XML Structure
View Full XML<?xml version="1.0" encoding="UTF-8"?>
<VAST version="2.0">
<Ad id="1">
<InLine>
<AdSystem>Example Ad Server</AdSystem>
<AdTitle>Sample VAST 2.0 Ad</AdTitle>
<!-- Impression Tracking -->
<Impression><![CDATA[https://...tracking/impression.php?ad_id=vast_2_0]]></Impression>
<Creatives>
<Creative>
<Linear>
<Duration>00:00:30</Duration>
<!-- Event Tracking URLs -->
<TrackingEvents>
<Tracking event="start">https://.../start.php</Tracking>
<Tracking event="firstQuartile">https://.../q1.php</Tracking>
<Tracking event="midpoint">https://.../q2.php</Tracking>
<Tracking event="thirdQuartile">https://.../q3.php</Tracking>
<Tracking event="complete">https://.../complete.php</Tracking>
</TrackingEvents>
<!-- Click Tracking -->
<VideoClicks>
<ClickTracking>https://.../click.php</ClickTracking>
<ClickThrough>https://advertiser-website.com</ClickThrough>
</VideoClicks>
<!-- Video Files -->
<MediaFiles>
<MediaFile type="video/mp4" width="1280" height="720">
<![CDATA[https://.../ad-video.mp4]]>
</MediaFile>
</MediaFiles>
</Linear>
</Creative>
</Creatives>
</InLine>
</Ad>
</VAST>
Key Elements Explained
- <Impression>
- Fires when ad starts loading
- <Duration>
- Total length of the ad (HH:MM:SS)
- <MediaFile>
- Actual video file URL (MP4, WebM)
- <ClickThrough>
- Landing page when user clicks ad
Event Tracking Timeline
- 0% ??? start event fires
- 25% ??? firstQuartile
- 50% ??? midpoint
- 75% ??? thirdQuartile
- 100% ??? complete
Each tracking URL is called automatically by the player
Why Event Tracking Matters
Event tracking tells advertisers exactly how their ad performed. For example:
- ??? Impression = Ad was served (billing starts)
- ??? Start = User actually started watching
- ??? Midpoint = User watched at least 50%
- ??? Complete = User watched entire ad (most valuable!)
- ??? Click = User clicked the ad (engagement metric)
Advanced VAST Examples
What is a Wrapper?
A Wrapper is a VAST tag that redirects to another VAST tag. It's used by ad networks to track impressions before passing the call to the next system.
<VAST version="2.0">
<Ad id="wrapper_1">
<Wrapper>
<AdSystem>Example Wrapper</AdSystem>
<!-- Redirects to another VAST URL -->
<VASTAdTagURI><![CDATA[https://.../vast_2_0_sample1.xml]]></VASTAdTagURI>
<Impression>...</Impression>
</Wrapper>
</Ad>
</VAST>
What is an Ad Pod?
Ad Pods allow multiple ads to play in sequence (like a TV commercial break). VAST 3.0 introduced the sequence attribute.
<VAST version="3.0"> <!-- First Ad in Sequence --> <Ad id="pod_1" sequence="1"> <InLine>...</InLine> </Ad> <!-- Second Ad in Sequence --> <Ad id="pod_2" sequence="2"> <InLine>...</InLine> </Ad> </VAST>
What is a Mezzanine File?
Introduced in VAST 4.0, a Mezzanine file is a very high-quality video file used by Server-Side Ad Insertion (SSAI) vendors to transcode the ad into different formats.
<MediaFiles>
<MediaFile delivery="progressive" type="video/mp4" width="1920" height="1080">
<![CDATA[https://.../ad-video.mp4]]>
</MediaFile>
<!-- High Quality Source for Transcoding -->
<Mezzanine delivery="progressive" type="video/mp4" width="3840" height="2160">
<![CDATA[https://.../ad-master-4k.mp4]]>
</Mezzanine>
</MediaFiles>
VPAID in VAST
VPAID creatives are delivered inside a standard VAST tag. The MediaFile points to the JavaScript file instead of a video.
<MediaFiles> <!-- Points to JS file, not Video --> <MediaFile delivery="progressive" type="application/javascript" apiFramework="VPAID"> <![CDATA[https://.../vpaid_creative.js]]> </MediaFile> </MediaFiles>
Error Tracking
The <Error> tag allows the player to report issues. The [ERRORCODE] macro is replaced by the player with a specific code (e.g., 401 for File Not Found).
<InLine> <!-- Error Pixel with Macro --> <Error><![CDATA[https://.../error.php?code=[ERRORCODE]]]></Error> <Creatives>...</Creatives> </InLine>
3. What is VPAID? (Video Player Ad Interface Definition)
Why was VPAID created?
Because VAST is static. Publishers wanted:
- Interactive ads
- Expandable ads
- Hover animations
- Custom buttons
- Advanced tracking
VPAID allowed the advertiser to run rich, interactive experiences inside the video player.
Evolution of VPAID
VPAID 1.0 (The Flash Era)
Built primarily for Adobe Flash (SWF). It allowed ads to communicate with the player but is now completely obsolete since Flash died.
VPAID 2.0 (The Standard)
Introduced JavaScript support (VPAID JS). This became the industry standard for interactive ads, viewability measurement, and verification.
Is there a VPAID 3.0?
No! The industry realized VPAID had too many security and performance issues. Instead of VPAID 3.0, the IAB Tech Lab split the functionality into:
- VAST 4.x (for the video file)
- SIMID (for interactivity)
- OMID (for verification/measurement)
What VPAID enabled:
- ??? User interaction tracking
- ??? Clicks, mouseovers
- ??? Expand/collapse
- ??? Play/pause control
- ??? Timers
- ??? Custom UI elements
How it works
The VPAID tag loads a JavaScript file that controls the ad inside the video player.
4. Why is VPAID dying?
VPAID gave advertisers too much control inside the player's environment, leading to:
The Problems:
- ??? Security risks
- ??? Latency and slower video loads
- ??? Fraud possibilities
- ??? No consistency across players
- ??? Not supported in CTV environments
The Solution (Modern Tech):
So the industry moved away from VPAID. Modern CTV and mobile environments prefer:
- ??? VAST 4.x
- ??? OMID + Open Measurement SDK
- ??? SSAI (Server-side ad insertion)
5. VAST vs VPAID (Quick Comparison)
| Feature | VAST | VPAID |
|---|---|---|
| Type | XML | JavaScript |
| Control | Player-controlled | Ad-controlled |
| Interactivity | Limited | High |
| Security | Safe | Risky |
| Load time | Fast | Slow |
| Support | Web, in-app, CTV | Mostly web |
| Status | Current standard | Deprecated / phasing out |
6. How to Explain All This in One Line (for interviews)
Here's a crisp version:
"Video ads are digital ads delivered inside video content."
"VAST is an XML standard that gives the video player instructions to serve the ad."
"VPAID is a JavaScript-based wrapper for interactive video ads, now replaced by OMID and VAST 4.x due to security and performance issues."
Intermediate: VAST Loader
Test and inspect VAST tags directly in your browser.
Upload any VAST XML file from your computer
Technical Deep Dive
Parsed Data
- MediaFile: The actual video link (like an .mp4).
- Impression: A "receipt" sent to say "Ad started!".
- ClickThrough: Where the user goes if they click.
View Raw XML
Preview
Event Log
Advanced VAST Concepts
Wrappers
A VAST tag that redirects to another VAST tag. Used for tracking and ad network chaining.
Ad Pods
A sequence of ads (like TV commercial breaks) played back-to-back.
Advanced: VPAID Sandbox
Simulate VPAID events and interactions.
Q: What is VPAID really?
Think of VPAID as a mini-website running inside the video player. Unlike VAST (which is just a video file), VPAID is code (JavaScript) that can talk to the player. It can pause the video, show buttons, or even play a game!
Interactive VPAID Playground
Setup
Upload your main video content (MP4)
Ad will appear at this time and auto-close after 15 seconds
Interactive ad will play automatically at scheduled time
Player
Interactive Ad
Loading...
VPAID Controls
Event Log
Enterprise Technologies
SSAI
Server-Side Ad Insertion stitches ads into the video stream, bypassing ad blockers and improving playback stability.
Header Bidding
Allows publishers to offer inventory to multiple ad exchanges simultaneously before making calls to their ad server.
Measurement
Advanced metrics like Viewability (MRC standards) and Attention Time are crucial for premium video campaigns.