Using the Advertising module, you can edit the ad request policies for your players. You can also use the Advertising module to edit the ad request policies for your videos. When a player has been enabled for ad requests, if there are any conflicts between video and player level policies, the video level policies will override the ad policies set at the player level.
NOTE: You can also set an ad policy for a player using the Brightcove Player API. This approach enables you to override a player's ad policy set in the Advertising module. For more information about these advanced features, see Dynamically Setting Ad Policies and Developing an Ad Rules SWF.
Before enabling player to make ad calls, make sure you have thought through your ad strategy. Also, make sure you are aligned with an ad network or have an account with an ad server, and have campaigns set up with available inventory. If you want to try testing ads and you don't have an ad delivery system in place yet, you may want to read about configuring ads with no ad server.
To enable ad requests for one or more players:
If you are enabling ads for the first time, selecting Ads On will enable the default ad frequency policy. To use an ad policy other than the default, select Edit to set your specific ad policy.
The status of the player selected appears in the Ad Requests On field of the Details Pane on the right side of the Advertising Module. If ads are enabled for the player, the value is true. If ads are not enabled, the value is false.
If ads are not enabled for a player, then no ad requests will be made from that player, regardless of any video level policies or any previously set player policies.
To edit ad policies for one or more players:
In the Batch Edit Players dialog, you can:
In the Batch Edit Players dialog, click Yes in the Request ads from this player field to enable ad requests for this player, or click No if you do not want to allow ads to be requested from this player. Selecting Yes has the same effect on the player as clicking the Ads On button to enable ads for selected players. (Remember that selecting Ads On for the very first time enables a default ad policy.) If you have already enabled or disabled ad requests using the Ads On and Ads Off buttons in the toolbar, you do not need to set this field.
If you select No, then no ad requests will be made from the player, regardless of the ad policy settings of any videos being played by that player.
The ad source setting determines where your player sends its ad requests. You can set this either at the account level or at the player level. If an ad source is set at the account level, the default ad source will display below the ad source selection menu. By default, Brightcove players are integrated with DoubleClick's DFP ad server. If you are not using DFP, you can contact Brightcove support to set up a different account-level default ad source. You can override the account-level ad source for particular players by selecting the appropriate ad source from the drop-down list in the Advertising module.
When you set the ad source for your players, you can choose among a number of different solutions, including:
When you select Tremor Media Acudeo or a custom ad rules SWF, all the Brightcove Ad Policy Settings on this screen are disabled since you will be configuring your ad policy settings in the Tremor Acudeo console or in your other third-party interface, in the case of a custom ad rules SWF. For information on setting the ad policies using Tremor Media's ad network, see Integrating with Tremor Acudeo.
For information about custom ad translators, see Developing Ad Translators. For information about custom ad rules SWFs, see Developing an Ad Rules SWF.
By default, Brightcove players send ad requests to the ad server set at the account level (if any). You can contact support to set up your account-level Ad Server URL setting, if you have not done so already. Even if you have an account-level Ad Server URL, you can override the default (Ad Server URL) for the selected player(s) using this field. For more information about how to construct a Base Ad Tag URL (Ad Server URL), click here.
You can set the policy for how often ad requests are made and determine whether the policy is time-based (look for an insertion point after every x minutes of video playback) or video-based (look for an insertion point after every x videos are played). In the Ad Policy for Videos in this Player field, select either Time Based or Video Based.
If you want to set the most basic ad policy, select the video-based ad policy and select 1 for each frequency setting. If you set this policy, ad requests will be made for every video and only one ad request will be made at a time. Many of our current publishers find that setting a video-based policy that requests 1 ad every 3 videos is a good setting, however you should experiment to find the ad frequency that works for you and your brand.
The default ad policy associated with a new player depends on the player's template.
All Brightcove player templates (except the Video Player and the Video Display templates) use a time-based ad policy (pre-roll insertion, every two minutes) by default. If you create a custom template that can display a playlist, the default ad policy will also be time-based (pre-roll insertion, every two minutes). If you create a custom template that cannot display a playlist, the default ad policy is video-based (pre-roll insertion, every video).
If you select a time-based ad policy, then the frequency of ad requests is based on how long video playback has progressed in this player and the insertion points that have been set.

In the time-based ad policy section, you can set:
How frequently ads are played depends on the interaction of the ad request interval, the ad request quantity, the ad insertion points, and the length of the videos.
The ad request frequency determines how much time has to pass before an ad insertion point will be considered active. After the ad request frequency time has passed, then the next ad insertion point will cause an ad request. If the ad request quantity is set higher than 1, then future ad insertion points may also cause ad requests. After the correct number of ad requests have been made, then the time counter goes back to 0 and the time starts incrementing again.
The elapsed time between ad requests is based on the time the viewer spends watching videos; skipping ahead in a video does not make ad requests come faster, but rewinding and viewing again does count against the elapsed time. Time spent watching part of one video counts toward the time interval on the next video.
If an ad insertion point is passed and the ad frequency time has not elapsed, then the ad insertion point will be skipped. If ad frequency time has elapsed and the viewer rewinds the video, the earlier insertion points will be considered active.
If you select a video-based ad policy, then the frequency of ad requests is based on how many videos have played back in this player and the insertion points that have been set.

In the video-based ad policy section, you can set:
The first ad will be played after the selected number of videos play. The number is calculated by the number of videos that are started to play and not the number of videos that are completed. The same calculation is used for videos that are played between ad requests. If your player has more than one playlist, then video plays are summed across videos played in different playlists as the viewer skips around.
The number of ads to play at a time is the number of ads to play at the current insertion point. If for example, a pre-roll or post-roll insertion point is set up in the player and the number of ads to play is set to 2, then two ads will be played at the pre-roll and the post-roll insertion points.
You can set the insertion points for when the videos in the player should make an ad request.

The insertion points supported are:
Ad requests can include key/value pairs that aid the ad server in selecting the appropriate ad to serve. You can set player-level key/value pairs, which are used for all ad requests from that player. Click here for a list of key/value pairs that are automatically passed by Brightcove to the ad server in an ad call. In addition, you can add additional key/value pairs.
You can also set ad insertion points key/value pairs to use for ad requests in specific situations:
Ad key/value pairs are cumulative. For example, if you have key/value pairs set at the video level, key/value pairs set at the player level, and pre-roll key/value pairs, all three sets of key/value pairs will be sent in the ad request to the ad server. It is up to the ad server to figure out what to do with all the key/value pairs it receives in the ad request.
Note that to use mid-roll ad requests, you need to set cue points in your videos.
To set ad key/value pairs for one or more players in the Advertising Module:
category=news;news=headlines;promo=sponsorship<Multiple values> as a reminder.Read more about: