Page Summary
-
This document provides important deprecation and sunset dates for Display & Video 360 API versions and features, with announcements also posted on the Google Ads developer blog.
-
Display & Video 360 API versions transition through Release, Deprecation (migration required), and Sunset (no longer supported) stages.
-
Several changes to Structured Data Files (SDF) and API behavior are outlined with specific effective dates, impacting features like Reach Line Items, Video Action Campaigns, custom bidding, audience membership duration, and content category settings.
-
Starting September 8, 2025, it will be mandatory to declare whether new and existing Line Items serve EU political ads via API or SDF.
This page lists the deprecation and sunset dates for API versions and individual features in the Display & Video 360 API.
Deprecations and sunset dates for the API will also be announced on the Google Ads developer blog .
Version Deprecations
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.
This table lists all existing core Display & Video 360 API versions, their release dates, and their deprecation and sunset dates, if announced.
| API Version | Release Date | Deprecation Date | Sunset Date | Migration Guide |
|---|---|---|---|---|
| March 27, 2025 | ||||
| October 31, 2023 | April 2, 2025 | October 7, 2025 | Migrate from v3 to v4 | |
| December 6, 2022 | February 15, 2024 | September 3, 2024 | Migrate from v2 to v3 | |
| March 9, 2020 | March 13, 2023 | September 14, 2023 | Migrate from v1 to v2 |
Feature Deprecations
Follow our Google Ads developer blog for announcements of upcoming significant feature deprecations.
This table lists all announced feature deprecations impacting live versions, providing the initial effective date and a description of the deprecation with recommended actions and links to relevant documentation:
On February 23, 2026, Display & Video 360 will sunset insertion order and campaign targeting. Changes will be made to Display & Video 360 API and Structured Data Files (SDFs) to align with this change. In Display & Video 360 API, a subset of methods will sunset and return an error if called. In SDF, targeting columns in Insertion Order and Campaign files will no longer be populated on download and be required to be empty on upload. It is recommended that users assign targeting directly to line items upon line item creation.
The following Display & Video 360 API methods will return a 404
error if called:
-
advertisers.campaigns.listAssignedTargetingOptions -
advertisers.campaigns.targetingTypes.assignedTargetingOptions.get -
advertisers.campaigns.targetingTypes.assignedTargetingOptions.list -
advertisers.insertionOrders.listAssignedTargetingOptions -
advertisers.insertionOrders.targetingTypes.assignedTargetingOptions.create -
advertisers.insertionOrders.targetingTypes.assignedTargetingOptions.delete -
advertisers.insertionOrders.targetingTypes.assignedTargetingOptions.get -
advertisers.insertionOrders.targetingTypes.assignedTargetingOptions.list -
advertisers.lineItems.generateDefault
Campaign SDF entries that have values assigned to the following columns will fail on upload:
-
Demographic Targeting Gender -
Demographic Targeting Age -
Demographic Targeting Household Income -
Demographic Targeting Parental Status -
Geography Targeting - Include -
Geography Targeting - Exclude -
Language Targeting - Include -
Language Targeting - Exclude -
Digital Content Labels - Exclude -
Brand Safety Sensitivity Setting -
Brand Safety Custom Settings -
Third Party Verification Services -
Third Party Verification Labels -
Viewability Targeting Active View -
Position Targeting - Display On Screen -
Position Targeting - Video On Screen -
Position Targeting - Display Position In Content -
Position Targeting - Video Position In Content -
Inventory Source Targeting - Authorized Seller Options -
Inventory Source Targeting - Include -
Inventory Source Targeting - Exclude -
Inventory Source Targeting - Target New Exchanges -
Environment Targeting
Insertion Order SDF entries that have values assigned to the following columns will fail on upload:
-
Geography Targeting - Include -
Geography Targeting - Exclude -
Proximity Targeting -
Proximity Location List Targeting -
Language Targeting - Include -
Language Targeting - Exclude -
Device Targeting - Include -
Device Targeting - Exclude -
Browser Targeting - Include -
Browser Targeting - Exclude -
Digital Content Labels - Exclude -
Brand Safety Sensitivity Setting -
Brand Safety Custom Settings -
Third Party Verification Services -
Third Party Verification Labels -
Channel Targeting - Include -
Channel Targeting - Exclude -
Site Targeting - Include -
Site Targeting - Exclude -
App Targeting - Include -
App Targeting - Exclude -
App Collection Targeting - Include -
App Collection Targeting - Exclude -
Category Targeting - Include -
Category Targeting - Exclude -
Content Genre Targeting - Include -
Content Genre Targeting - Exclude -
Keyword Targeting - Include -
Keyword Targeting - Exclude -
Keyword List Targeting - Exclude -
Audience Targeting - Include -
Audience Targeting - Exclude -
Affinity & In Market Targeting - Include -
Affinity & In Market Targeting - Exclude -
Custom List Targeting -
Inventory Source Targeting - Authorized Seller Options -
Inventory Source Targeting - Include -
Inventory Source Targeting - Exclude -
Inventory Source Targeting - Target New Exchanges -
Daypart Targeting -
Daypart Targeting Time Zone -
Environment Targeting -
Viewability Omid Targeting Enabled -
Viewability Targeting Active View -
Position Targeting - Display On Screen -
Position Targeting - Video On Screen -
Position Targeting - Display Position In Content -
Position Targeting - Video Position In Content -
Position Targeting - Audio Position In Content -
Video Player Size Targeting -
Content Duration Targeting -
Content Stream Type Targeting -
Audio Content Type Targeting -
Demographic Targeting Gender -
Demographic Targeting Age -
Demographic Targeting Household Income -
Demographic Targeting Parental Status -
Connection Speed Targeting -
Carrier Targeting - Include -
Carrier Targeting - Exclude
Starting September 8, 2025, you will be required to declare whether or not a line item will serve European Union political ads when creating a new line item using Display & Video 360 API or SDFs. These declarations can be made in the following ways:
- Using the
containsEuPoliticalAdsfield in the Display & Video 360 APILineItemresource. You can also make this declaration using new fields inadvertisers.lineItems.duplicateandadvertisers.lineItems.generateDefaultrequests. - Using the
Contains EU Political Adscolumn in the SDF v9 Line Item file type.
If your parent advertiser won't contain any line items that serve EU political ads, then you can declare at the advertiser level using the containsEuPoliticalAds
field in the Display & Video 360 API Advertiser
resource. If this field is set to DOES_NOT_CONTAIN_EU_POLITICAL_ADVERTISING
, then all new line items under the advertiser will be assigned the same value if not otherwise specified and all existing line items under the advertiser will be updated to use the same value if a value is not already set. A line item's declaration can be updated any time after creation using the UI, API, or SDF.
If you can't declare at the advertiser level or have declared that EU political ads may be served under your advertiser, update your Display & Video 360 API and SDF integration before September 8, 2025 to avoid an interruption of service:
- Set the
containsEuPoliticalAdsfield in a newLineItemresource when making anadvertisers.lineItems.createrequest. - Set the
containsEuPoliticalAdsfield in the request body of anyadvertisers.lineItems.duplicateandadvertisers.lineItems.generateDefaultrequests. - Migrate to use Structured Data Files v9 and set the
Contains EU Political Adscolumn for any new line items toYesorNoon upload. See our v9 migration guide for a step-by-step instructions. - Before updating geography targeting for an existing line item using Display & Video 360 API or SDF, update the line item to provide a declaration.
On June 12, 2025, content category configurations for individual YouTube & partners line items will no longer be modifiable level as part of an update to brand suitability experience . Content category settings will instead be solely controlled at the advertiser-level. To accommodate this change, the following changes will be made to the Display & Video 360 API and Structured Data Files:
- The
contentCategoryfield inYoutubeAndPartnersSettingsobjects of YouTube & partnersLineItemresources will no longer be updated. It will be removed entirely at a later date. - The
TrueView Content Filtercolumn in Line Item SDFs will no longer be writable.
- Retrieve the
effectiveContentCategoryfield in place of thecontentCategoryfield when reviewing YouTube & partners line items in the API. - Stop modifying the
TrueView Content Filtercolumn when updating SDF line item entries. Keep the column empty when creating new line items.
Starting on June 12, 2025, you will no longer be able to update the budget settings for line items with parent insertion orders set to optimize using automated bid strategies.
To avoid any interruption of service:- In API: Check if a line item's parent
InsertionOrderhas eitherbidStrategy.maximizeSpendAutoBidorbidStrategy.performanceGoalAutoBidset. If so, don't attempt to update theLineItembudget field usingadvertisers.lineItems.patch. - In SDF: Check if the SDF entry for the line item's parent insertion order
has its
Insertion Order Optimizationcolumn set toTRUE. If so, don't attempt to update theBudget TypeorBudget Amountcolumns for the line item SDF entry.
Starting June 12, 2025, we will remove an existing restriction for URLs targeted in SDF entries that restricted newer sites from being included. Instead, SDF will match API and UI behavior and allow the targeting of URLs as long as they are correctly formatted.
This is relevant toSite Targeting - Include
and Site Targeting - Exclude
columns in Insertion Order
and Line Item
files.On May 1, 2025, entries in Line Item Structured Data Files that attempt to set the "Bid Multipliers" column will fail to create or update resource on file upload.
Starting April 22, 2025, you will be required to include the value "Video Partners" in the TrueView Inventory Source Targeting
column of line item
entries that have a Type
column value of "Demand Gen". Once this enforcement begins, the value will be backfilled for existing line items and included when downloading new Structured Data Files.
To avoid any interruption of service:
- Update your integration to include the "Video Partners" value in all Demand Gen line item entries.
- Update your integration to manage Demand Gen inventory sources at the Ad Group level using SDF v8.1 Ad Group
columns
Demand Gen Inventory Source StrategyandDemand Gen Enabled Inventory Sources.
On April 22, 2025, you will no longer be able to create Line items for video action campaigns using Structured Data Files, as they are being upgraded to Demand Gen
. Line item
entries attempting to be uploaded with a Subtype
column value of "Action" and a Type
column value of "TrueView" will fail.
To avoid any interruption of service, update your integration to use Demand Gen instead of video action campaigns.
On April 7, 2025, FirstAndThirdPartyAudience
resources will no longer allow infinite audience membership duration. firstAndThirdPartyAudiences.create
and firstAndThirdPartyAudiences.patch
requests setting the membershipDurationDays
field value to 10,000 will return a 400
error. Existing audiences with a membershipDurationDays
field value of 10,000 will be updated to 540 and the new membership duration will be retroactively applied to existing memberships. This will expire all memberships older than 540 days.
To avoid any interruption of service:
- Verify that your integration is not setting the
membershipDurationDaysfield value of new or existing audiences to 10,000. - Refresh the memberships of your existing Customer Match audiences using
firstAndThirdPartyAudiences.editCustomerMatchMembers. - Regularly refresh your Customer Match audience memberships to make sure that the list size of your audiences don't get smaller unintentionally.
In v4, this change is reflected in FirstPartyAndPartnerAudience
resources.
On April 1, 2025:
-
advertisers.lineItems.createrequests attempting to set thefloodlightActivityConfigsfield of theConversionCountingConfigobject and thecustomBiddingAlgorithmIdfield ofMaximizeSpendBidStrategyorPerformanceGoalBidStrategyobjects that don't use matching floodlight activities will return a400error. -
advertisers.lineItems.patchrequests attempting to update thefloodlightActivityConfigsfield of theConversionCountingConfigobject while thecustomBiddingAlgorithmIdfield ofMaximizeSpendBidStrategyorPerformanceGoalBidStrategyobjects is set will return a400error. - Entries in Line Item Structured Data Files that attempt to update the "Conversion Floodlight Activity Ids" column when the "Algorithm Id" column is set will fail to update on file upload.
-
customBiddingAlgorithms.patch,customBiddingAlgorithms.rules.create,customBiddingAlgorithms.scripts.createrequests forCustomBiddingAlgorithmresources that are assigned to a line item will return an error.
To avoid any interruption of service, update your integration to:
- Verify that the relevant floodlight activities are assigned to a line item before or at the same time as the assigning of a custom bidding algorithm.
- Existing custom bidding algorithms are unassigned from all line items before attempting to be updated.
Previous feature deprecations
To read about announced deprecations impacting sunset versions of Display & Video 360 API, see our archived deprecations .
