Tag Archives: update

May 2021 update to Display & Video 360 API v1

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. Before using these new features, make sure to update your client library to the latest version.

We also recently published a collection of code samples on GitHub. The samples, available in Python, Java, and PHP, demonstrate how to interact with the Display & Video 360 API using the available client libraries.
If you run into issues or need help with these new features or samples, please contact us using our support contact form.
- Trevor Mulchay, Display & Video 360 API Team

April 2021 update to Display & Video 360 API v1

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.

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.
- Trevor Mulchay, Display & Video 360 API Team

March 2021 update to Display & Video 360 API v1

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.

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.
- Trevor Mulchay, Display & Video 360 API Team

New validation for line items in Display & Video 360 API

Beginning in May 2021, the Display & Video 360 API will start enforcing new validation when creating or updating line item resources.

This validation will require all Floodlight activity configurations in a line item to use the same lookback windows. All TrackingFloodlightActivityConfig objects assigned to conversionCounting.floodlightActivityConfigs in a line item must have the same postClickLookbackWindowDays value and the same postViewLookbackWindowDays value. The values of the two lookback window types do not have to be the same.

This validation will be enforced when creating new line items or updating the conversionCounting.floodlightActivityConfigs field of an existing line item. 
Requests that do not comply will return one of two errors, depending on the invalid field: “Floodlight click windows must be the same” or “Floodlight view windows must be the same.”

Once this validation is in effect, you will still be able to retrieve and update unrelated fields of line items that do not comply with this rule.

If you run into issues or have questions regarding this new validation, please contact us using our support contact form.
- Trevor Mulchay, Display & Video 360 API Team

February 2021 update to Display & Video 360 API v1

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.

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.
- Trevor Mulchay, Display & Video 360 API Team

January update to Display & Video 360 API v1

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.

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.


- Trevor Mulchay, Display & Video 360 API Team

December update to Display & Video 360 API v1

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.

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.
- Trevor Mulchay, Display & Video 360 API Team

November update to Display & Video 360 API v1

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 in the Display & Video 360 API release notes.

Before using these new features, make sure to update your client library to the latest version. We have also updated our Managing Line Items guide to discuss serving ads using manual triggers.

If you run into issues or need help with these new features, please contact us using our support contact form.
- Trevor Mulchay, Display & Video 360 API Team

October update to Display & Video 360 API v1

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.
- Trevor Mulchay, Display & Video 360 API Team

DoubleClick Bid Manager API upgrading authorization scope to "sensitive"

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.

Starting on October 1st, all unverified apps that are using the DBM API 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.

Existing apps that began using the DBM API scope before October 1st will not see the “unverified app screen” and will not immediately need to go through the verification process. However, all apps accessing sensitive scopes will require explicit verification before the end of 2021. 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.
- Trevor Mulchay, Display & Video 360 API Team