2017-07-20 Release

Error tracking reporting available in Custom Reporting, using skip offset from third-party VAST tickets in HTML5 SDK

Error tracking reporting available in Custom Reporting

Error tracking reports only work if error tracking is enabled for your account, and you have an integration with at least one of the following SDKs:
  • HTML5 SDK (Core and Pulse) or any of its derivatives (HTML5 Ad Player and Plugins) for version or higher
  • iOS Pulse SDK version or higher
  • Android Pulse SDK version or higher

No error tracking information is available for direct VAST or VMAP integrations.

You can now create Custom Reports for the tracked error events for your integrations. These error events relate to error trackers generally available in VAST tickets (see Error Reporting in the VAST standard), and a few Pulse specific error trackers. A new dimension, filter and metric are available in both the user interface and the REST API.

To create meaningful reports, you should always use the Error Code dimension in combination with the Error metric. You can also report on error counts for the following dimensions:
  • Campaign
  • Goal
  • Ad
  • Device group
  • Geography (Country, Region, City, and Metro Area)
  • Format type
  • Category
  • Tag

Using skip offset from third-party VAST tickets in HTML5 SDK

From version, the HTML5 SDK (and all its derivatives) supports using the skip offset defined in third-party VAST tickets, instead of using the skip offset from the relevant insertion policy defined in Pulse. To enable this functionality in your integration, you must set the new useVASTSkipOffset parameter of the RequestSettings object to true when you create your session.

If you have enabled useVASTSkipOffset, but the third-party VAST ticket has no skip offset defined for the ad, then no skip button is shown for this ad.

By default, useVASTSkipOffset is set to false.

Documentation releases

This release includes the following documentation updates: