Release Notes: July 17, 2017

Improvements

  • Config Publisher Performance Improvements: Our configuration change publishing system, which pushes management UI & API changes to the ad servers, has had a few growing pains lately. Some folks have suffered slow publish times, where a simple change like enabling a campaign could take an hour or longer to take effect. We're heads-down on a totally new version of this publishing system that will scale as Adzerk continues to grow, but in the meantime we've added some changes this week that will reduce both the likelihood of a publishing slow-down and the impact if one did occur. Most folks, especially those that are not heavy management API users, should only rarely see a large slow-down now.

  • RTB: Geolocation Support: The geolocation (country code and latitude/longitude) of requests are now passed along automatically on each RTB request. This often results in higher CPMs by unlocking locale-specific campaigns.

  • RTB: Additional Pubmatic & Index Exchange Video Parameters: We've been working with Pubmatic and Index Exchange to fine tune the RTB request parameters we pass to improve CPMs and fill. We've made lots of small changes in this area.

  • Targeting Optimization Performance Improvements: Our beta targeting optimization system was putting a bit of unnecessary strain on our configuration database. We've tuned that guy up, and he's running like a champ now. If you're interested in using this beta feature, please contact [email protected] .

Bug Fixes

  • UI 2.0: Missing Flight: Some folks saw a bug in UI 2.0 where when they would create a flight and then navigate to the flight list for the campaign then that newly-created flight would be missing until the page was refreshed. We've coaxed these shy flights to always come out and show themselves.

  • UI 1.0: Campaign List Failures: Some folks were seeing a rash of error pages when trying to view the campaigns list home page in UI 1.0.

  • Publisher Account Field in Scheduled Reporting: The legacy publisher account field, which is similar to a site group, was not correctly grouping or filtering in scheduled reports.

Documentation Additions