Google Ads Developer Blog

March 2021 update to Display & Video 360 API v1

2021-03-30T10:47:00.000-07:00

Today we’re releasing an update to the Display & Video 360 API which includes the following features:

A new method in the line item service that generates a line item with default settings and assigned targeting in a manner identical to line item creation in the Display & Video 360 UI.
A new campaign targeting service and bulk list method enabling the retrieval of campaign targeting.
A new appPlatform field in the app targeting details object for targeting apps on additional platforms.
A new replace method for advertisers.channels.sites, partners.channels.sites and advertisers.negativeKeywordLists.negativeKeywords services that fully overwrites the existing sites of a channel or negative keywords of a keyword list.

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

2021-03-02T07:10:00.000-08:00

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

2021-02-24T10:32:00.001-08:00

Today we’re releasing an update to the Display & Video 360 API which includes the following features:

A new insertion order targeting service and bulk list method enabling the retrieval of insertion order targeting.
Additional output-only fields mp3Audio and oggAudio for third-party audio creatives.
Support for more performance goal types to assign to insertion orders and campaigns, including click and impression conversion rate performance goals.

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

Sunset date for deprecated DBM API services postponed to April 15, 2021

2021-02-23T12:21:00.000-08:00

The sunset of deprecated services in the DoubleClick Bid Manager (DBM) API, originally scheduled for February 26, 2021, has been postponed to April 15, 2021. The deprecated services scheduled for sunset include the entirety of DBM API v1, the DBM API v1.1 SDF Download service, and the DBM API v1.1 Line Item service.

Prior blog posts regarding this sunset give instructions on how to migrate from these deprecated services to either the DBM API v1.1 Reporting service or the Display & Video 360 (DV360) API. Consult these previous announcements for more information.

If you encounter issues with your migration or want to report a separate issue, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team

January update to Display & Video 360 API v1

2021-01-28T12:09:00.000-08:00

Today we’re releasing an update to the Display & Video 360 API which includes the following features:

Support for retrieval and management of TV insertion orders and over-the-top line items through the introduction of an insertionOrderType field and new LineItemType enum value.
Full support of mobile app line items with the addition of a mobileApp field in the LineItem resource.
Additional values for Exchange, GoogleAudienceType, and SdfVersion enums.
The ability to filter and order advertiser.list responses by updateTime.

- Trevor Mulchay, Display & Video 360 API Team

December update to Display & Video 360 API v1

2020-12-04T12:51:00.000-08:00

Today we’re releasing an update to the Display & Video 360 API which includes the following features:

A new search method in the Targeting Options service for Geo Region targeting options.
The ability to filter and order list responses by updateTime in the Campaigns, Insertion Orders, and Line Items services.
An additional LineItemWarningMessage enum value that informs users when a line item is using deprecated geographic targeting.

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

Upcoming sunset for DBM API v1, SDF Download and Line Item services

2020-11-30T11:23:00.000-08:00

As announced in August, deprecated services in the DoubleClick Bid Manager (DBM) API, comprised of DBM API v1, the DBM API v1.1 SDF Download service, and the DBM API v1.1 Line Item service, will be sunset on February 26, 2021.

If you are still using the DBM API v1 Reporting service, you must migrate to the DBM API v1.1 Reporting service before the sunset date to avoid an interruption of service. Consult the API release notes for details of the changes between v1 and v1.1. Differences to note during this migration include:

Queries created and accessed through the Reporting service require more specific filters in the params.groupBy field in v1.1. You might have to add more values to the params.groupBy field in order to create the same report structure generated in v1.
Responses from queries.listqueries and reports.listreports calls are paginated in v1.1. You have to update your implementation to traverse multiple pages if you want to consume more than the first 100 items returned.

If you are using any version of any other DBM API service, you must migrate to the Display & Video 360 (DV360) API.

The DBM API SDF Download service is being replaced by the DV360 API asynchronous SDF Download service. It features new filter options and a new download format.
The DBM API Line Item service is being replaced by the DV360 API Line Item service. This service provides create, update, and delete methods for line items using a more easily managed REST Line Item resource, separate from Entity Write File format currently used in the DBM API.

