Welcome to Video Advertising Documentation
Optimise your ad revenue and make the most of your growing audience with the Pulse Products. The Pulse ad management and programmatic trading tools are designed specifically to help broadcasters and publishers run their video ad businesses. For an overview, see Video Advertising Overview and Pulse Video Advertising Platform.
VideoJS v7.x and Brightcove Player v6.x HTML5 Plugin
A new plugin is available to integrate your VideoJS v7.x and Brightcove Player version 6.x with Pulse for ad serving. The plugin and all its documentation can be found on GitHub: Pulse Plugin for VideoJS and Brightcove Player. Read more in this release note.
Daily and Hourly Impression and Event Caps
- Daily and hourly impression caps: to limit the daily and hourly amount of impressions delivered for certain goals.
- Daily and hourly event (% ad completion and click through) caps: to limit the daily and hourly amount of events delivered for 25%, 50%, 75%, and 100% ad completion, or click through goals.
Currently, in Pulse, you can set the following impression and event caps, and combine them where applicable:
|Cap Type||Impressions (normal and sponsor)||Share of Voice (normal and sponsor)||Unlimited impressions||Priority unreserved||25%, 50%, 75%, or 100% Ad completion||Click throughs|
|Total Impression Cap||X||X||X|
|Daily Impression Cap||X||X||X||X|
|Hourly Impression Cap||X||X||X||X|
|Daily Event Cap||X||X|
|Hourly Event Cap||X||X|
This provides you with more control around delivery pacing and distribution during the entire goal period, and reduces the amount of manual work previously needed to achieve this. Using daily and/or hourly caps means that the goal's daily and/or hourly delivery should not exceed the cap, but there is no guarantee it will reach the cap, especially in case of traffic pattern changes. For more information, refer to Daily and Hourly Goal Caps vs Pulse Dynamic Design.
Support for caps has also been added in the Goal REST API, which means you can handle all available impression and event caps through the https://api.videoplaza.com/api/1.0.cpvext/goal set of endpoints. Read more in these release notes: 2019-02-14 Release and 2019-03-08 Release.
Target Any Position in a Linear Ad Break
Previously, you could already target the first, the last, or, the first or last ad position in an ad break. Now, it is also possible to target absolute positions in an ad break, but only from the second to the ninth position. This allows you to reserve specific positions in an ad break for certain types of campaigns or goals. Read more in this release note .
New Performance Metrics Explorer Functionality in Pulse
- Campaign progress monitoring in near real-time.
- Visualising the near-real time or historical campaign performance in the form of a time series graph, broken down by day.
- Quick and simple retrieval of near real-time or historical performance metrics totals.
- Sharing the active campaign's performance view with relevant advertisers, so they can monitor on their own without having access to any other data in your Pulse account.
Back-to-back Clash Protection
Client Categories are used to create clash protection rules for advertisers and brands. Previously, it was only possible to set up clash protection to prohibit ads from certain advertisers or brands to be shown together in the same ad break or in the same session. Now, it is also possible to allow ads from advertisers and/or brands within the same Client Category to be shown together in the same ad break, but not back-to-back. This means that an unrelated ad, in terms of clash protection, should be located in between the related ads.
The introduction of back-to-back clash protection allows you to fill more inventory, and still fulfil your obligations to your advertisers. Read more in this release note.
Sponsor Ad Position
Previously, sponsor ads were always shown closest to the video content: after pre-rolls, after mid-rolls, and before post-rolls. Now, you have the option to show all ads from a sponsor goal either only before or only after the relevant linear ad break by setting the ad position at creation time. If you want to show sponsor ads before and after a linear ad break, which may be desirable for mid-roll ad breaks, then you must set up two separate sponsor goals: one selecting the before ad position, and one selecting the after ad position. Read more in this release note.
New Campaign Management Query REST API Endpoints
A new series of endpoints, called Campaign Management Query API, have been added to the Campaign Management APIs, to quickly retrieve detailed information and performance metrics from your campaigns, goals, and ads. These endpoints allow you to build your own interfaces to view the information in your account.
Consent Framework Launch in Pulse
The implementation of IAB's Transparency and Consent Framework in Pulse is now finalised, and we honour the viewer's consent settings to serve personalised or non-personalised ads when you send in this information in your ad requests.
- registration as a vendor with IAB, see Global Vendor and CMP list,
- implementation of a site setting to enforce your general GDPR stance site wide, and
- implementation to handle the consent settings for your viewer and serve personalised or non-personalised ads accordingly, also taking the GDPR stance into account.
These new parts, together with the parameters and macros available since the 2018-06-14 Release, allow all parties in the digital ad serving chain involving Pulse to be GDPR compliant.
Full information regarding our vendor registration, parameters, macros and ad selection implications is found here: GDPR, IAB Consent Framework and 'Do Not Track' in Pulse.
Where to Find What
- Pulse User Guide for Pulse administrators, ad operations, traffic managers and sales and product managers:
- Developer Guides for developing and validating integrations between
your player and Pulse for ad serving:
- Mandatory Validation Importance and Process for all integrations.
- Plugins for several video players.
- Pulse SDKs (high level SDKs) for HTML5, Android, iOS and tvOS.
- Pulse Integration Toolkit (low level SDKs) for HTML5, Android (deprecated) and iOS (deprecated).
- VAST and VMAP for VAST and VMAP integrations.
- SDK reference documentation (both Pulse and Core SDKs).
- Developer Guides for accessing and handling data in Pulse:
- Pulse REST API guides and examples.
- Pulse REST API references:
- Knowledge Base Articles
- Pulse FAQ
- Pulse Video Advertising Release Notes for up-to-date information about the Pulse products