VAST Introduction
VAST (Video Ad Serving Template) is a specification defined and released by the Interactive Advertising Bureau (IAB). VAST sets a standard for communication requirements between Ad Servers and Video Players to present video ads, and it is declared using XML
.
In short, VAST makes it possible for an ad provider to serve ads to various video players using a universal way of communication which all these players understand.
A thorough description of the overall idea behind VAST, as well as the full VAST specification, can be found here: VAST 3.0.
Note: The default standard served through ExoClick is v3
, but VAST Wrappers might use other VAST versions based on advertisers preference.
How VAST Works
A regular VAST communication happens like this:
- VAST Request: The video player makes a call to the ad server for a VAST response.
- VAST Inline Response: The ad server responds with a VAST Inline response that contains all the media files and tracking URIs required to display and track the ad.
- Tracking URIs Pinged: The video player requests tracking resources from the tracking URIs provided when associated events occur in the ad.
Events and Statistics
Currently the system tracks three events when a VAST ad is being processed:
- Video Impression: the exact timing of the event depends on the video player, but most often it is triggered when the site visitor presses the player Play button. .
- Video View: this event happens after watching 10 seconds of video ad playback at normal speed. When this event takes place, the video player notifies the ad provider and a view is registered. This event is important for determining the cost of CPV campaigns.
- Click: this event happens when clicking on the video ad. The video player notifies the ad provider and a standard click event is registered.
Sample VAST structures
ExoClick uses VAST to handle In-Stream, Outstream, Slider and In-Video ads. In this section you will find visual examples of XMLs returned by our ads and detailed explanations of each element within these XMLs:
Note that you will only need to process the VAST events when receiving a VAST tag ad zone, which corresponds to either In-Stream or In-Video. For a simple explanation on how to add an In-Stream or In-Video ad zone to your website, please check our tutorials:
In-Stream:
- In-Stream: How to implement In-Stream Part 1 - Setting up the Ad zone
- In-Stream: How to implement In-Stream Part 2 - Implementation examples
- In-Stream: How to implement In-Stream Part 3 - Testing the ad zone
In-Video:
VAST errors
If your video player is experiencing issues when interpreting the VAST responses, you can check out our list of errors to help you debug your problem.