Your Structured Data Files will break on if they reference digital content label exclusions or most sensitive category exclusions. Google published the notice on the Ads Developer Blog on , and the changes are unversioned, meaning there is no migration window and no way to avoid them by staying on an older API release.
For teams managing thousands of line items through bulk uploads, this is not a minor deprecation. It is a forced change to brand safety workflows that have been stable for years.
Three Changes, Two Deadlines
The announcement covers three distinct changes. Two land on . The third lands on .
According to PPC Land's analysis, the first October 1 change removes the ability to exclude specific digital content labels through targeting. This affects the TARGETING_TYPE_DIGITAL_CONTENT_LABEL_EXCLUSION endpoint in the API and the Digital Content Labels - Exclude column in Line Item Structured Data Files. If your current SDFs contain values in that column, those uploads will fail or behave unexpectedly after the cutoff.
The second October 1 change is broader. The majority of sensitive categories can no longer be excluded using targeting. The affected surfaces are TARGETING_TYPE_SENSITIVE_CATEGORY_EXCLUSION in the API, plus the Brand Safety Sensitivity Setting and Brand Safety Custom Settings columns in Line Item SDFs. Google's use of majority rather than all is doing real work here; the Announced Deprecations page should clarify which specific categories remain available, but the default assumption should be that your current exclusion lists will need revision.
The third change, effective , requires business name and logo assets for YouTube responsive ads if a default value is not set at the advertiser level. Per Google's deprecation documentation, the Business Name and Logo Asset IDs columns in Ad SDFs become mandatory fields. Uploads that omit them will fail.
Why Unversioned Changes Matter More Than Version Deprecations
Most DV360 API changes arrive attached to a version number. Version 4 reached general availability on March 27, 2025, and v3 sunset on , leaving v4 as the only supported major release. Version numbers give integration teams a migration window: code written against an older version keeps working until that version is retired.
Unversioned changes remove that buffer entirely. They apply to every supported version at once, on the date specified. A team running a stable v4 integration that has not been touched in months will still be affected on October 1 if it writes exclusion targeting through the affected endpoints. The same mechanism applies on the Structured Data Files side, where the changes hit column values rather than API fields.
This matters for forecasting and planning. If your media team has been using sensitive category exclusions to manage brand safety at scale, the October 1 deadline forces a workflow redesign, not just a code update. The question is not whether your developers can update the API calls; it is whether your brand safety strategy can survive without the controls you have been using.
The Brand Safety Workflow Impact
For years, DV360 advertisers have relied on two layers of brand safety control. The first layer is Google's automated filtering, which removes content that no advertiser should run against. The second layer is advertiser-controlled exclusions, which let individual brands opt out of content that is technically brand-safe but not brand-suitable for their specific context.
The October changes compress that second layer. Digital content labels and sensitive categories have been the primary mechanism for advertisers to express nuanced brand suitability preferences at scale. Removing the ability to exclude most of these categories through targeting means advertisers will need to rely more heavily on other controls: keyword exclusions, channel exclusions, third-party verification integrations, or advertiser-level settings that apply across all line items.
Google's brand suitability documentation distinguishes between brand safety (filtering out harmful content) and brand suitability (allowing advertisers to opt in or out of content that some find acceptable while others do not). The October changes appear to shift more of the brand suitability decision-making away from line-item-level targeting and toward advertiser-level defaults or third-party tools.
For CMOs and their teams, this raises a practical question: how much of your current brand safety posture depends on line-item-level exclusions that will no longer be available? If the answer is a lot, you have about 30 days to redesign those workflows.
The YouTube Responsive Ads Requirement
The October 12 change is more straightforward but still operationally significant. YouTube responsive ads will require business name and logo assets if no default is set at the advertiser level. This is a data completeness requirement, not a targeting change, but it will break bulk uploads that omit these fields.
The fix is simple: ensure every advertiser in your DV360 account has default business name and logo values set, or update your SDF templates to include these fields for every ad. The risk is that teams discover the requirement only when uploads start failing, which is why the 30-day notice matters.
What to Do Before October 1
First, audit your current SDFs. Search for any values in the Digital Content Labels - Exclude, Brand Safety Sensitivity Setting, and Brand Safety Custom Settings columns. Document which line items rely on these exclusions and what the exclusions are intended to accomplish.
Second, identify alternative controls. If you have been excluding specific sensitive categories at the line item level, determine whether you can achieve similar outcomes through advertiser-level settings, keyword exclusions, or third-party verification partners. The answer may be no, in which case you need to document the gap and communicate it to stakeholders.
Third, update your YouTube responsive ad templates. Add Business Name and Logo Asset IDs as required fields, or set advertiser-level defaults so the fields become optional.
Fourth, test before the deadline. Run a small batch of updated SDFs through the API in the last week of September to confirm your changes work as expected. Do not wait until October 1 to discover that your assumptions were wrong.
The Larger Pattern
This is not the first time Google has consolidated brand safety controls in DV360. Earlier in 2026, the platform shifted planning and forecasting from cookie-based audience reach to impression volume, reflecting a broader move away from granular, user-level controls toward aggregate, platform-managed optimization.
The October changes fit that pattern. Google is reducing the surface area of advertiser-controlled exclusions, which simplifies the platform's targeting logic but also reduces the precision available to advertisers who have built workflows around those controls.
For marketing leaders, the strategic question is whether your brand safety requirements can be met within the controls Google continues to support, or whether you need to invest in third-party verification and measurement to maintain the level of control you have today. That is not a question your developers can answer. It is a question for your next pipeline review.
