What’s changing?

As announced last year, Google will stop serving political advertising in the European Union (EU) ahead of new regulation in October 2025. Starting September 8, 2025, the Display & Video 360 API and Structured Data Files (SDFs) will roll out enforcements related to this change. If you use either of these products to create or manage line items, you may need to update your application to handle these enforcements before September 8, 2025 to avoid an interruption of service.

Background

Starting September 8, 2025, Display & Video 360 will require self-declaration for EU political ads. You must declare whether a line item will serve EU political ads when creating it.

You can also make this declaration for the advertiser as a whole. This declaration will state whether any line items under the advertiser will serve EU political ads. Make the declaration at the advertiser level using the Display & Video 360 API or under the advertiser Basic details settings in the Display & Video 360 UI once it launches after September 8. If you declare that your advertiser won’t serve EU political ads, new line items under that advertiser will use that declaration if another isn’t provided, avoiding an interruption of service.

Display & Video 360 API and Structured Data Files have added support for declaring whether a line item serves EU political ads. Similar support for self-declaration will launch in the Display & Video 360 UI starting September 8, 2025.

Display & Video 360 API

In the Display & Video 360 API, the field containsEuPoliticalAds has been added to the following API objects in v3 and v4 to surface self-declaration at different resource levels:

• LineItem objects for getting and setting the declaration at the line item level.
• Advertiser for getting and setting the declaration at the advertiser level.

The possible settable values for the field are shown in the table below, with a meaning relevant to the resource to which it is assigned.

Value	Meaning
CONTAINS_EU_POLITICAL_ADVERTISING	The resource will be used to serve EU political ads.
DOES_NOT_CONTAIN_EU_POLITICAL_ADVERTISING	The resource will not be used to serve EU political ads.

Starting September 8, 2025, Display & Video 360 API will start requiring that the containsEuPoliticalAds field is set for new line item resources or for existing line item resources when updating geography targeting of existing line items.

What do I need to do?

Every new line item created will need a valid declaration using the field containsEuPoliticalAds.

Set the containsEuPoliticalAds field in the Advertiser object using the advertisers.patch method, or set the declaration under the advertiser Basic details settings in the Display & Video 360 UI once it is available. If you set the containsEuPoliticalAds field to DOES_NOT_CONTAIN_EU_POLITICAL_ADVERTISING for the parent advertiser, new line items will use that value unless another value is set at creation, and the field will be backfilled for existing line items within a day. This field can then be updated using either the UI, API, or Structured Data Files.

If your advertiser is not serving EU political ads, declaring at the advertiser level will be a sufficient action to avoid errors. If you can’t declare at the advertiser level or have declared that EU political ads may be served under your advertiser, you must update your use of the following API methods:

• Set the containsEuPoliticalAds field in the new line item resource when making an advertisers.lineItems.create request.
• Set the containsEuPoliticalAds field in the request body when making advertisers.lineItems.duplicate and advertisers.lineItems.generateDefault requests.
• Set the containsEuPoliticalAds field in existing line item resources using an advertisers.lineItems.patch request before updating geography targeting for those line items. Geography targeting includes the following targeting types:
  • TARGETING_TYPE_GEO_REGION
  • TARGETING_TYPE_POI
  • TARGETING_TYPE_BUSINESS_CHAIN
  • TARGETING_TYPE_REGIONAL_LOCATION_LIST
  • TARGETING_TYPE_PROXIMITY_LOCATION_LIST

Structured Data Files

In Structured Data Files, we have launched v9, which adds the column Contains EU Political Ads to the line item file. This allows for the retrieval and setting of EU political ads declaration at the line item level. This column uses the values YES and NO to represent the line item declaration.

With this launch, we are also deprecating SDF v7.1, v8, and v8.1 and recommend that you migrate to v9 your earliest convenience. We will support these versions until we sunset them in March 2026.

