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
- HTML5 SDK (Core and Pulse) or any of its derivatives (HTML5 Ad Player and Plugins) for version 126.96.36.199.1 or higher
- iOS Pulse SDK version 188.8.131.52.0 or higher
- Android Pulse SDK version 184.108.40.206.0 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.
- Device group
- Geography (Country, Region, City, and Metro Area)
- Format type
Using Skip Offset from Third-Party VAST Tickets in HTML5 SDK
From version 220.127.116.11.1, 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
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
useVASTSkipOffset is set to
This release includes the following documentation updates: