Today we’re pleased to announce the release of the v201605 DFP API. This release focuses on new features for reporting and sales manager.
For a full list of API changes in v201605, see the release notes.
Here is a breakdown of how this dimension behaves:
You can read more about DFP First Look and how it affects the query tool in our help center article.
The second reporting feature is more time zone settings in sales reports. For this, we’ve added a ReportQuery flag called useSalesLocalTimeZone. This option only applies to reports containing sales attributes and metrics. When set to true, all applicable attributes or metrics will be displayed or calculated using proposal or proposal line item time zones, instead of the network time zone.
We’ve also added the long awaited workflowProgress indicator to proposals. The WorkflowProgress contains information such as which step or rule a proposal’s workflow is currently on. This information is equivalent to the progress bar you see in the DFP web UI when viewing a proposal.
Finally, proposals now have a field called offlineErrors that contains errors that might have occurred in background processes. For example, if a proposal failed to reserve inventory, this field will be populated with an error. Proposal.hasOfflineErrors has been added to help you find proposals that have offline errors.
Also, please remember that we are tightening our sunset schedule. DFP versions v201508 and v201511 will both be sunset at the same time at the end of November 2016.
As always, if you have any questions, feel free to drop us a line on the DFP API forums or the Ads Developer Google+ page.
- Vincent Tsao, DFP API Team