Starting September 8, 2025, Display & Video 360 will start requiring you to use v9 to upload Structured Data Files and set the Contains EU Political Ads column to YES or NO for new SDF line item entries. If your advertiser has declared that it will not serve EU political ads, you can continue to use previous versions to upload SDFs.

What do I need to do?

Every new line item created will need a valid declaration using the column Contains EU Political Ads.

Set the containsEuPoliticalAds field in the advertiser using the Display & Video 360 API advertisers.patch method, or set the declaration under the advertiser Basic details settings in the Display & Video 360 UI once it is available. If you declare that the advertiser will not serve EU political ads, new line items will use the NO value for the Contains EU Political Ads column unless another value is set at creation, and the field will be backfilled for existing line items within a day. This enables you to use v7, v7.1, v8, or v8.1 for SDF upload. After line item creation, this field can be updated using the UI, API, or Structured Data Files.

If you can’t declare at the advertiser level or have declared that EU political ads may be served under your advertiser, do the following before September 8, 2025:

• Migrate to using SDF v9. See our migration guide for instructions.
• Set the Contains EU Political Ads column to YES or NO in line item entries on SDF upload when:
  • Creating new line items.
  • Updating any of the following columns of the existing line item:
  • Geography Targeting - Include
  • Geography Targeting - Exclude
  • Geography Regional Location List Targeting - Include
  • Geography Regional Location List Targeting - Exclude
  • Proximity Targeting
  • Proximity Location List Targeting
  • Creating new ad groups with set Geography Targeting columns under the existing line item.
  • Updating the Geography Targeting columns of ad groups under the existing line item.

Also, if you use Structured Data Files at all, make sure to migrate to v9 before all previous versions are sunset in March 2026.

How do I get help?

Reach out to the Display & Video 360 API support channels if you have more questions about this change.

- Trevor Mulchay, Display & Video 360 API Team

Today, we’re announcing the July 2025 update to the Display & Video 360 API. This update includes the following:

• Support for campaign and insertion order targeting in v4, bringing it to parity with v3.
• The ability to retrieve video ad inventory control settings for YouTube & Partners line items.

For more details, see the Display & Video 360 API release notes. Before using these new features, make sure to update your client library to the latest version.

Display & Video 360 API v3 will sunset on October 7, 2025. If you are still using v3, update your integration to use v4 as soon as possible. Follow the steps in our v4 migration guide to migrate.

If you need help with these new features, please contact us using our Display & Video 360 API Technical support contact form.

- Trevor Mulchay, Display & Video 360 API Team

On June 12, 2025, we will be making three changes to the Display & Video 360 API and Structured Data Files (SDFs) to better align with the Display & Video 360 product.

These changes may impact your existing integrations. We have announced these changes on our Announced Deprecations page:

• Content category settings for YouTube & partner campaigns will no longer be modifiable at the line item level.
• Budget for line items under insertion orders using automated bid strategies will no longer be able to be updated using Display & Video 360 API or SDFs.
• SDFs will allow targeting of any properly-formatted URL.

If you believe any of these changes will impact your integrations, follow the recommended actions in the change description.

If you run into any issues or have questions about these changes, please contact us using our Display & Video 360 API Technical support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Today we’re announcing the deprecation of Structured Data Files (SDF) v7. This version will sunset on November 4, 2025.

Migrate to SDF v7.1 or higher before the sunset date to avoid any interruption of service. See the differences between SDF v7 and v7.1 in the v7.1 release notes.

After November 4, 2025, the following changes will apply to all users:

• The default version of partners and advertisers that use v7 will be updated to v7.1.
• sdfdownloadtasks.create requests that use SDF_VERSION_7 in the request body will return a 400 error.

If you run into issues or need help with your migration, please contact us using our new Display & Video 360 API Technical support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Today, we’re announcing the April 2025 update to the Display & Video 360 API. This update includes the following:

• Support for Commerce Grid and Spotify exchanges.
• The ability to retrieve excluded content theme targeting.
• New ruleset settings for rule-based custom bidding algorithms (only available to select partners).

In addition to these new features, This update also includes a fix for a known issue that caused advertisers.list requests to ignore provided orderBy parameters.

For more details, see 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 need help with these new features, please contact us using our new Display & Video 360 API Technical support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Today we’re announcing the general availability of Structured Data Files v8.1. All users can now use SDF v8.1 to upload and download SDFs in the Display & Video 360 UI, and to download SDFs through the Display & Video 360 API.

SDF v8.1 adds support for controlling inventory source settings for Demand Gen ad groups, enforces OMID targeting set at the advertiser level, and renames TrueView Content Filter column to Inventory Mode in “Line Item” and “Insertion Order” files.

In addition to launching SDF v8.1, we are also announcing the following two breaking changes to Structured Data Files that will go into effect on April 22, 2025:

• You will no longer be able to create YouTube video action line items using SDF. Instead, customers should create Demand Gen line items. Any attempted creation of line items using SDF upload with a Subtype column value of “Action” and a Type column value of “TrueView” will fail.
• You will be required to include the value “Video Partners” in the TrueView Inventory Source Targeting column of line items with the 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 control whether ad groups within Demand Gen line items serve on Google Display Network inventory, you will be required to update to SDF v8.1 and set your desired values in the Demand Gen Inventory Source Strategy and Demand Gen Enabled Inventory Sources columns for ad groups. More details on this renaming and inventory expansion can be found in the Display & Video 360 Help Center.

Full details on the changes between v8 and v8.1 can be found in the Structured Data Files release notes. If you are still using v6, v7 or v7.1, you can follow the instructions in our v7 and v8 migration guides.

If you run into issues or need help with this new version, please follow the instructions in our support guide, or contact us using our contact form.

- Trevor Mulchay, Display & Video 360 API Team

Today, we are deprecating Display & Video 360 API v3. We will sunset v3 on October 7, 2025. Please migrate to Display & Video 360 API v4 before the sunset date to avoid an interruption of service.

New features will not be added to v3 now that it is deprecated. All new feature releases will target v4 exclusively. Read our release notes for more information on updates made to the API in v4 and see our GitHub repository for new code samples using v4. Follow the steps in our v4 migration guide to migrate.

If you run into issues or need help with this new version, please follow the instructions in our support guide or contact us using our contact form.

- Trevor Mulchay, Display & Video 360 API Team

We’re pleased to announce that we are promoting Display & Video 360 API v4 from beta to general availability. With v4 entering general availability, it is now our recommended version. Our guides have been updated to reflect v4 features and conventions.

We recommend migrating from v3 to v4 at your earliest convenience, as v3 will be deprecated and sunset in the coming months. See instructions on migrating to v4 in our migration guide and an exhaustive list of changes made in v4 in our February 13, 2025 release notes.

Before trying to call v4, make sure to update your client library to the latest version.

If you run into issues or need help using this new version, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team

In the coming months, we will make changes to the Display & Video 360 API and Structured Data Files to improve API function and better align with the Display & Video 360 product.

These changes may impact your existing integrations. We have announced these changes on our Announced Deprecations page. We recommend you review these individual changes that will take effect on the following dates:

• On February 28, 2025, frequency caps over 30 days will be deprecated for campaign, insertion order, and line item resources.
• On March 6, 2025:
  • Optimized targeting will no longer be available for fixed bidding line items.
  • The default page size of audience list requests will be updated.
  • Requests generating structured data files will throw an error if using mismatched partner and advertiser IDs.
• On April 1, 2025, line items will be required to assign floodlight activities that align with those used in any assigned custom bidding algorithm.
• On May 1, 2025, bid multipliers will be deprecated.

If you believe any of these changes will impact your integrations, follow the recommended actions in the change description.

