Geotargeting: Duplicate and obsolete regions fix, asset filtering fix in HTML5 Pulse SDK, additional events sent from HTML5 Pulse SDK and ad player, asset filtering and cache busting changes in Android SDK
Geotargeting: Duplicate and obsolete regions fix
- adding geotargeting rules on global, campaign, and goal level,
- adding geotargeting rules in targeting templates,
- and creating inventory and campaign simulations for a specific geotarget.
Now, with the issue fixed, the duplicate and obsolete regions no longer appear when adding geotargets. However, they are still available in our system, marked with DO NOT USE, so Pulse can display them in campaigns, targeting templates, inventory simulations, and campaign simulations where they were previously used, and also make them available for reporting purposes.
Our provider does not assign any IP addresses to these duplicate and obsolete regions. In order to successfully target the desired regions, you must:
- Remove and/or replace the regions marked with DO NOT USE from the:
- global geotargeting rules,
- geotargeting rules in any running campaigns and/or goals,
- targeting templates, especially those linked to your running campaigns and/or goals.
- Use new location IDs in your Pulse REST API requests, because the location IDs of the duplicate and obsolete regions are now deprecated.
Please contact your CSM (Customer Success Manager) for more information.
Asset filtering fix in HTML5 Pulse SDK
In version 220.127.116.11.0 of the HTML5 Pulse SDK, a fix was made to the asset filtering based on the bandwidth detection introduced in version 18.104.22.168.1. In case the media files of an ad are all filtered out because their bitrates are too high for the detected bandwidth, then the asset with the lowest bitrate is still selected for playback.
Additional events sent from HTML5 Pulse SDK and ad player
From version 22.214.171.124.0, the HTML5 Pulse SDK and Ad Player send a few additional events during ad playback, which you can now respond to and run custom code for in your integration.
These events are:
|Pulse SDK||Ad player||Description|
||25% of the ad has been shown to the viewer|
||50% of the ad has been shown to the viewer|
||75% of the ad has been shown to the viewer|
||The ad was shown to the viewer|
For the HTML5 Ad Player, see heading Listen to Ad Player Events on the Using the Pulse Ad Player page for an example of how to handle these events.
Asset filtering and cache busting changes in Android SDK
- Asset Filtering: previously, asset filtering based on the viewer's user agent was enforced in the Android SDK. Now, you have the option to turn off asset filtering, which means that all media files, available in Pulse for a specific ad, are then also available for playback in your native application. By default, asset filtering is turned on.
- Cache Busting: previously, all tracking URLs in a third-party VAST 2.0 ticket were padded with a cache busting macro, to ensure that multiple events from the same user would trigger properly. Now, you have the option to leave the cache busting macro out of the URLs, if it is not already present. By default, cache busting is turned on.
To turn off asset filtering, set
disableAssetFiltering in the
request settings to
true. To turn off cache busting (when not
already present), set
setEnforceCachebusting in the request
This release includes the following documentation updates: