VAST and VMAP
Request VAST or VMAP tickets directly to integrate ad serving from Ooyala Pulse into your video player application.
What is VAST?
VAST (Video Ad Serving Template) is the industry standard for communicating video ads from ad server to ad server and from ad server to video player. VAST is developed and maintained by the IAB (Interactive Advertising Bureau) which is comprised of more than 500 ad serving companies, including Ooyala.
VAST is an XML based format that describes one or more ads, their media files, links to track on certain events, which page to open when someone clicks on the ad, and more.
What is VMAP?
VMAP (Video Multiple Ad Playlist) is an XML based format that describes ad inventory insertion policy, meaning it describes to the video player when ad breaks should start, the types of ads to display and whether or not to display multiple ads in the break.
You could see VMAP as a wrapper of multiple VAST 3.0 tickets, supplying the video player with all metadata about the ad breaks to play the ads at the right time and in the right context.
Why a VAST or VMAP integration?
In case your selected video player does not allow you to control video playback, then a way to insert ads in your video content is to rely on the video player to handle VMAP and VAST tickets. You may also opt for a VAST or VMAP integration in case you are integrating ad serving into non-video player applications, like an audio streaming application, a game, and so on.
It is possible to integrate using VAST or VMAP requests even when you have full control over the video player, but it is recommended to use one of the other integration options mentioned on the Ooyala Pulse Integration Toolkit page. This avoids having to have a VAST and/or VMAP XML parser.
Difference between VAST and VMAP integration
- You need to request ads for each ad break you want to insert, instead of requesting a session which would include all ad breaks at once.
- You need to connect the ad requests with an ID so that the ad server can see them as one call.
When creating a VMAP integration, you only make one request just before content start, because the VMAP response contains all ad breaks. You also have no need for a unique identifier for the current content, so clash protection is automatically guaranteed within the session.