This page lists the deprecation and sunset dates for [API
versions](https://developers.google.com/display-video/api/deprecations#versions) and [individual features](https://developers.google.com/display-video/api/deprecations#features) in the
Display \& Video 360 API.

Deprecations and sunset dates for the API will also be announced on the
[Google Ads developer blog](https://ads-developers.googleblog.com/).

## 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 |
|---|---|---|---|---|
| [v4](https://developers.google.com/display-video/api/reference/rest/v4) | March 27, 2025 |   |   |   |
| [v3](https://developers.google.com/display-video/api/reference/rest/v3) | October 31, 2023 | April 2, 2025 | October 7, 2025 | [Migrate from v3 to v4](https://developers.google.com/display-video/api/v4-migration-guide) |
| [v2](https://developers.google.com/display-video/api/reference/rest/v2) | December 6, 2022 | February 15, 2024 | September 3, 2024 | [Migrate from v2 to v3](https://developers.google.com/display-video/api/v3-migration-guide) |
| [v1](https://developers.google.com/display-video/api/reference/rest/v1) | March 9, 2020 | March 13, 2023 | September 14, 2023 | [Migrate from v1 to v2](https://developers.google.com/display-video/api/v2-migration-guide) |

## Feature Deprecations

Follow our [Google Ads developer blog](https://ads-developers.googleblog.com/search/label/dv360_api) 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:

| Feature | Initial Effective Date | Description |
|---|---|---|
| Business name and logo values required for YouTube responsive ads | October 12, 2026 | Starting October 12, 2026, business name and logo assets will be required for YouTube responsive ads if a default value is not set for the advertiser. As a result, the `Business Name` and `Logo Asset IDs` columns in [Ad](https://developers.google.com/display-video/api/structured-data-file/v10-1/AdGroupAd) SDFs will be required to be set for ads of type "Responsive" if default values are not assigned to the parent advertiser. If a default value is assigned and the column is left empty, the ad will inherit the advertiser-level defaults upon saving. |
| Deprecating sensitive category exclusion | October 1, 2026 | Starting October 1, 2026, you will no longer be able to exclude the majority of sensitive categories when assigning line item targeting. To accommodate this change, the following changes will be made to the Display \& Video 360 API and Structured Data Files: - The following [`SensitiveCategory`](https://developers.google.com/display-video/api/reference/rest/v4/SensitiveCategory) enum values will be deprecated and no longer be accepted in the [`excludedSensitiveCategory`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.adGroups.targetingTypes.assignedTargetingOptions#AssignedTargetingOption.SensitiveCategoryAssignedTargetingOptionDetails.FIELDS.excluded_sensitive_category) field of the [`SensitiveCategoryAssignedTargetingOptionDetails`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.adGroups.targetingTypes.assignedTargetingOptions#AssignedTargetingOption.SensitiveCategoryAssignedTargetingOptionDetails) object when assigning targeting of type `TARGETING_TYPE_SENSITIVE_CATEGORY_EXCLUSION`: - `SENSITIVE_CATEGORY_ADULT` - `SENSITIVE_CATEGORY_ALCOHOL` - `SENSITIVE_CATEGORY_DEROGATORY` - `SENSITIVE_CATEGORY_DOWNLOADS_SHARING` - `SENSITIVE_CATEGORY_DRUGS` - `SENSITIVE_CATEGORY_GAMBLING` - `SENSITIVE_CATEGORY_POLITICS` - `SENSITIVE_CATEGORY_PROFANITY` - `SENSITIVE_CATEGORY_RELIGION` - `SENSITIVE_CATEGORY_SENSITIVE_SOCIAL_ISSUES` - `SENSITIVE_CATEGORY_SHOCKING` - `SENSITIVE_CATEGORY_SUGGESTIVE` - `SENSITIVE_CATEGORY_TOBACCO` - `SENSITIVE_CATEGORY_TRAGEDY` - `SENSITIVE_CATEGORY_TRANSPORTATION_ACCIDENTS` - `SENSITIVE_CATEGORY_VIOLENCE` - `SENSITIVE_CATEGORY_WEAPONS` - The `Brand Safety Sensitivity Setting` column in [Line Item](https://developers.google.com/display-video/api/structured-data-file/v10-1/LineItem) SDFs will no longer allow the option "Use custom". - The `Brand Safety Custom Settings` column in [Line Item](https://developers.google.com/display-video/api/structured-data-file/v10-1/LineItem) SDFs will no longer be supported and will be populated with an empty value on download. |
| Deprecating digital content label exclusion | October 1, 2026 | Starting October 1, 2026, you will no longer be able to exclude specific digital content labels using targeting. To accommodate this change, the following changes will be made to the Display \& Video 360 API and Structured Data Files: - The following [`ContentRatingTier`](https://developers.google.com/display-video/api/reference/rest/v4/ContentRatingTier) enum values will be deprecated and no longer be accepted in the [`excludedContentRatingTier`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.adGroups.targetingTypes.assignedTargetingOptions#AssignedTargetingOption.DigitalContentLabelAssignedTargetingOptionDetails.FIELDS.excluded_content_rating_tier) field of the [`DigitalContentLabelAssignedTargetingOptionDetails`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.adGroups.targetingTypes.assignedTargetingOptions#AssignedTargetingOption.DigitalContentLabelAssignedTargetingOptionDetails) object when assigning targeting of type `TARGETING_TYPE_DIGITAL_CONTENT_LABEL_EXCLUSION`: - `CONTENT_RATING_TIER_FAMILIES` - `CONTENT_RATING_TIER_GENERAL` - `CONTENT_RATING_TIER_MATURE` - `CONTENT_RATING_TIER_PARENTAL_GUIDANCE` - `CONTENT_RATING_TIER_TEENS` - `CONTENT_RATING_TIER_UNSPECIFIED` - The `Digital Content Labels - Exclude` column in [Line Item](https://developers.google.com/display-video/api/structured-data-file/v10-1/LineItem) SDFs will only allow assignment of the option "?", otherwise the column must be empty. Attempting to assign any other value will result in an error on upload. |
| Nielsen as a third-party vendor measuring brand lift | July 13, 2026 | Starting July 13, 2026, Nielsen will no longer be able to be assigned as a third-party vendor for measuring brand lift. To accommodate this change, the following changes will be made to the Display \& Video 360 API and Structured Data Files: - The [`ThirdPartyVendor`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.lineItems#ThirdPartyVendor) enum value `THIRD_PARTY_VENDOR_NIELSEN` will no longer be accepted in the [`LineItem`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.lineItems#LineItem) resource under the [`ThirdPartyMeasurementConfigs`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.lineItems#ThirdPartyMeasurementConfigs) object field [`brandLiftVendorConfigs.vendor`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.lineItems#ThirdPartyVendorConfig.FIELDS.vendor). - The `TrueView Third-Party Brand Lift Vendor` column in [Line Item](https://developers.google.com/display-video/api/structured-data-file/v10/LineItem) SDFs will no longer allow the option "Nielsen". Existing use of Nielsen as a brand lift vendor will be removed. In order to avoid an interruption of service, remove any assignment of Nielsen as a brand lift vendor from your integration. |
| Default business name and logo inheritance | July 13, 2026 | Starting July 13, 2026, YouTube responsive ads will begin supporting business name and logo assets and all Demand Gen and YouTube responsive ads with unset business name and logo assets will inherit any default values set at the advertiser level. At the same time, This change will cause the following changes to the behavior of Display \& Video 360 API and Structured Data Files: - The `businessName`, `logo`, and `logoImages` fields in the [`ad_details`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.adGroupAds#AdGroupAd.FIELDS.oneof_ad_details) Demand Gen [`AdGroupAd`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.adGroupAds#AdGroupAd) resources will no longer be required if default values are assigned to the parent advertiser. If not provided, the ad will inherit the advertiser-level defaults. - The `Business Name` and `Logo Asset IDs` columns in [Ad](https://developers.google.com/display-video/api/structured-data-file/v10/AdGroupAd) SDFs will be able to be set for ads with any of the following types: "Responsive", "Demand Gen Product", "Demand Gen Video", "Demand Gen Image", and "Demand Gen Carousel". If these columns are not set for a relevant ad entry, and default values are assigned to the parent advertiser, the ad will inherit the advertiser-level defaults upon saving. - The `Business Name` and `Logo Asset IDs` columns in [Ad](https://developers.google.com/display-video/api/structured-data-file/v10/AdGroupAd) SDFs are no longer required for Demand Gen ads if its parent advertiser has assigned default values. If default values are set at the advertiser level, all ads under that advertiser will have an assigned business name and logo value. If you want to leave the business name and logo asset values unset for YouTube responsive ads, **do not set default values for your advertiser**. |
| Insertion order and campaign targeting management in Display \& Video 360 API and Structured Data Files | February 23, 2026 | 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](https://developers.google.com/display-video/api/structured-data-file/v9-2/InsertionOrder) and [Campaign](https://developers.google.com/display-video/api/structured-data-file/v9-2/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`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.campaigns/listAssignedTargetingOptions) - [`advertisers.campaigns.targetingTypes.assignedTargetingOptions.get`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.campaigns.targetingTypes.assignedTargetingOptions/get) - [`advertisers.campaigns.targetingTypes.assignedTargetingOptions.list`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.campaigns.targetingTypes.assignedTargetingOptions/list) - [`advertisers.insertionOrders.listAssignedTargetingOptions`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.insertionOrders/listAssignedTargetingOptions) - [`advertisers.insertionOrders.targetingTypes.assignedTargetingOptions.create`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.insertionOrders.targetingTypes.assignedTargetingOptions/create) - [`advertisers.insertionOrders.targetingTypes.assignedTargetingOptions.delete`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.insertionOrders.targetingTypes.assignedTargetingOptions/delete) - [`advertisers.insertionOrders.targetingTypes.assignedTargetingOptions.get`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.insertionOrders.targetingTypes.assignedTargetingOptions/get) - [`advertisers.insertionOrders.targetingTypes.assignedTargetingOptions.list`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.insertionOrders.targetingTypes.assignedTargetingOptions/list) - [`advertisers.lineItems.generateDefault`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.lineItems/generateDefault) [Campaign](https://developers.google.com/display-video/api/structured-data-file/v9-2/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](https://developers.google.com/display-video/api/structured-data-file/v9-2/InsertionOrder) 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` |
| Declare whether line items serve EU political ads | September 8, 2025 | 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 [`containsEuPoliticalAds`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.lineItems#LineItem.FIELDS.contains_eu_political_ads) field in the Display \& Video 360 API [`LineItem`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.lineItems#LineItem) resource. You can also make this declaration using new fields in [`advertisers.lineItems.duplicate`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.lineItems/duplicate) and [`advertisers.lineItems.generateDefault`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.lineItems/generateDefault) requests. - Using the `Contains EU Political Ads` column in the SDF v9 [Line Item](https://developers.google.com/display-video/api/structured-data-file/v9/LineItem) 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`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers#Advertiser.FIELDS.contains_eu_political_ads) field in the Display \& Video 360 API [`Advertiser`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers#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 [`containsEuPoliticalAds`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.lineItems#LineItem.FIELDS.contains_eu_political_ads) field in a new [`LineItem`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.lineItems#LineItem) resource when making an [`advertisers.lineItems.create`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.lineItems/create) request. - Set the `containsEuPoliticalAds` field in the request body of any [`advertisers.lineItems.duplicate`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.lineItems/duplicate) and [`advertisers.lineItems.generateDefault`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.lineItems/generateDefault) requests. - Migrate to use Structured Data Files v9 and set the `Contains EU Political Ads` column for any new line items to `Yes` or `No` on upload. *See our [v9 migration guide](https://developers.google.com/display-video/api/structured-data-file/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. |
| Content Category settings for YouTube \& partners Line Items | June 12, 2025 | 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](https://support.google.com/displayvideo/answer/15968266). 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 [`contentCategory`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.lineItems#YoutubeAndPartnersSettings.FIELDS.content_category) field in [`YoutubeAndPartnersSettings`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.lineItems#YoutubeAndPartnersSettings) objects of YouTube \& partners [`LineItem`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.lineItems#LineItem) resources will no longer be updated. It will be removed entirely at a later date. - The `TrueView Content Filter` column in [Line Item](https://developers.google.com/display-video/api/structured-data-file/v8-1/LineItem) SDFs will no longer be writable. To avoid any interruption of service: <!-- --> - Retrieve the [`effectiveContentCategory`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.lineItems#YoutubeAndPartnersSettings.FIELDS.effective_content_category) field in place of the [`contentCategory`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.lineItems#YoutubeAndPartnersSettings.FIELDS.content_category) field when reviewing YouTube \& partners line items in the API. - Stop modifying the `TrueView Content Filter` column when updating [SDF line item](https://developers.google.com/display-video/api/structured-data-file/v8-1/LineItem) entries. Keep the column empty when creating new line items. |
| Line item budget updates with insertion order optimization | June 12, 2025 | 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 [`InsertionOrder`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.insertionOrders#InsertionOrder) has either [`bidStrategy.maximizeSpendAutoBid`]() or [`bidStrategy.performanceGoalAutoBid`]() set. If so, don't attempt to update the [`LineItem`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.lineItems#LineItem) budget field using [`advertisers.lineItems.patch`](https://developers.google.com/display-video/api/reference/rest/v4/advertisers.lineItems/patch). - In SDF: Check if the SDF entry for the line item's parent [insertion order](https://developers.google.com/display-video/api/structured-data-file/v8-1/InsertionOrder) has its `Insertion Order Optimization` column set to `TRUE`. If so, don't attempt to update the `Budget Type` or `Budget Amount` columns for the [line item](https://developers.google.com/display-video/api/structured-data-file/v8-1/LineItem) SDF entry. |
| Site restrictions for Structured Data Files | June 12, 2025 | 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 to `Site Targeting - Include` and `Site Targeting - Exclude` columns in [Insertion Order](https://developers.google.com/display-video/api/structured-data-file/v8-1/InsertionOrder) and [Line Item](https://developers.google.com/display-video/api/structured-data-file/v8-1/LineItem) files. |
| "Bid Multipliers" column in Line Item Structured Data Files | May 1, 2025 | On May 1, 2025, entries in [Line Item](https://developers.google.com/display-video/api/structured-data-file/v8/LineItem) Structured Data Files that attempt to set the "Bid Multipliers" column will fail to create or update resource on file upload. |
| Require video partner inventory source for Demand Gen Line items in Structured Data Files | April 22, 2025 | Starting April 22, 2025, you will be required to include the value "Video Partners" in the `TrueView Inventory Source Targeting` column of [line item](https://developers.google.com/display-video/api/structured-data-file/v8-1/LineItem) 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](https://developers.google.com/display-video/api/structured-data-file/v8-1/AdGroup) columns `Demand Gen Inventory Source Strategy` and `Demand Gen Enabled Inventory Sources`. |
| Video action campaigns in Structured Data Files | April 22, 2025 | 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](https://support.google.com/displayvideo/answer/16062960). [Line item](https://developers.google.com/display-video/api/structured-data-file/v8-1/LineItem) 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. |
| Infinite [membership duration](https://developers.google.com/display-video/api/reference/rest/v3/firstAndThirdPartyAudiences#FirstAndThirdPartyAudience.FIELDS.membership_duration_days) for first-party audiences | April 7, 2025 | On April 7, 2025, `FirstAndThirdPartyAudience` resources will no longer allow infinite audience membership duration. [`firstAndThirdPartyAudiences.create`](https://developers.google.com/display-video/api/reference/rest/v3/firstAndThirdPartyAudiences/create) and [`firstAndThirdPartyAudiences.patch`](https://developers.google.com/display-video/api/reference/rest/v3/firstAndThirdPartyAudiences/patch) requests setting the [`membershipDurationDays`](https://developers.google.com/display-video/api/reference/rest/v3/firstAndThirdPartyAudiences#FirstAndThirdPartyAudience.FIELDS.membership_duration_days) field value to 10,000 will return a `400` error. Existing audiences with a [`membershipDurationDays`](https://developers.google.com/display-video/api/reference/rest/v3/firstAndThirdPartyAudiences#FirstAndThirdPartyAudience.FIELDS.membership_duration_days) 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 [`membershipDurationDays`](https://developers.google.com/display-video/api/reference/rest/v3/firstAndThirdPartyAudiences#FirstAndThirdPartyAudience.FIELDS.membership_duration_days) field value of new or existing audiences to 10,000. - Refresh the memberships of your existing Customer Match audiences using [`firstAndThirdPartyAudiences.editCustomerMatchMembers`](https://developers.google.com/display-video/api/reference/rest/v3/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`](https://developers.google.com/display-video/api/reference/rest/v4/firstPartyAndPartnerAudiences#FirstPartyAndPartnerAudience) resources. |
| Mismatched custom bidding algorithm and floodlight activities | April 1, 2025 | On April 1, 2025: - [`advertisers.lineItems.create`](https://developers.google.com/display-video/api/reference/rest/v3/advertisers.lineItems/create) requests attempting to set the [`floodlightActivityConfigs`](https://developers.google.com/display-video/api/reference/rest/v3/advertisers.lineItems#ConversionCountingConfig.FIELDS.floodlight_activity_configs) field of the [`ConversionCountingConfig`](https://developers.google.com/display-video/api/reference/rest/v3/advertisers.lineItems#ConversionCountingConfig) object and the `customBiddingAlgorithmId` field of [`MaximizeSpendBidStrategy`](https://developers.google.com/display-video/api/reference/rest/v3/BiddingStrategy#MaximizeSpendBidStrategy.FIELDS.custom_bidding_algorithm_id) or [`PerformanceGoalBidStrategy`](https://developers.google.com/display-video/api/reference/rest/v3/BiddingStrategy#PerformanceGoalBidStrategy.FIELDS.custom_bidding_algorithm_id) objects that don't use matching floodlight activities will return a `400` error. - [`advertisers.lineItems.patch`](https://developers.google.com/display-video/api/reference/rest/v3/advertisers.lineItems/patch) requests attempting to update the [`floodlightActivityConfigs`](https://developers.google.com/display-video/api/reference/rest/v3/advertisers.lineItems#ConversionCountingConfig.FIELDS.floodlight_activity_configs) field of the [`ConversionCountingConfig`](https://developers.google.com/display-video/api/reference/rest/v3/advertisers.lineItems#ConversionCountingConfig) object while the `customBiddingAlgorithmId` field of [`MaximizeSpendBidStrategy`](https://developers.google.com/display-video/api/reference/rest/v3/BiddingStrategy#MaximizeSpendBidStrategy.FIELDS.custom_bidding_algorithm_id) or [`PerformanceGoalBidStrategy`](https://developers.google.com/display-video/api/reference/rest/v3/BiddingStrategy#PerformanceGoalBidStrategy.FIELDS.custom_bidding_algorithm_id) objects is set will return a `400` error. - Entries in [Line Item](https://developers.google.com/display-video/api/structured-data-file/v8/LineItem) 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`](https://developers.google.com/display-video/api/reference/rest/v3/customBiddingAlgorithms/patch), [`customBiddingAlgorithms.rules.create`](https://developers.google.com/display-video/api/reference/rest/v3/customBiddingAlgorithms.rules/create), [`customBiddingAlgorithms.scripts.create`](https://developers.google.com/display-video/api/reference/rest/v3/customBiddingAlgorithms.scripts/create) requests for [`CustomBiddingAlgorithm`](https://developers.google.com/display-video/api/reference/rest/v3/customBiddingAlgorithms#CustomBiddingAlgorithm) resources 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](https://developers.google.com/display-video/api/deprecations-archive).