This document assumes you have access to Brightcove and is only a basic view of setting up Brightcove to make ad calls to SAS Intelligent Advertising for Publishers. It also assumes you have knowledge of setting up creative formats and creatives in SAS Intelligent Advertising for Publishers.
To serve VAST ads into Brightcove players there are a couple of things that need to be set up at the video player level first.
1. You must allow your player to request ads.
2. Your ad source needs to be pointed to the sasiaAdTranslator.swf.
3. Your ad server base url needs to be set.
Load up the advertising module in Brightcove and edit the player you want to set up.
1. Select yes to "Request ads from this player"
2. Select yes to "Overide default base ad tag url" under Ad server URLs and enter the base URL to your instance, for example: http://crtl.aimatch.com/{customername}/tserver.
3. Select "Customer Ad Translator SWF URL" under ad source and enter: http://content.aimatch.com/sasiaAdTranslator.swf
This will set up the base ad call for all of your videos using the player that you set up.
Key=value pairs
It's up to you to set up the key=value pairs on the video player level, individual movie level, or both. Key=value pairs are separated by ";" in the Brightcove console. These will be converted to "/" when read by aiMatchAdTranslator.swf. If your ad call from the player should always include a specific key=value pair you will need to set this at the player level which means that these will always be appended to the base ad call.
Select Edit under "Request ads from this player" and input the key=value pairs separated by ";" --- for example, "site=test;size=video". Below you can see where you would set up player load, pre-roll, mid-roll and post-roll ad insertions. These coincide with the cue points set within the individual videos.
You can also set up key=value pairs at the individual video level, which is basically the same as shown above.
Vast Wrapper for serving 3rd party VAST ads
Using a vast wrapper to serve 3rd party VAST ads from SASIA/aiMatch is pretty simple. You can use the below as your creative format. You would simply put the VAST ad url from the SASIA/third party in the custom field that coincides with %%X_AD_URL%%.
Download the VAST wrapper XML file here.
Serving inline VAST ads directly
For serving inline VAST ads directly from SAS Intelligent Advertising for Publishers you can using the following basic VAST creative format. This is only a basic template. There many other elements that can be added.
Download the VAST standard XML file here.
As for now to have multiple media files you need to create custom fields to make this work. %%X_VIDEO_TYPE%% is the mime type for the type of video you are serving.
Please note that this information is a work in progress and will be updated accordingly.
For more information on Brightcove and VAST please visit their documentation at
Brightcove VAST Overview.
Enabling support for companion flights and categories
Flights with companion type enabled and flights that have categories applied require that the viewids for all ad calls on a given page match on each refresh. Built into the Ad Translator SWF is support for a Javascript function called "getPageNum". This is a simple block of code that returns the viewid being used by the ad calls on the page:
function getPageNum() {
return pageNum;
}
|
Note that if the ad calls use a variable name other than "pageNum" for the viewid in the ad calls, this needs to be reflected in the above code, changing "return pageNum" to "return {variable_name}".
This code needs to be placed on every page where the Brightcove player resides.
Operating System and Release Information
SAS System | SAS Intelligent Advertising for Publishers | N/A | | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.