If you run into any issues or have questions about these changes, please contact us using our new Display & Video 360 API Technical support contact form.
- Trevor Mulchay, Display & Video 360 API Team

We’re pleased to announce that Display & Video 360 API v4 is available in public beta starting today. We’ve also launched an update to the v3, adding new features.

Here is a subset of changes introduced in v4:

• The optimizationObjective field in InsertionOrder resources is now required and must be set when creating new insertion orders.
• You can no longer retrieve and manage Campaign and InsertionOrder resource targeting.
• The FirstAndThirdPartyAudience resource was renamed to FirstPartyAndPartnerAudience.

In addition, we've released an update that adds the following features in both v3 and v4:

• Support for asset-based creatives through the addition of a new CreativeType value and multiple AssetRole values.
• Support for Integral Ad Science quality sync custom segments in third party verifier targeting.
• New GeoRegionType values used to identify geographic region targeting options.

More detailed information about this release can be found in our release notes. Follow the steps in our migration guide to migrate from v3 to v4. Be aware that breaking changes may be made to v4 while in beta, and any such changes will be listed in the Display & Video 360 API release notes.

Before using new v3 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.

- Trevor Mulchay, Display & Video 360 API Team

Starting on April 7, 2025, a new maximum membership duration of 540 days will gradually roll out for Customer Match lists in Google Ads and Display & Video 360 platforms. This change is being made to better align with Customer Match best practices.

From this date, existing lists configured to have no membership expiration set or membership expiration greater than 540 days will be updated to use the maximum membership duration of 540 days, and a membership duration of 540 days will be retroactively applied to all those existing members that have a longer duration. The reflected list size decreases as memberships expire. Campaigns targeting too small a segment of users can’t serve ads and may automatically pause. Refresh your Customer Match list before April 7, 2025 to renew memberships or replace the expired Customer Match lists with up-to-date lists to ensure that your ad campaigns are not interrupted.

With a set membership duration, you will need to start refreshing your list regularly by re-uploading customer data to your lists. If you do not, the list size will get smaller over time. Refer to this article to learn more about Customer Match.

Required actions for Google Ads API users

Starting on April 7, 2025, requests to set the UserList.membership_life_span field in the Google Ads API to greater than 540 will return a RangeError.TOO_HIGH error. We recommend you check your current implementation to make sure you no longer set the field value to greater than 540.

For existing user lists with membership_life_span field in the Google Ads API greater than 540, starting from April 7, 2025 customer data user lists will be automatically migrated to have a membership life span of the maximum 540 days. If you need to update your code to regularly refresh your customer lists, check out our guide for examples.

No action is required if you do not set the membership_life_span field in the Google Ads API and you regularly refresh your customer lists. Leaving the field unset has the same effect as setting it to the maximum 540 days value.

If you run into issues or have questions about these changes, please contact us using our Google Ads API forum.

Required actions for Display & Video 360 API users

Starting on April 7, 2025, firstAndThirdPartyAudiences.create and firstAndThirdPartyAudiences.patch requests to the Display & Video 360 API that set the membershipDurationDays field to greater than 540 will return a 400 error. Setting the membershipDurationDays field is required when you create a Customer Match list, so we recommend that you check your current implementation to make sure you no longer set the field to a value greater than 540.

From April 7, 2025, existing Customer Match list with a membershipDurationDays field set to a value greater than 540 days will be automatically migrated to a membership duration of the new maximum 540 days. After this date, you will need to regularly refresh your Customer Match list. See our guide for examples on how to update your Customer Match list.

If you run into issues or have questions about these changes, please contact us using our Display & Video 360 API Technical support contact form.

- Da Yang, Google Ads API Team
- Trevor Mulchay, Display & Video 360 API Team

Today, we’re announcing the December 2024 update to the Display & Video 360 API. This update includes the following:

• Support for additional exchanges.
• An increased maximum page size of 5000 for firstAndThirdAudiencePartyAudiences.list requests. To optimize quota usage, manually set the pageSize parameter of list requests to the maximum value.

More details 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 need help with these new features, please contact us using our new Display & Video 360 API Technical support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Today we’re announcing the general availability of Structured Data Files (SDF) v8. All users can now use SDF v8 to upload and download SDFs in the Display & Video 360 UI, and to download SDFs through the Display & Video 360 API.

SDF v8 adds support for Demand Gen Line Item, Ad Group, and Ad resources, as well as the companion banner field for YouTube and Demand Gen Ads.

Full details on the changes made in v8 can be found in our Structured Data Files release notes and instructions for migrating from v7.1 to v8 can be found in our migration guide. If you are currently using SDF v6, follow the instructions in our v7 migration guide first before migrating to v8.

If you run into issues or need help with this new version, please follow the instructions on our support guide or contact us using our contact form.

- Trevor Mulchay, Display & Video 360 API Team

Today, we’re announcing the October 2024 update to the Display & Video 360 API. This update adds the following:

• Support for cost-per-view performance goals and the targeting of connected devices.
• The ability to generate and download Structured Data Files (SDFs) using SDF v8. This version is currently in beta and only available to limited partners.
• Additional Adloox brand safety settings under third-party verifier targeting.

In addition, we’ve also officially deprecated the SDF v5.5 enum value given the sunset of v5.5 earlier this month.

More details 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 need help with these new features, please contact us using our new Display & Video 360 API Technical support contact form.

- Trevor Mulchay, Display & Video 360 API Team

If you want all new blog posts sent directly to your inbox, we have good news. The blog includes a customizable RSS feed that you can subscribe to with your favorite RSS service. Just paste the URL above into your RSS service and get the blog contents delivered in whatever way you prefer. If you're new to RSS, check out this community resource on GitHub describing how it works and providing a list of well-supported services.

If you want to filter to specific products that interest you, that's possible too. Here are some quick links to the RSS feeds for the products supported by this blog:

• Google Ads API
• Google Ads scripts
• Ad Manager API
• Authorized Buyers
• Bid Manager API
• DV360 API
• Structured Data Files
• IMA SDK
• Mobile Ads SDK

- Mike Cloonan, Ads DevRel Team

Update: Updated section on changes to YouTube & partners line item content targeting to clarify that targeting of this type will not be able to be assigned directly to YouTube & partners line items, but can be inherited from the parent advertiser.

In the coming months, the following updates to the Display & Video 360 product might impact your integration with the Display & Video 360 API and Structured Data Files:

• On September 30, 2024, directly assigned content targeting will be deprecated for YouTube & partners line items.
• On September 30, 2024, audiences from Oracle will no longer be accessible and removed from existing targeting.
• On September 30, 2024, optimized targeting will no longer be available for line items using a subset of bid strategies.
• On November 5, 2024, “Flight ASAP” pacing configuration will no longer be accepted for insertion orders, and existing insertion orders with this configuration will automatically be updated.

For details on how to prepare for each of these changes, read the rest of this blog post and check the Display & Video 360 API Announced Deprecations page.

Changes to content targeting for YouTube & partners line items

On September 30, 2024, it won’t be possible to directly assign Digital Content Label and Other Content Types exclusion targeting to YouTube & partners line items. Embedded video, live streaming, and Family content rating exclusion will still be available at the advertiser-level, and then will be applied to child YouTube & partners line items only.

In Display & Video 360 API, all TARGETING_TYPE_DIGITAL_CONTENT_LABEL_EXCLUSION and TARGETING_TYPE_SENSITIVE_CATEGORY_EXCLUSION AssignedTargetingOptions will be removed from YouTube & partners line items.

Assigned targeting inherited by YouTube & partners line items are not retrievable at the line item level, so any targeting of these types inherited from the parent advertiser will continue to not be returned. This will impact responses from assigned targeting LIST requests and attempts to retrieve these resources using advertisers.lineItems.targetingTypes.assignedTargetingOptions.get will return a 404 error.

