Google is making several changes to Display & Video 360 (DV360) in October 2026, and some of them could affect existing advertising workflows more than expected.

The company has announced three unversioned updates affecting the Display & Video 360 API and Structured Data Files. Two changes will take effect on October 1, 2026, while another arrives on October 12, 2026.

The biggest shift involves brand safety controls. Google is removing certain targeting exclusions that advertisers and ad-tech platforms may currently rely on. YouTube responsive ads are changing too, with business names and logos becoming required in some situations.

For teams running automated DV360 campaigns, October is not a month to ignore these changes.

Google Is Removing Digital Content Label Exclusions

Starting October 1, advertisers will no longer be able to exclude specific digital content labels through targeting in the Display & Video 360 API.

The change affects TARGETING_TYPE_DIGITAL_CONTENT_LABEL_EXCLUSION options. It also affects values inside the Digital Content Labels - Exclude field used in Line Item Structured Data Files.

This may sound like a developer-only change, but the effect can reach much further. Agencies, ad-tech companies and large advertisers often build campaign rules around automated targeting controls. If those systems currently depend on digital content label exclusions, they may need to be adjusted before the October deadline.

Advertisers using these controls for brand suitability should review how their current workflows handle content filtering. Waiting until the change goes live could create unexpected campaign behavior.

Most Sensitive Category Exclusions Are Going Away Too

Google is making another brand safety adjustment on October 1. Advertisers will no longer be able to exclude most sensitive categories through the existing targeting mechanism.

The change affects TARGETING_TYPE_SENSITIVE_CATEGORY_EXCLUSION options in the API. It also changes valid values used in the Brand Safety Sensitivity Setting and Brand Safety Custom Settings fields inside Structured Data Files.

This matters because some advertisers use sensitive-category exclusions as a routine layer of protection around campaign placement. Those controls may already be buried inside automated systems, agency tools or custom integrations.

The update does not mean that DV360 is removing brand safety altogether. It does mean that some familiar exclusion methods will no longer work the same way. Advertisers should check which controls remain available and make sure their current setup still matches their brand suitability requirements.

YouTube Responsive Ads Will Need Clear Business Identity

Another change arrives on October 12, 2026, this time affecting YouTube responsive ads.

Developers creating or updating these ads will need to provide a business name and logo when those assets have not already been assigned as defaults to the parent advertiser.

The requirement also applies to Ad Structured Data File uploads. That makes the change especially relevant for advertisers that create or update large volumes of YouTube ads through automated systems.

For smaller advertisers, the adjustment may be fairly simple. For platforms managing hundreds or thousands of ads, however, missing business identity information could become an operational problem.

Teams should make sure that valid business names and logo assets are already available inside their workflows before the October 12 deadline.

These DV360 Changes Are Unversioned

One of the most important details in Google’s announcement is that the changes are unversioned.

That means advertisers and developers cannot simply remain on an older API version and postpone the update. Once the changes take effect, existing integrations may be affected automatically.

This creates more urgency for teams using custom DV360 tools. A workflow that works today may start returning different results once Google removes the affected targeting options.

Developers should review their integrations now rather than treating this as a future migration problem.

Advertisers Should Audit DV360 Integrations Before October

The safest approach is to review any system that relies heavily on DV360 automation before October begins.

Advertisers should look closely at integrations that manage digital content exclusions, sensitive-category controls, Structured Data Files and YouTube responsive ad creation.

Business identity assets also deserve attention. If a system creates YouTube responsive ads automatically, it should already know where to pull the advertiser’s business name and logo when those defaults are missing.

This type of audit is not complicated when done early. It becomes much more frustrating when campaigns are already live and an integration suddenly stops behaving as expected.

October 1 and October 12 Are the Dates That Matter

There are two deadlines advertisers need to remember.

The first is October 1, 2026. That is when Google plans to remove support for specific digital content label exclusions and most sensitive-category exclusions through the affected targeting controls.

The second is October 12, 2026. From that date, YouTube responsive ads will need business name and logo information when those assets are not already configured at the advertiser level.

For developers and agencies using DV360 at scale, both dates should already be part of their October planning.

What the DV360 Update Means for Advertisers

Google’s October update is not a major product launch, but it still carries practical consequences.

Brand safety controls are often deeply embedded inside campaign management systems. When Google removes or changes one of those controls, the effect can spread across internal dashboards, automated rules and agency workflows.

The YouTube change points in a slightly different direction. Google is placing more emphasis on clear advertiser identity inside responsive ads, which means businesses need to make sure their branding assets are available at the right level.

For advertisers using DV360 manually, the changes may be manageable. For businesses running large automated advertising operations, the smarter move is to test integrations before October rather than after something breaks.

Sources