Release Notes: January 9, 2017

Improvements

  • Totally New & Improved Documentation: Huzzah! We have a brand-spanking-new system for our knowledge base and our API documentation! It's a lot easier to read, browse, and search for that tasty tidbit of Adzerk knowledge you need, whatever it may be. Add a bookmark to http://dev.adzerk.com/ and set your phasers to fun. We're super-proud and excited to add even more content in 2017!

  • Header Bidding Beta: Another exciting announcement this week is that our beta header bidding solution is ready to go. If you're using the open source Prebid.js then this may look familiar to you. If you're new to header bidding, our docs are a great way to get started. Please note you'll need the creative templates beta feature enabled. If you're interested, please contact [email protected] .

  • UI Reports Performance Improvements: We've added significantly more computing resources to reports and forecasts that are kicked off from the Adzerk UI (as opposed to via our reporting API). This should make reports return noticeably faster for UI users!

Bug Fixes

  • Reporting Errors Improved in UI & API: There were some error cases that made reports fail in the API with a status code of 0 or just "clock" forever in the UI. (The UI would show "generating the report" forever and never return.) We've fixed these error cases and added additional error-handling code in the front and backend reporting systems. From now on, if an error does occur on a report, you will be notified immediately with a correct error code in the API or a message in the UI.

  • Documentation Fix Regarding Create Creatives & Flights Separately: In our API documentation, we had an old example that showed creating a new, nested Creative object when creating a new CreativeFlightMap object (aka an "ad"). This old approach is now deprecated due to many unexpected behaviors. We've removed the example, and we now support only mapping a preexisting flight and creative together with a Creative Flight Map.

On the Tech Blog...

On our latest Adzerk technical blog entry, Sean Chaney explains the "four step process" we use to roll out new versions of existing features without breaking production. In Burning Down Your Backend, Sean tells the story of how we shipped the new Reporting 2.0 system over several months of load testing, tweaking, and tuning before it was finally ready for our production traffic.