VPAID 2.0 Interactive Ads
Understanding How VPAID Works
Compared to standard linear video ads, where the ad experience is defined entirely by a static instream video, VPAID ads are interactive and dynamic. As such, they have a variety of events that need to be communicated back and forth between the player and the advertisement. A basic, simplified example of VPAID chatter would be:
- Player: Hello, VPAID ad! I am ready for you to play!
- VPAID Ad: Okay! I am loading some content. Hold on...
- VPAID Ad: I'm going to play a 30 second ad now!
- Player: Cool! I'm waiting for you to finish playing. Just let me know!
- VPAID Ad: Finished! My ad is done!
- Player: I’m removing you now! I am going to play my content!
Of course, since VPAID ads are dynamic and play their own content, conversation between these player and ad needs to be maintained throughout ad playback. Both the player and advertisement will need to react accordingly as well. For example:
- VPAID Ad: I have paused! Please wait until I give the all-clear.
- Player: My volume has increased! Please set your volume to 80%!
- VPAID Ad: Someone interacted with me! My new duration is 45 seconds!
There is a full list of available VPAID 1 and 2 API calls available on the IAB’s website.
New to VPAID 2.0
Why use iframes at all?
VPAID 2.0 Event Flow
adStarted is a new event that signals that the ad unit was loaded into JW Player but has not yet begun video playback. This is sometimes used as the ad unit is searching for a video creative to fill the slot.
adImpression is only fired when the ad unit signals that the an ad impression has been reached. This is different than previous when the player would trigger an impression based off of the ad loading.
adStopped is not currently implemented but will be fired when a user stops playback of the ad unit.
Google IMA and VPAID Modes
VPAID 2.0 is supported in both our VAST and Google IMA plugins, however Google IMA allows for additional iframe configuration settings. Inside of your advertising block, vpaidmode can be configured as the following:
disabled - VPAID ads will not play and an error will be returned if VPAID is requested.
enabled - VPAID is enabled using a cross domain iframe. The VPAID ad cannot access the site. VPAID ads that depend on friendly iframe access may not play.
Browser support is entirely dependant on the media file used by your VPAID advertisement. A full list of supported creatives and browsers is found on our Ad Reference Page.
Did you find this article helpful?
Please log in to rate this article.