2017-10-12 Release

Ability to target insertion policies against categories using the new Insertion Policy API and UI, HTML5 Ad Player additional events, Custom Reporting Fetch REST API endpoint contains report definition.

Category Targeting in the New Insertion Policy REST API and User Interface

Note: Please contact your Account Manager if you want to use the new Insertion Policy functionality.

The ability to configure targeting settings in the new insertion policies has been extended. Previously, you could only target the new insertion policies against tags, while configuring category based insertion policies was tied to each node of your Account category structure. Now, you can also target the new insertion policies against categories or a combination of tags and categories, both in the new Insertion Policy REST API and User Interface.

  • Target 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.
  • Target 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.

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.

By using tag and category targeting, you reduce the amount of insertion policies you need to configure across your category tree. By default, you can create up to 50 insertion policies for your Pulse account and specify up to 20 tags and/or 29 categories per one insertion policy. Contact your Account Manager if you need to change these values.

Note: Insertion policies without any specified targeting are currently not taken into consideration by the Pulse Distribution Engine.

HTML5 Ad Player Additional Events

A number of events have been added to the HTML5 Ad Player to aid our customers with the following:
  • AD_BREAK_EMPTY: This event is triggered when an ad break should have played, but contained no ads. This way you know that no suitable ads were available, and could potentially extend the session with new request parameters.
  • AD_BREAK_STARTING: This event is triggered right before an ad break is about to start, so before the AD_BREAK_STARTED is triggered, and allows you to insert any additional functionality before the ad player takes over.
  • AD_BREAK_FINISHING: This event is triggered right before an ad break is about to finish, so before the AD_BREAK_FINISHED is triggered, and also allows you to insert any additional functionality before the ad player hands back control to the video player.
  • LINEAR_AD_STARTING: This event is triggered right before a linear ad is about to start, so before the LINEAR_AD_STARTED is triggered, and again allows you to insert any additional functionality before the ad player plays the ad.

The last three new events are mainly used to show any of your own content, like trailers for other shows your viewers may be interested in based on the current show they are watching, or trailers in general.

Custom Report Definition Available when Fetching Report through API

When fetching your Custom Reports in JSON format through the REST API, you now also receive the creation date and report definition in the metadata section of the response body. For example:

{
  "metaData": {
    "creationDate": 1506681978650,
    "name": "Impressions per category and subcategory december 2016",
    "rowCount": 4,
    "reportDefinition": {
      "startDateTime": "2016-12-01T00:00:00+02:00",
      "endDateTime": "2017-01-01T00:00:00+02:00",
      "timeGranularity": "none",
      "dimensions": ["category", "category"],
      "metrics": ["impression"],
      "filters": []
    }
  },
  "headers": [
    {
      "name": "category_0",
      "type": "STRING"
    },
    {
      "name": "category_0_name",
      "type": "STRING"
    },
    {
      "name": "category",
      "type": "STRING"
    },
    {
      "name": "category_name",
      "type": "STRING"
    },
    {
      "name": "impression",
      "type": "INTEGER"
    }
  ],
  "rows": [
    [
      "11",
      "Sports",
      "",
      "",
      6598
    ],
    [
      "",
      "",
      "111",
      "Football",
      8456
    ],
    [
      "",
      "",
      "112",
      "Tennis",
      1574
    ],
    [
      "",
      "",
      "113",
      "Basketball",
      567
    ]
  ]
}

Documentation Releases

This release includes the following documentation updates:

Subscribe to Ooyala Release Notes

See Subscribe to Ooyala Release Notes for instructions on how to subscribe for automated notifications of Ooyala release notes.

Was this article helpful?