Welcome to Video Advertising Documentation
Optimise your ad revenue and make the most of your growing audience with Ooyala Video Adverstising Products. Ooyala’s 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.
Revised Ooyala Pulse REST API Developer Guide
In the new REST API developer guide, we have restructured the information in a more meaningful and logical flow to reflect a typical workflow used in the Pulse user interface:
- Account Management: set up your Pulse account, which is a must before creating ad campaigns.
- Campaign Management: after the account is set up, your ad operators are able to create and manage ad campaigns.
- Forecasting: after a two week period of running your campaigns, your sales have data to forecast on your campaigns and inventory, so they are able to compose better sales packages for your advertisers.
- Analytics: after running ad campaigns, your accounting team is able to extract reports for reconciliation and your analysts are able to report on trends in your inventory and success rates of your sales packages.
New Insertion Policies UI and API
Insertion Policies in Pulse define the foundation for your ad serving settings, by setting the allowed ad formats, number of linear ads, behaviour of non-linear ads, and so on.
Previously, the insertion policies had to be defined for each combination of category, device container and content play length. In this scenario, you could have many duplicate insertion policies and maintenance of the insertion policies was tedious.
- Tags: for example, a user group like loyal users. This means the insertion policy can be used on any content, because tags are not necessarily tied to your category tree. The tags specified in the insertion policy need to match at least one tag coming in the ad request to Pulse.
- Categories: for example, Sport. This means you can control the ad serving down to content level, but through a new user interface and API, providing a simple way to overview, manage, and reuse your insertion policies. One of the categories specified in the insertion policy needs to match the share coming in the ad request to Pulse.
- Tags and categories: for example, loyal users watching sport. This
means you can minutely control the ad serving based on precise combinations
of tags and content categories. The tags and categories specified in the
insertion policy need to match at least one tag and the share coming in the
ad request to Pulse.
Pulse looks at the parent categories as well, so that all sub-categories of the categories specified in the insertion policy are considered matched.
By using the new insertion policies functionality, you reduce the amount of insertion policies you need to configure across your category tree. You can rank the insertion policies, so when more than one insertion policy matches the tag targeting, category targeting, or both tag and category targeting coming in the ad request, then the insertion policy with the highest rank gets selected and overrides the default ad insertion policy which targets the underlying category. If no insertion policy matches the parameters coming in the ad request, the old category based ad insertion policy acts as the default.
You can also manipulate your insertion policies through the Insertion Policy API.
A new reporting tool, called Custom Reporting, is now available in Pulse. This reporting functionality utilises a new framework to allow for much more complex reporting than Insight. Instead of pre aggregating data, reports are scheduled and created on the fly. The result is a big increase in flexibility and range of data with the tradeoff of time to produce the report.
- Advanced invoicing and reconciliation reporting.
- Monthly financial revenue reports.
- Reports that are too complex to be created within Insight.
- Historical reporting, not already defined in Insight.
- Reports with dimensions and filters not supported by Insight.
- Getting advanced reports across all sales channels.
- Reporting on error related events.
- Combining many dimensions and filters.
- Reporting where no predefined report definitions exist.
Where to Find What
- User Guides for Ooyala Pulse and Ooyala Pulse SSP administrators, ad operations, traffic managers and sales and product managers:
- Developer Guides for developing and validating integrations between
your player and Ooyala 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.
- Ooyala 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).
- Samples integrations and documentation.
- Developer Guides for accessing and handling data in Ooyala Pulse:
- Ooyala Pulse REST API guides and examples.
- Ooyala Pulse REST API references:
- Release Notes for up-to-date information about Ooyala Video Advertising products:
- Ooyala Community for Video Advertising forum and knowledge base articles:
If you are looking for primers on using Ooyala's Video Advertising Products, we have a number of video tutorials with tips, tricks and how-tos. View the video tutorials at Ooyala Training Videos.