Guides are available to help you set up and start using the Display & Video 360 API to download SDFs and manage your line items.

If you encounter issues with your migration or want to report a separate issue, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Sunset of deprecated Geo Region targeting options in Display & Video 360 API

2020-11-20T13:44:00.000-08:00

Starting January 2021, over 1500 deprecated Geo Region targeting options will no longer be supported in Display & Video 360. This announcement, along with the full list of deprecated options, can be found on the Geography Targeting Help Center article. These deprecated targeting options reflect outdated geographical regions and, therefore, do not change the serving of line items.

How will this happen in the API?

This sunset will be reflected in the Display & Video 360 API through the following sequence of events:

Starting today, we will begin removing deprecated targeting from older resources. These resources consist of Line Items or Insertion Orders that are currently archived or have been paused for more than six months.
In February 2021, the deprecated targeting options will no longer be retrievable through the Targeting Options service and attempts at assigning or removing deprecated targeting through the Line Item Assigned Targeting Options service will return an error.
After the deprecated targeting options are no longer able to be assigned, we will begin removing deprecated targeting from all remaining resources. Any line items only using deprecated targeting will be paused upon the removal of said targeting. This concludes the formal sunset of the deprecated targeting options.

What should I do to prepare for this?

In anticipation of this sunset, it is recommended that you do the following:

Check to see if any existing Line Items utilize deprecated targeting options. Use advertisers.lineItems.targetingTypes.assignedTargetingOptions.list to list the assigned Geo Region targeting for each active line item and check the targeting against the deprecated targeting options. Remove or replace any deprecated targeting as soon as possible using advertisers.lineItems.bulkEditLineItemAssignedTargetingOptions.
If you are storing oft-used targeting option IDs locally, cross-reference them against the list of deprecated targeting options. This will avoid errors caused by attempting to assign sunset targeting options.

Should I expect more deprecations in the future?

Users should expect the occasional deprecation and sunset of targeting options in Display & Video 360 in much smaller quantities than this deprecation. As such, future deprecations likely won’t be announced through a blog post or documentation change.

In order to account for these deprecations, it is recommended that you use targetingTypes.targetingOptions.get to confirm that a targeting option is still available before assigning it. This should be done before assigning any option not obtained through the Targeting Options service, including those stored locally or copied from existing targeting. This will avoid errors caused by attempting to assign deprecated targeting.

You can read more about the Targeting Options and Assigned Targeting Options services in our reference documentation and on the Set Targeting page of our Managing Line Items guide.
If you have questions or run into issues navigating this process, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team

November update to Display & Video 360 API v1

2020-11-10T05:40:00.001-08:00

Today we’re releasing an update to the Display & Video 360 API v1 which includes the following features:

A manual trigger service that allows users to create, activate, and deactivate manual triggers through the API. Manual triggers, when assigned to a line item, allow you to quickly switch on and ramp up spending for that line item. Manual triggers can also now be assigned to line items using a new line item flight field and enum value.
New targeting expansion options that can enable the widening of existing audience targeting to include similar users.
The addition of customSegmentId fields for DoubleVerify and Integral Ad Science objects used in the assigning of third-party verification targeting.

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

2020-10-12T12:22:00.000-07:00

Today we’re releasing an incremental update to the Display & Video 360 API v1 which includes the following features:

A new warningMessages field for line items. This field exposes warnings usually displayed in the platform UI that do not obstruct the line item from being saved, but may affect or block the serving of the line item.
A click-through rate (CTR) performance goal type for the performance goal object utilized in campaigns and insertion orders.

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

Filter options update to Display & Video 360 API v1

2020-08-28T08:11:00.000-07:00

Today we’re releasing an incremental update to the Display & Video 360 API v1 which includes the following features:

New filterable fields for various list methods, including targeting option subtypes carrierAndIspDetails.type and geoRegionDetails.geo_region_type for the targetingTypes.targetingOptions.list method.
Additional fields in the advertisers.audit method response body that allow for the tracking of more entity counts against their account entity limits.

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.

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

Sunset of DBM API v1, SDF Download and Line Item services

