As explained in In-Stream: How to implement In-Stream Part 1 - Setting up the Ad zone the Wrapper element is the code below in between . It will point to a secondary ad server where the ad and the other VAST elements are placed.
This basically means that the VAST file will look like this:
VAST Wrapper Coding Example:
<AdSystem>Sample Ad Wrapper</AdSystem>
<Creative sequence="1" id="1">
<Tracking event="progress" offset="00:00:10.000"><![CDATA[http://main.exoclick.com/view.php?tracking_event=progress&progress=00:00:10.000&idzone=0000000]]>
You must ensure that the player you are using to display ads is Wrapper compatible, meaning that it can get and read the content within the wrapper tag.
The players listed in In-Stream: How to implement In-Stream Part 2 - Implementation examples are 100% VAST compatible with our ads, which means that they will also work for Wrapper VAST tags.
The players are:
However, here is an explanation of how to integrate VAST in FlowPlayer
The code shared is just to guide you and is not guaranteed that it will work as it is. Please check also the links provided in order to check the status of the player and how to integrate VAST ad tags properly in each case.
Steps to follow VAST Wrapper incompatibilities:
- Check the Player with a test wrapper zone:
- Check the player with the third party VAST tag https://syndication.realserv.com/splash.php?idzone=3165233 (refer to In-Stream: How to implement In-Stream Part 3 - Testing the ad zone)
- If it is not compatible:
- Update or change your Player.
- Review the compatible Players listed in In-Stream: How to implement In-Stream Part 2 - Implementation examples
If you are unable to update or to change the Player:
Disable VAST Tag campaigns on zone level (enabled by default).
The main reason for doing this is if you are using an incompatible Player your ads will be displayed, but no impressions or views will be counted. This would be misleading for our advertisers and they might stop targeting your ad zone causing a negative impact on your revenues.