Display & Video 360 API versions are released, deprecated, and sunset regularly. These
steps are defined as follows:
Release: The version exits any alpha or beta status and is considered
stable. Feature additions may still be released for the version.
Deprecation: The version is being retired and an end of support (sunset)
date is announced. Users must migrate to a newer version before the sunset
date. Feature additions will no longer be released for the version.
Sunset: The version is no longer supported. Requests made to the version
return an error.
The table below lists all existing core Display & Video 360 API versions, their release
dates, and their deprecation and sunset dates, if announced.
Follow our Google Ads developer blog for announcements of
upcoming significant feature deprecations.
The table below lists all announced feature deprecations, providing the initial
effective date and a description of the deprecation with recommended actions and
links to relevant documentation:
Feature
Initial Effective Date
Description
Targeting Expansion
March 25, 2023
Replacement of the targeting expansion feature with optimized targeting, rolled out gradually from March 25, 2023 to early May 2023. Relevant changes to Display & Video 360 API and Structured Data Files behavior as well as recommended actions were announced in a blog post.
Manual Triggers
May 17, 2023
Timeline:
May 17, 2023: line items using manual triggers will stop serving in Display & Video 360. If you activate a manual trigger linked to an active line item after this date, the line item will not serve ads.
Installed App and New Mobile Devices GoogleAudience Types
May 20, 2023
Timeline:
May 20, 2023: You will no longer be able to assign GoogleAudience resources with a GoogleAudienceType of GOOGLE_AUDIENCE_TYPE_INSTALLED_APPS or GOOGLE_AUDIENCE_TYPE_NEW_MOBILE_DEVICES to line item or insertion order audience targeting. Requests assigning these audiences to a line item's audience targeting will return an error. This includes advertisers.lineItems.duplicate and advertisers.lineItems.generateDefault requests, if the created line item would include deprecated audiences in its audience targeting.
June 8, 2023: Impacted audiences will be removed from all line item and insertion order targeting and from all combined audiences. If a line item is not able to serve ads when these audiences are removed, they will be paused. On this date, these audiences will also no longer be retrievable using the googleAudiences service.
Recommended Tasks:
We recommend that you immediately stop using impacted audiences when making future updates to your line item targeting.
Remove all impacted audiences from existing line item and insertion order targeting. Read about updating audience targeting in our Target Audiences guide.
May 20, 2023: You will no longer be able to assign FirstAndThirdPartyAudience resources with a AudienceType of ACTIVITY_BASED or FREQUENCY_CAP to line item or insertion order audience targeting. Requests assigning these audiences to a line item's audience targeting will return an error. This includes advertisers.lineItems.duplicate and advertisers.lineItems.generateDefault requests, if the created line item would include deprecated audiences in its audience targeting.
June 8, 2023: Impacted audiences will be removed from all line item and insertion order targeting and from all combined audiences. If a line item is not able to serve ads when these audiences are removed, they will be paused. On this date, these audiences will also no longer be retrievable using the firstAndThirdPartyAudiences service.
Recommended Tasks:
We recommend that you immediately stop using impacted audiences when making future updates to your line item targeting.
Remove all impacted audiences from existing line item and insertion order targeting. Read about updating audience targeting in our Target Audiences guide.
Existing API Quota Limits
May 30, 2023
On May 30, 2023, existing usage limits will be replaced with a hybrid quota structure that does the following:
Eliminates the requests per day per project quota.
Institutes a requests per minute per advertiser per project quota for qualifying methods.
These new limits will allow greater flexibility in API usage and enable parallelization of requests across advertisers. Details of this change are in our existing quota limit documentation.
OR operator usage between restrictions of different fields in LIST filters
June 21, 2023
On June 21, 2023, LIST request filter parameters will no longer allow OR logical operators to be used between restrictions of different fields.
For example, resources identified with filter string lineItemType="LINE_ITEM_TYPE_DISPLAY_DEFAULT" OR insertionOrderId="123" must instead be retrieved using two LIST requests with the following filter strings:
Review the filter query parameters of all your existing LIST calls and verify that they are using the OR logical operator correctly before June 21, 2023 to avoid an interruption of service.
Remove all filter logic using these four fields before June 21, 2023 to avoid an interruption of service.
Outcome based buying
August 1, 2023
On August 1, 2023, insertion orders using outcome based buying, defined by a billableOutcome field value of BILLABLE_OUTCOME_PAY_PER_CLICK or BILLABLE_OUTCOME_PAY_PER_VIEWABLE_IMPRESSION, and their child line items will be archived.