DoubleClick's DFP Specific Information
This section describes all of the unique information required to integrate Brightcove with DoubleClick's DFP (DART for Publishers). This section describes both the DFP product and the extension to the DFP product for video and rich media called DFP Video and Rich Media. Most of the information is common to both DFP and DFP Video and Rich Media. Any differences will be highlighted.
DFP-specific tasks performed before you begin integration
Perform the following tasks before you begin integration:
Establish a unique DFP ad size to distinguish all Brightcove Media
Brightcove does not have a specific ad size as there are many combinations for ad assets that can be scheduled to a Brightcove player at once. However, for trafficking and reporting purposes it is recommended that you select a size that would represent all Brightcove ad formats within your DFP network.
Brightcove suggests you use 8x8 as an arbitrary size as it is not commonly used by publishers for any other media. (Note: 8x8 is a suggestion, but another arbitrary size can be used.)
Specify the unique size by adding the Size key/value pair to all ad-enabled players, in the player level key/value field in the Brightcove Advertising Module as follows:
;sz=8x8
For more information on adding the key/value pairs, see Setting ad key/values.
Host ads on DFP or set up alternate ad hosting
Brightcove does not support the hosting of advertising assets, including video ads. DoubleClick offers video ad hosting through their ad server. If you want to use DoubleClick's video ad hosting, contact DoubleClick Customer Support. If you will host the video ad assets internally, you will need to determine a process for uploading your video ads (using FTP or some other method) and you will need to enter the full file path name for the video ads into DFP.
Determine how ads will be encoded
DoubleClick does not offer encoding services for your video ads. You will need to encode them internally using a video encoding program or obtain a publisher FLV video file from your advertisers.
Upload Brightcove XML templates into DFP
Before you begin trafficking ads for the first time using DFP, you must upload the Brightcove's XML templates for each ad format you will be using in DFP.
For DFP Video and Rich Media Only: Enable DFP Video and Rich Media
DFP Video and Rich Media is an add-on product to DFP and is not automatically enabled for your DFP network. Contact your DoubleClick Account Manager or DoubleClick Customer Support for information on enabling this add-on product.
For DFP Video and Rich Media Only: Determine how Rich Media ads will be compiled
All banner ads supported in the Brightcove player will be published as DFP Rich Media ads (.mft files) using DoubleClick's Flash ad kit. The ad kit is available as a Flash program add-in on DoubleClick's website and DoubleClick Creative Services can distribute the template suite. DoubleClick's Creative Services group also offers a service to create the Rich Media ads (.mft files) for you. For more information, contact your DoubleClick Account Manager.
DFP-specific integration tasks
Set the Ad Translator
DFP is Brightcove's default Ad Translator. No action is required to use the DFP Ad Translator.
For DFP Video and Rich Media Only: To use the DFP Video and Rich Media Ad Translator, either request that Brightcove Customer Support enable the DFP Video and Rich Media Ad Translator at the account level, or set the Ad Translator to DFP Video and Rich Media at the player level. For information on setting the Ad Translator at the player level, see Setting the default Ad Translator.
Set the Ad Server URL
Examples of the Ad Server URL for DFP are as follows:
- http://ad.doubleclick.net/pfadx/sitename/zone (includes site & zone)
- http://ad.doubleclick.net/pfadx/sitename/ (no zone)
- http://ad.de.doubleclick.net/pfadx/sitename/zone (contains international server)
Determine if the Ad Server URL will be assigned at the account level, the player level using the Brightcove Advertising module, or the player level using the JavaScript/ActionScript publishing parameter. For more information, see Setting the Ad Server URL.
DFP-specific tasks related to setting ad policies
Perform the following tasks while setting ad policies:
Set the appropriate DFP-specific key/value pairs
There are two DFP-specific key/value pairs:
- ord (Cache Busting Time stamp) - This key/value pair is automatically passed to the DFP Ad Server. It provides the cache busting time stamp.
- sz (Size) - As described in Before you begin integration above, Brightcove recommends that you select a unique size that would identify all Brightcove ad formats within your DFP network. For more information on setting key/value pairs, see Setting key/value pairs.
Playlist Targeting Examples for DFP
The following provides some examples of how you might use the playlistTargeting configuration parameter with DoubleClick DART for Publishers, together with examples of the resulting ad requests. For more information on playlist targeting, see Player Configuration Parameters for Ads. These examples are for ActionScript; in JavaScript/HTML code, use this syntax:
<param name="playlistTargeting" value="playListName" />
Example ad request:
http://ad.doubleclick.net/adi/N3271.example.com/;dcadv=1386940;sz=160x600;ord=3206438966013914?
Example ad request, where Sharks is the playlist name:
http://ad.doubleclick.net/adi/N3271.example.com/Sharks;dcadv=1386940;sz=160x600;ord=3206438966013914?
Example ad request, where 16863662 is the playlist ID:
http://ad.doubleclick.net/adi/N3271.example.com/16863662;dcadv=1386940;sz=160x600;ord=3206438966013914?
Example ad request, where playlist0012 is the playlist ref ID:
http://ad.doubleclick.net/adi/N3271.example.com/playlist0012;dcadv=1386940; sz=160x600;ord=3206438966013914?