In Structured Data Files, Line Item files will no longer use the following values in the “TrueView Category Exclusions Targeting” column:

• “All Audiences”
• “Younger Teens”
• “Teens”
• “Adults”
• “Not Yet Rated”

Generated files will no longer populate these values in the column. The values “Embedded Videos,” “Live Streaming,” “Games,” and “Families” will be populated in the column when the targeting is inherited from the parent advertiser. Line Item file entries for YouTube & partners line items updating the “TrueView Category Exclusions Targeting” column will fail on upload.

To avoid any interruption of service, remove any impacted targeting from YouTube & partners line items using the UI or Structured Data Files upload.

Sunset of Oracle first- and third-party audiences

On September 30, 2024, first- and third-party audiences sourced from Oracle will sunset. Once sunset, these audiences will be removed from any resource targeting and combined audiences. This update will automatically pause any line items that target only sunset audiences, or negatively target any sunset audiences.

You can identify sunsetting third-party audiences in the UI as third-party audiences from providers “Bluekai”, “Datalogix”, and “AddThis”. If you have an external account link with Oracle to import audiences from their platform, check with your relevant team to identify sunsetting first-party audiences. These audiences can’t be easily identified using the Display & Video 360 API.

In the Display & Video 360 API, TARGETING_TYPE_AUDIENCE_GROUP AssignedTargetingOptions will be updated to remove sunset audiences. Requests to add sunset audiences to resource targeting will return a 400 error.

In Structured Data Files, IDs of sunset audiences will no longer be included in “Audience Targeting - Include” or “Audience Targeting - Exclude” columns in Insertion Order, Line Item, and YouTube Ad Group files, as well as the “Bid Multiplier” column in Line Item files. File entries using sunset audience IDs in these columns will fail on upload.

To avoid any interruption of service, review the audiences used in your resource targeting, identify any Oracle audiences, and remove them. If you cache audience ID, make sure to remove any of these audiences from your cache.

Ineligibility of Optimized Targeting for certain bid strategies

On September 30, 2024, line items using the following bid strategies will no longer be able to use optimized targeting:

• Maximum views with in-view time over 10 seconds
• Maximum completed in-view and audible views
• Maximum viewable impressions
• Target viewable CPM

At this time, line items that use one of these bid strategies combined with optimized targeting will be updated to turn off optimized targeting.

In the Display & Video 360 API, LineItem resources with targetingExpansion.enableOptimizedTargeting set to True and bidStrategy.maximizeSpendAutoBid.performanceGoalType set to BIDDING_STRATEGY_PERFORMANCE_GOAL_TYPE_CIVA, BIDDING_STRATEGY_PERFORMANCE_GOAL_TYPE_IVO_TEN, or BIDDING_STRATEGY_PERFORMANCE_GOAL_TYPE_AV_VIEWED or bidStrategy.performanceGoalAutoBid.performanceGoalType set to BIDDING_STRATEGY_PERFORMANCE_GOAL_TYPE_VIEWABLE_CPM will be updated to set targetingExpansion.enableOptimizedTargeting to False. Requests creating or updating LineItem resources with any of these sunset configurations will return a 400 error.

In Structured Data Files, Line Item file entries with either “Optimized vCPM” in the “Bid Strategy Type” column or a combination of “Maximum” in the “Bid Strategy Type” column and “CIVA”, “IVO_TEN”, or “AV_VIEWED” in the “Bid Strategy Unit” column will be updated, if needed, to set the “Optimized Targeting” column to False. Line Item file entries using the sunset configurations will fail on upload.

To avoid any interruption of service, update and verify that your line items using these bid strategies don’t have optimized targeting turned on.

Sunset of “Flight ASAP” pacing for insertion orders

