Google Ads Developer Blog: update
Today we’re releasing an update to the Display & Video 360 API which includes the following features: release notes .client library to the latest version .support contact form .
Today we’re releasing an update to the Display & Video 360 API which includes the following features: More detailed information about this update can be found in the Display & Video 360 API release notes .If you run into issues or need help with these new features, please contact us using our
support contact form .
Today we’re releasing an update to the Display & Video 360 API v1 which includes the following features: If you run into issues or need help with these new features, please contact us using our
support contact form .
Today we’re releasing an incremental update to the Display & Video 360 API v1 which includes the following features:
Today’s update also includes changes to
how quota is handled in the Display & Video 360 API. The following usage limits are now in effect:
A default daily limit of 86,400 total requests made to the API per project. This limit can be increased on a case-by-case basis to customers who have demonstrated need for a higher limit. A rate limit of 600 total requests per minute. A rate limit of 300 write requests per minute, which are calls to methods (such as create, patch, delete, and bulkEdit) that modify resources. More detailed information about this update can be found in the Display & Video 360 API
release notes .
Before using these new features, make sure to update your client library to the latest version.
If you run into issues or need help with these new features, please contact us using our
support contact form .
On October 1, 2020, we are upgrading the classification of the authorization scope used for the DoubleClick Bid Manager API ( https://www.googleapis.com/auth/doubleclickbidmanager ) to “sensitive ”. This upgrade is taking place to better secure the DBM API and the data retrieved from it.for the first time will encounter an “unverified app screen” upon attempted authentication. This screen can be removed by submitting your app to our verification process . This process usually takes about 3 to 5 business days. Information on how this process fits in the larger task of authorizing requests can be found in our guide .In anticipation of this requirement, it is recommended that existing apps complete the verification process at their earliest convenience. If you run into issues or need help with this process, please contact us using our
support contact form .
Today we’re releasing an incremental update to the Display & Video 360 API v1 which includes the following features:release notes page.support contact form .
Today we’re releasing an update to the
Display & Video 360 API v1 which includes the following features:
More detailed information about this update can be found on the Display & Video 360 API
release notes page.
Before using these new features, make sure to update your client to the latest version. For more information on how to use some of these new features, you can read our new
User Management guide and
Auditing Account Limits page .
If you run into issues or need help with these new features, please contact us using our
support contact form .
We’re launching an incremental update to the
Display & Video 360 API v1 today. The update includes:
A more detailed summary of this update can be found on the Display & Video 360 API
release notes page. You can take advantage of these additional features by updating your
client library to the most recent version.
If you run into issues or need help using this new functionality, please contact us using our
support contact form .
ZW5kZW5yYWhheXU5QGdtYWlsLmNvbQ==
