Sequence of video ad


Here is a sample sequence, using preroll as an example.
get VMAP, Video Multiple Ad Playlist, form DFP, e.g. vmap.xml, which has preroll midroll ad.
vmap.xml look like this, with URLs for preroll:
<vmap:VMAP
<vmap:AdBreak
<vmap:AdTagURI
https://pubads.g.doubleclick.net/gampad/ads?url=https://developers.google.com/&#8230;

The AdTagURI above returns a preroll ad, which is a VAST, e.g. vast.xml, and looks like the following:
<!–?xml

<?xml
<VAST
<Ad id=”7096…..”>
<InLine>
<Impression> https://securepubads.g.doubleclick.net/pcs/view?xai=AKA
<Creatives>
<Creative id=”578610…..
<Linear>
<Duration>00:00:10
<TrackingEvents>
<Tracking event=”start”> https://pubads.g.doubleclick.net/pagead/ai=BZK9Sr&#8230;
<VideoClicks>
<ClickThrough id=”GDFP”> https://pubads.g.doubleclick.net/pcs/click?xai=AK&#8230;
<MediaFiles>
<MediaFile id=”GDFP” https://redirector.gvt1.com/video../id/5bad…/file.mp4

Some of the key fields are:
Impression: call this URL to tell that this ad has been viewed.
Tracking: call this URL to tell that the video ad has started playing
ClickThrough: the URL to go to when the ad is clicked.
MediaFiles: the .mp4 if the video ad

For JW Player, vast.xml is passed into Setup() as:
advertising.schedule.adbreak1.tag, with adbreak1.offset=pre

Advertisements

VAST video ad from scratch


JW Player plays video ads with absence of ads server.
http://riowing.net/ads/AdsNoSvr.htm

Key components:
Ad Tag .xml file in the html page
ClickThrough and MediaFile in the xml, for ad destination URL and ad video file

VAST vs VPAID


(To be finished)
VAST: simple, support server stitching.
Here is my googima sample video page from last year.
http://riowing.net/ads/AdsVideo.htm
(sometimes a F5 refersh is needed for ads to play)

VPAID: better interactivity, e.g. in a car ad, the car 3D model can be rotated by mouse.
better metrics: VAST can only report limited info back like ad start, skip.

Ads in Video


Video contains ads, which are interactive, skippable, and hooked to DoubleClick for payment process.

Tools needed:

  1. Player: enterprise version of JW Player, which in turn calls Google IMA SDK.
  2. An account from Google DFP, which examine our domain name and web site content for eligibility.

Acronyms:

  1. VAST: Video Ad Serving Template
  2. Google IMA SDK: Google Interactive Media Ads SDK, an implementation of VAST specification.
  3. Google DFP: Google DoubleClick For Publishers: http://www.doubleclickbygoogle.com

The URL from DFP becomes the value of “advertising” property of JW Player, parallel to the “file” property for video. This URL returns a VAST document in XML format with info such as MediaFiles and VideoClicks. Here is quick demo, which play ads before my gym video.

http://riowing.net/ads/AdsVideo.htm  (sometimes a F5 refersh is needed)