2019-10-16 Release

Scheduled removal of old and unused ad assets from Pulse, ability to estimate the duration of third-party ads using the Pulse Ad REST API, and Goal UI and REST API bug fix.

Scheduled Removal of Old and Unused Ad Assets from Pulse

We are making improvements to our asset file storage and, as part of this process, we will be removing old and unused asset files from Pulse on 1 April 2020. This applies to all files uploaded to Pulse, regardless of the upload method. Files that are linked to an active or upcoming campaign will not be removed.

Timeline

  • Files that have been uploaded to Pulse before 7 August 2019, and that are not linked to an active or upcoming campaign by 1 April 2020, will be removed on 1 April 2020.
  • Files that have been uploaded to Pulse before 7 August 2019, and are linked to an active or upcoming campaign by 1 April 2020, will not be removed.
  • Files that have been uploaded to Pulse after 7 August 2019 are not affected even if they are not linked to any campaign.

If, for any reason, you still need the old and unused files that have been transcoded using the Pulse Asset Factory, you can download them from the Asset Factory by 1 April 2020. The asset files are ordered by time of upload, with most recent assets at the top. If you need to find out the exact date of upload, or have any questions, contact your Account Manager.

Estimated Duration of Third-party Ads Available in Pulse Ad REST API

Note: If you are using Time Based Breaks, you have to estimate the duration of the third-party ad. If the ad does not have an estimated duration, or exceeds the time based break duration, it will not get selected.

Previously, you could estimate the duration of standard third-party ads only through the Pulse user interface. Now, when handling standard third-party ads through the Ad API, you can also set (POST), update (PUT), and retrieve (GET) the estimatedAdDuration in seconds. The standard third-party creative type looks as follows:

"creative": {
  "type": "thirdparty",
  "insertionPoint": "<preroll|midroll|postroll>",
  "vastUri": "<string>",
  "vpaidStrict": "<boolean>", (Optional)
  "vpaidCountdown": "<boolean>", (Optional)
  "estimatedAdDuration": "<positive integer from 1 to 9999>"  (Optional, duration in seconds) 
}

Goal UI and REST API Bug Fix

There was an issue with updating active and upcoming goals through the Goal UI and API, where you could update the start date and time to a date and time in the past. This caused delivery issues as it made it seem like the goal was lagging behind and under-delivering so Pulse would significantly accelerate the delivery to catch up, which led to uneven or over-delivery.

From 16 October 2019, with the issue fixed, if you try updating the start date and time of active or upcoming goals to a date and time in the past, you will not be able to save the change in the UI, and the Goal API will return an error. Things to keep in mind:
  • The start date and time of active goals can only be updated to a future start date and time, starting from the current date and time, or remain set to the original creation date and time in the past.
  • The start date and time of upcoming goals can only be updated to a future start date and time, starting from the current date and time.

Documentation Releases

This release includes the following documentation updates: