Tag Archives: dv360_api

November 2021 update to Display & Video 360 API v1

Today we’re releasing an update to the Display & Video 360 API that primarily adds full support for managing custom bidding algorithms and their scripts. The update 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 include a page describing the full process of implementing a custom bidding strategy using the Display & Video 360 API.

If you run into issues or need help with these new features or samples, please contact us using our support contact form.

September 2021 update to Display & Video 360 API v1


Today we’re releasing an update to the Display & Video 360 API that 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 or samples, please contact us using our support contact form.

September 2021 update to Display & Video 360 API v1


Today we’re releasing an update to the Display & Video 360 API that 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 or samples, please contact us using our support contact form.

August 2021 update to Display & Video 360 API v1

Today we’re releasing an update to the Display & Video 360 API that 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 or samples, please contact us using our support contact form.

Deprecation of Entity Read Files

Today we’re announcing the deprecation of Entity Read Files (ERFs). Users currently retrieving Display & Video 360 resource information from ERFs should begin migrating to using the Display & Video 360 (DV360) API or Structured Data Files (SDFs).

With this deprecation, we will no longer support ERFs through documentation updates or bug fixes. ERFs will continue to be generated and available for download for the immediate future. However, users should be prepared for ERFs to sunset at a later date. We will announce a sunset date in a future blog post and publish a notice on the ERF documentation page far in advance of the sunset.

Refer to our ERF to API Migration guide for more detailed information about the differences between ERFs and the DV360 API and how ERF information maps to the API resources and services.

If you run into issues, need help with your migration, or have any questions, please contact us using our support contact form.


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.

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.

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.

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.

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.