2020-08-27T10:59:00.000-07:00

Today we’re announcing the deprecation of the Doubleclick Bid Manager (DBM) API v1.1 Line Item service and the sunset of all deprecated DBM API services on February 26, 2021. Deprecated DBM API services include the entirety of DBM API v1 and DBM API v1.1 Structured Data File (SDF) Download service. This sunset was originally scheduled for June 15, 2020, but was postponed due to COVID-19.

Refer to the table below to verify if the methods you are currently using will be available in v1.1 after February 26, 2021:

Service	Methods	Available in v1.1 after February 26, 2021?
Reporting	queries.createquery queries.deletequery queries.getquery queries.listqueries queries.runquery reports.listreports	Yes
Line Item	lineitems.downloadlineitems lineitems.uploadlineitems	No. Use the new Display & Video 360 API instead.
SDF Download	sdf.download	No. Use the new Display & Video 360 API instead.

If you are still using the DBM API v1 Reporting service, you must migrate to v1.1 by the sunset date to avoid an interruption of service. Consult the API release notes for the finer details of the changes between v1 and v1.1. Differences to note during this migration include:

Queries created and accessed through the Reporting service require more specific filters in the params.groupBy field in v1.1. You might have to add more values to the params.groupBy field in order to create the same report structure generated in v1.
Responses from queries.listqueries and reports.listreports calls are paginated in v1.1. Users have to update their implementation to traverse multiple pages if they wish to consume more than the first 100 items returned.

If you are using any version of any other DBM API service, you must migrate to the Display & Video 360 (DV360) API.

The DBM API SDF Download service is being replaced by the DV360 API asynchronous SDF Download service. It features new filter options and a new download format.
The DBM API Line Item service is being replaced by the DV360 API Line Item service. This service provides create, update, and delete methods for line items using a more easily managed REST Line Item resource separate from Entity Write File format currently used in the DBM API.

Guides are available to help you set up the Display & Video 360 API and get started using it to download SDFs and manage your line items.

If you encounter issues with your migration or want to report a separate issue, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team

August update to Display & Video 360 API v1

2020-08-04T14:09:00.000-07:00

Today we’re releasing an update to the Display & Video 360 API v1 which includes the following features:

A user service that allows for the management of Display & Video 360 users and their assigned user roles.
Partner and partner targeting services that enable users to retrieve partner resources and edit partner targeting.
A custom bidding algorithm service that users can utilize to retrieve existing custom bidding algorithm resources for use in managing insertion order or line item bidding strategies.
The additions of a new advertiser.audit method and lineItem.list orderBy and filter capabilities to give users tools to proactively avoid reaching account entity limits.
A new audio line item type that enables API support for audio line items.

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.

- Trevor Mulchay, Display & Video 360 API Team

Incremental update to Display & Video 360 API v1

2020-06-26T07:04:00.000-07:00

We’re launching an incremental update to the Display & Video 360 API v1 today. The update includes:

A create method for partner and advertiser channels.
New fields for FirstAndThirdPartyAudiences.
Additional exchange options.

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.

- Trevor Mulchay, Display & Video 360 API Team

June update to Display & Video 360 API v1

2020-06-02T13:15:00.000-07:00

Today we’re releasing an update to the Display & Video 360 API v1 which includes the following features:

Advertiser targeting capabilities that allow you to add or remove channel, digital content label, and sensitive category targeting options for an advertiser. These targeting changes are then applied to all current and future campaigns.
Targetable entity management that allows you to create and update Inventory Source Groups, Negative Keyword Lists, and Location Lists. Channels can now be updated as well, but not created.
A new Creative entity field lineItemIds which is output only and lists the line items the creative is currently associated with. The Creatives service list method now supports this field in its filter parameter.

More detailed information about this update can be found on the Display & Video 360 API release notes page.

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

Postponement of DBM API v1 and SDF Download Service Sunset

2020-05-15T12:06:00.000-07:00

We’re officially postponing the planned sunset of the Doubleclick Bid Manager (DBM) API v1 and the DBM API v1.1 Structured Data File (SDF) Download service.

