Release Notes: February 27, 2017
Improvements
-
Budget Goals on Flights: (BETA) We've expanded our budget goals beta features to include setting budget (i.e. revenue) goals on flights as well as specific ads. If you're interested in beta testing the budget goal feature, please contact [email protected] .
-
Several Internal RTB Improvements: Internally, we've been reorganizing some of our real-time bidding (RTB) code to better support our current partners and to easily add additional partners in the future.
-
Reserved Custom Events: We've officially reserved 200 custom event numbers for your use. (More details)
Bug Fixes
-
Incorrect Ad Codes: A bug had crept in that caused several folks to cut & paste an incorrect ad tag. Specifically the
div
ID could be incorrect causing ads to not be placed on the page. -
Inputing Flight Categories: Folks tracking interests with Behavioral Targeting were having trouble adding interest categories to flights.
-
Header Bidding Zero CPM: Our header bidding beta testers found a bug where if a zero CPM was returned it would cause an error. This doesn't normally happen but can be encountered during testing. If you're interested in beta testing our header bidding solution please contact [email protected] .
UI 2.0 Bug Fixes
We are concentrating on UI 2.0 so everyone can rely on it on an everyday basis. UI 2.0 is in public beta which means it is available for all users. We will continue to add new features and address all reported issues. I encourage you to test it as much as you can, and let us know at [email protected] if you have any questions or encounter any issues.
- Ability to enable passbacks on flights
- Correctly save valid JSON metadata
- Creatives added to a flight were not displaying
- After saving a flight, navigate to the campaign page
- Minute granularity for flight start/end times
- JavaScript console error messages when changing flight start/end dates
In Progress
Lastly, we're heads-down on a couple of important, long-running development efforts. Stay tuned for more details on these in the near future -- reporting on ad requests and a brand-spanking new reporting UI 2.0.