On November 5, 2024, “Flight ASAP” pacing will sunset for insertion orders. All existing Insertion Orders with “Flight ASAP” pacing will be updated to “Flight Ahead” pacing.

In the Display & Video 360 API, InsertionOrder resources with a pacing.pacingPeriod of PACING_PERIOD_FLIGHT and a pacing.pacingType of PACING_TYPE_ASAP will be updated to use a pacing.pacingType of PACING_TYPE_AHEAD. Requests creating or updating InsertionOrder resources with this configuration will return a 400 error.

In Structured Data Files, Insertion Order file entries with “Flight” and “ASAP” values in “Pacing” and “Pacing Rate” columns, respectively, will be updated to an “Ahead” value in the “Pacing Rate” column. Insertion Order file entries using the sunset configuration will fail on upload.

To avoid any interruption of service, update the pacing of any existing insertion orders currently using the “Flight ASAP” configuration.

If you run into issues or have questions about these changes, please contact us using our new Display & Video 360 API Technical support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Today we’re announcing the promotion of the Structured Data Files (SDF) QA format to general availability.

The SDF QA Format was initially released in open beta on May 30, 2024. The QA format allows you to download SDFs for Line Item and YouTube Ad Group resources that use human-readable values, such as display names, in place of numeric IDs to make it easier to review resource settings in bulk. These QA format files are read-only and can’t be uploaded to modify or create Display & Video 360 resources.

The two new file types using this format are Line Item - QA and YouTube Ad Group - QA and are available in SDF v6 and later. These files can be downloaded in the Display & Video 360 interface or by using Display & Video 360 API v3, by either:

• Using the FILE_TYPE_AD_GROUP_QA or FILE_TYPE_LINE_ITEM_QA FileType values in a ParentEntityFilter
• Providing relevant IDs to new lineItemQaIds and adGroupQaIds fields in an IdFilter

To help you decide whether the SDF QA format is right for you and your integration, we’ve added information and recommendations to the existing Bulk Tools guide.

If you run into issues, please contact us using our new Display & Video 360 API Technical support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Today we’re announcing the deprecation of Structured Data Files (SDF) v6. This version will sunset on April 30, 2025.

Migrate to SDF v7 or higher before the sunset date to avoid any interruption of service. Instructions on how to migrate from v6 to v7 can be found in our migration guide.

After April 30, 2025, the following changes will apply to all users:

• The default version of partners and advertisers using those versions will be updated to v7.
• sdfdownloadtasks.create requests using SDF_VERSION_6 in the request body will return a 400 error.

If you run into issues or need help with your migration, please contact us using our new Display & Video 360 API Technical support contact form.

- Trevor Mulchay, Display & Video 360 API Team

As announced in February 2024, Display & Video 360 API v2 will sunset on September 3, 2024. Please migrate to Display & Video 360 API v3 before the sunset date to avoid an interruption of service.

You can read our release notes for more information about v3. Follow the steps in our v3 migration guide to help you migrate from v2 to v3.

If you run into issues or need help with your migration, please contact us using our new Display & Video 360 API Technical support contact form.

- Trevor Mulchay, Display & Video 360 API Team

On October 31, 2024, Display & Video 360 Entity Read Files (ERFs) will sunset. After this date, new private and public ERFs will not be generated. ERFs were deprecated in June 2021 and the October sunset date was first announced in January 2024.

If you are currently using ERFs to programmatically retrieve Display & Video 360 resource configurations, migrate to the Display & Video 360 API. You can either integrate directly with the Display & Video 360 API using REST requests or automatically import Display & Video 360 resource configurations into BigQuery using the Display & Video 360 API BigQuery Connector.

See our migration guide for more information on migrating to the Display & Video 360 API and the two integration options.

If you have questions or concerns about this migration, please contact us using our new Display & Video 360 API Technical support contact form.

- Trevor Mulchay, Display & Video 360 API Team