Originally scheduled for June 15, 2020, we are delaying the sunset indefinitely in order to account for the difficulties many users are facing due to COVID-19. We’re hoping that this postponement frees up room for users to address more immediately pressing issues. An updated sunset schedule will be announced at a later date.

Although a sunset date is no longer scheduled, these services are still deprecated and migrations to DBM API v1.1 and the Display & Video 360 (DV360) API are recommended.
- Trevor Mulchay, Display & Video 360 API Team

Major Display & Video 360 API v1 Feature Update

2020-04-28T10:29:00.000-07:00

Today we’re providing a major feature update to the Display & Video 360 API v1.

This update includes the following features:

Core resource management that allows you to create, retrieve, update, and delete entities such as Advertisers, Campaigns, Insertion Orders, and Line Items.
Line item targeting capabilities that allow you to edit or retrieve current targeting options for a line item individually or in bulk.
Creative resource management that allows you to upload creative assets, create creatives, and assign those creatives to line items.

Read the release notes for a more detailed list of this new functionality.

You can get started with the Display & Video 360 API and follow our new guides to begin managing your line items and creating new creatives.

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

Deprecation of DBM API v1 and SDF Download Service

2020-03-18T13:56:00.000-07:00

Today we’re announcing the deprecation of the Doubleclick Bid Manager (DBM) API v1 and the DBM API v1.1 Structured Data File (SDF) Download service. These services will no longer be supported and will be fully sunset on June 15, 2020. Refer to the table below to verify if methods you’re using will be available in v1.1 after June 15, 2020:

Service	Methods	Available in v1.1 after June 15, 2020?
Reporting	queries.createquery queries.deletequery queries.getquery queries.listqueries queries.runquery reports.listreports	Yes
Line Item Settings	lineitems.downloadlineitems lineitems.uploadlineitems	Yes
SDF Download	sdf.download	No. Use the new Display & Video 360 API instead.

If you are using the DBM API v1 Line Item Settings service or Reporting service, you must migrate to v1.1 by the sunset date to avoid an interruption of service. Consult the API release notes for the finer details of the changes between v1 and v1.1. Important things to know are:

Queries created and accessed through the Reporting service require more specific filters in the params.groupBy field in v1.1. You might have to add more values to the params.groupBy field in order to create the same report structure they generated in v1.
Responses from listqueries and listreports calls are paginated in v1.1. Users have to update their implementation to traverse multiple pages if they wish to consume more than the first 100 items returned.
The Line Item Settings service had no changes between v1 and v1.1. Users only have to update the version they are using.

The SDF Download service is deprecated in DBM API v1 and v1.1. Users should immediately migrate to the new Display & Video 360 API, which was released earlier this week. The Display & Video 360 API offers a new asynchronous SDF Download Service featuring new filter options and a new download format compared to its DBM API counterpart.

Guides are available to help you set up the new Display & Video 360 API, as well as use it to get started downloading SDFs.

- Trevor Mulchay, Display & Video 360 API Team

Introducing Display & Video 360 API v1

2020-03-09T10:04:00.000-07:00

Today we’re releasing the Display & Video 360 API v1. It offers a new, improved way to interact with your Display & Video 360 resources programmatically.

This initial API release includes new asynchronous Structured Data File (SDF) download functionality. This allows for the generation and downloading of large SDFs without worrying about individual API requests timing out. This is a change compared to the existing DoubleClick Bid Manager (DBM) API SDF Download service. Along with this change, other major changes include:

New default version logic that utilizes the default version of the partner or advertiser specified by the user.
New filter capabilities, including the ability to specify the exact resources to include in the generated files.
New response format that returns the generated SDFs as a .zip file to download, rather than JSON.

The Display Video 360 API SDF Download service will be replacing the DBM API SDF Download service. The deprecation of that service will be announced soon, and an immediate migration to the new API is advised. You can get started setting up the Display & Video 360 API here, and downloading Structured Data Files here.

More functionality will be coming to the Display & Video 360 API in the coming months, including line item management and targeting. Keep an eye out for future announcements!

- Trevor Mulchay, Display & Video 360 API Team