Before we start diving deep into the specification of VAST tags, let’s take a step back to understand how we can actually display video ads on a website. The first thing that comes to mind is probably an advertiser who uploads their video ad file somewhere on the server. Then they go to the website owner to negotiate the insertion of a video ad into the content (with a link in it).
These steps are correct but how does the advertiser find out how many people watched the video ad? How to find out if people watch it to the end or don’t watch it at all? Many questions arise after video ad placement.
The answer to all these questions can be provided by VAST – Video Ad Serving Template. What is a VAST tag? Ad serving template VAST is a specification (XML schema) developed by the Interactive Advertising Bureau (IAB) that contains all information about ad media files: physical location, format (also VAST URL that will be called upon particular events, etc). So, what is the VAST tag, how to create VAST tags, and what are their specifics and role?
In the early days of digital video advertising, there were too many video ad players and video player developers. Some of these players were functioning based on Flash, the others on HTML5, also some of them required native applications, and the others certain plugins. Since then many websites removed flash videos and technologies changed.
Back in 2008, however, the players didn’t speak the same language and required a unified standard to display video ads.
There was a lot of work on the ad server side. Additionally, there was no guarantee that the custom-coded video ads would correctly communicate with video players. The video ad code needed to be standardized so that video players would know which ads to play, and when. Later the industry developed VAST tags and VPAID standards to streamline ad creative rendering and serving across players and devices.
It is hard to underestimate the impact of video advertising – since lockdown, it only grows in popularity because people spend more time indoors. Plus, video content streaming becomes convenient on any type of gadget, no matter mobile, desktop, or SmartTV.
There’s nothing like the video advertising ad unit that сan tell a meaningful brand story or showcase the product in slight detail. The video media file can be also engaging.
In fact, 73% of people reported that they wanted to buy the product after watching the video ad. Marketers and advertisers, in their turn, also claim to receive higher ROI out of video ad serving.
In the future, ad spending in video advertising is poised to reach $35 billion by 2024, whereas now it already accounts for $26 billion. So far VAST tags along with VPAID are the only standards that ensure smooth and good quality ads delivery in video content.
Plus, XML data contained in the VAST provides additional information which is very convenient for the advertisers when they measure the ad performance. This way, regardless of the publisher’s ad network or server, advertisers can run and measure their ads while ensuring that the publisher’s video player understands VAST.
Ads can be served onto multiple ad inventories within many kinds of video ad players. This way video ads appear in the proper format across different websites and ad networks. But is VAST only created for video format? A VAST tag can be applicable for serving both video and audio ads. Thus, it is suitable for multiple ads.
Most frequently VAST is used for displaying video ads (pre, mid, post rolls) because video ads naturally fit into the video content on the website.
However, there are different kinds of ads that could be used with VAST.
As we already discovered, VAST stands for video ad serving template. It was developed by the Interactive Advertising Bureau as a framework that embeds third party video ads into a video stream. It is a Video Ad Serving Template for structuring ad tags that serve ads to video players. VAST was designed to facilitate and standardize communication between video players and ad servers.
The VAST tag is a script that uses the XML schema to transfer the metadata from the ad server to a video player on the publisher’s side.
After VAST transfers metadata from the master video ad slot on the ad server, the VAST tag can program the video player so that it can show the ad creative on different sites and devices (mobile devices, desktops, and tablets) in a way that guarantees seamless rendering.
Thus, ad serving template VAST is the main link between advertisers and site owners. It represents a language thanks to which the ad tag can communicate with the ad server. Thanks to this advertisers serve ads effectively and publishers effectively monetize inventory.
It’s time to find out how VAST works on web pages. The process of ad insertion takes place in three stages:
1. VAST request. At this stage, the ad server receives a call to fetch the ad (that comes from the player on the website).
2. VAST response. The ad server sends the VAST inline response to the ad player. Such an inline response contains the media file as well as the necessary VAST URL (helps the advertiser to track the impressions).
3. URL tracking. The video player initiates the URL tracking, which allows the advertiser to track impressions and assess the video ad performance.
It is worth mentioning that VAST advertising protocol also facilitates the creation of tracking pixels, which, in their turn are used for registering additional impression parameters like frequency, click rate, etc. Plus, tracking ad performance on a deeper level becomes possible thanks to advanced tag options. An additional tag parameter can specify the ad type, length, duration of watching, and so on.
Just as VAST, VPAID is a video ad serving standard developed by IAB. It facilitates the interaction between ads and the video players, thereby providing favorable conditions for serving interactive ads. It also allows advertisers to record data about how users interact with digital video ads.
In simple terms, VPAID is a set of definitions applied to VAST that help creatives themselves (not ad server) interact with the video player.
It works as so-called “interface addition” – a part of the ad unit, it delivers interactive elements (ad playback, skip, scroll, close, etc.), and also collects data about these interactions for advertisers.
VPAID uses the .SWF format to read elements such as images, GIFs, and other interactive elements (that only VPAID can read). However, for instance, sometimes it happens that the user’s video player can’t read the .SWF. In such a case, VPAID script is automatically overridden by the VAST script to ensure that the video ad appears on all compatible players.
That’s why answering the question of which is better – VAST tags or VPAID – can be tricky. Sure, whereas one advertiser may strive to serve an interactive video format with VPAID, focusing on interactivity doesn’t always get possible because of the limitation of the players.
Playback errors and the risk to slow down the web page loading on mobile are other reasons why VAST often gets prioritized over VPAID.
The benefit of executing video ads with VAST is in universality. Prior to the adoption of the latest version VAST 4.2, VAST had many limitations, for instance, the inability to support API integration for real-time impression evaluation.
Moreover, there were inconsistencies in adherence to industry viewability standards prior to VAST 4.0 / 4.1 versions. On top of that, the media players were often unable to display the linear ad (General Linear error, request timeout for a VAST URI, etc).
VAST 4.0 the majority of the problems were resolved and the benefits of vast tags are now pretty diverse. The 4.0 and later versions brought in such capacities as the ability to transfer the large arrays of media files – plus, now VAST transfers important metadata associated with ad (while providing good quality rendering on any device).
Stream stitching or ad insertion in digital videos are also happening on ad server side. It also delivers universal ad IDs attributed to every ad (for ensuring brand safety and targeting). VAST tags now also support more interactive formats, advanced reporting, and the opportunity to validate VAST tags.
When it comes to tag type – there are several of them: ones based on VAST XML and URL VAST. However, if you choose between tag options, know that VAST XML is the most preferred format when both XML and URL are supported by your DSP. So, let’s review how to create VAST tags in case you don’t use Google ad manager.
You can use VAST tag generators to generate VAST tags. VAST tag generators are usually offered by video players as an additional feature.
However, you need to make sure that video player that offers the VAST tag generator supports your specifications (to avoid potential errors in the ad display).
If you don’t use the Google ad manager and third party tools then you will be inserting VAST tag manually with pre defined parameters. For this, you will have to create a VAST script by editing the predefined parameters and combining them together to create a complete XML file. Pre defined parameters can make it way easier to create vast tags compared to coding a new file completely from scratch. A complete example of it you can see below.
It is not recommended to create a VAST tag manually, because tools greatly simplify and optimize the process excluding the chance for potential errors.
The above example showcases how the output looks like. After tag creation make sure you validate the output using the validation tool.
When generating a new connection on the SmartHub platform, you can easily select connection type VAST and generate your VAST tag with the supported macros.
Previously it was necessary to select third-party video ad servers that could support VAST tags insertion. These days advertisers often choose programmatic platforms where they can input the VAST tags and obtain detailed reporting and auditing of their ads as well as split testing tools.
As video ads gain traction, SmartHub owners also need to incorporate video advertising into the media-trading environment. Just choose connection type VAST and generate your VAST tag with the supported macros. Note, that SmartHub also supports VAST to RTB, VAST to VAST and VAST to ALL media trading which helps partners trade with each other no matter the connection type. This way your partners will be able to serve and monetize video content with no limitations or restrictions, which in turn will translate into greater opportunities and profits for you.
Sign up to our newsletters and we'll keep you in the loop with everything good going on in the world.
Want to Learn More?
We'll get back to you very soon.
You May Also Like