Google removes two DV360 brand safety exclusion controls on 1 October

Google will remove two brand safety exclusion controls from Display & Video 360 on 1 October 2026, and from 12 October 2026 it will require a business name and a logo when YouTube responsive ads are created or updated without advertiser-level defaults already in place. The three changes were set out in a post to the Ads Developer Blog on Thursday 27 August 2026, signed by Trevor Mulchay of the Display & Video 360 API Team, and reported by PPC Land. All three are unversioned. None of them requires migrating to a new API release, and none of them can be avoided by staying on an older one.

What Google announced on 27 August

Google said on 27 August 2026 that three changes to the Display & Video 360 API and to Structured Data Files "will take effect in October 2026" and may affect existing integrations. The post did not carry the full detail. Google pointed developers to the platform's Announced Deprecations page for that, which is a small procedural fact with a large practical consequence: the announcement alone is not enough to plan the work, and the page it points to is the document an integration owner has to read.

Two of the three changes land on 1 October 2026 and both concern exclusion targeting at the line item layer. The third lands on 12 October 2026 and concerns creative uploads. Structured Data Files, usually shortened to SDF, are comma-separated files used to create and update campaigns, insertion orders, line items and ads in bulk. Agencies and in-house teams that manage thousands of line items lean on them because the alternative is editing each object by hand in the interface, so a change to accepted column values is not an abstraction for those teams. It is the file that either uploads on Thursday or does not.

Why unversioned changes remove the safety net

Most Display & Video 360 API changes arrive attached to a version. Version 4 reached general availability on 27 March 2025, and version 3 sunset on 7 October 2025, which left v4 as the only supported major release. Version numbers exist to give integration teams a migration window: code written against an older release keeps working until that release is retired, and the retirement date is published well in advance.

Unversioned changes work differently. They apply to every supported version at once, on the date specified. A team running a stable v4 integration that nobody has touched in months is still affected on 1 October 2026 if that integration writes exclusion targeting through the affected endpoints. There is no pin to hold, no older release to sit on, and no staged rollout to wait out. The same mechanism applies on the Structured Data Files side, except that there the change hits accepted column values rather than API fields, so the thing that breaks is a file upload rather than a request body.

This is the single most important sentence in the announcement for anyone who owns a DV360 integration, and it is easy to skim past. The absence of a version bump reads like a minor housekeeping notice. It is the opposite: a version bump would have given a migration window, and its absence is what removes one.

The two removals that land on 1 October

Digital content labels can no longer be excluded

From 1 October 2026, specific digital content labels can no longer be excluded through targeting. On the API side that affects the options available under TARGETING_TYPE_DIGITAL_CONTENT_LABEL_EXCLUSION. On the Structured Data Files side it affects the accepted values for the Digital Content Labels - Exclude column in Line Item SDFs. Both surfaces sit at the line item layer, which is where most day-to-day campaign configuration happens rather than somewhere buried in advertiser settings.

Most sensitive categories can no longer be excluded either

From the same date, Google said the majority of sensitive categories can no longer be excluded using targeting. The affected surface is TARGETING_TYPE_SENSITIVE_CATEGORY_EXCLUSION in the API, plus the Brand Safety Sensitivity Setting and Brand Safety Custom Settings columns in Line Item SDFs. The word "majority" is carrying real weight in that sentence, because Google does not enumerate in the announcement which sensitive categories remain excludable and which do not.

That omission is the operationally awkward part. A team whose code validates SDF column values against a hard-coded list of accepted categories cannot tell, from the announcement alone, which entries in that list will still pass on 1 October. The Announced Deprecations page is the only route to establishing what survives, and until someone on the team reads it and diffs it against the list in the repository, the exposure is unknown rather than small.

The creative requirement that lands on 12 October

The third change is narrower and purely operational. From 12 October 2026, creating or updating YouTube responsive ads requires a business name and a logo when default values have not already been assigned to the parent advertiser. The affected workflow is the upload of Ad Structured Data Files.

This is the enforcement half of something Google shipped earlier in the year. The July 2026 DV360 API update added default business name and logo values to the Advertiser resource on 23 July 2026, alongside a synthetic content attestation field that arrived ten days before Article 50 of the EU AI Act became applicable on 2 August. Those defaults began life as a convenience: set them once at advertiser level and creatives built without their own values inherit them. From 12 October the convenience becomes a precondition for advertisers that never set them.

Of the three changes this is the easiest to close out, because the fix is a one-time write at advertiser level rather than a redesign of targeting logic. It is also the one most likely to be missed, because nothing in a working creative pipeline signals that advertiser defaults are absent until the upload that needs them fails.

The three changes, with dates and surfaces

The table below lists what Google said changes, where each change lands, and on what date, drawn from the 27 August announcement.

The roadmap said August, so October is an extension

Neither targeting removal is new information to anyone tracking the platform roadmap, but the timing has moved. Google's Q2 2026 roadmap, published in June, put deprecation of legacy digital content labels and sensitive category exclusions at an estimated August 2026, with "Content not yet rated" carved out and no automatic migration offered. That roadmap listed twelve changes across the quarter and identified the brand safety items as the most structurally significant of them.

The enforcement dates published on 27 August land in October, roughly two months later than the roadmap estimate. Teams that planned migration work around an August cutoff received an extension rather than a fresh deadline. That distinction is worth making internally, because the two framings produce different behaviour: an extension invites the work to slip again, whereas a published date with a named endpoint and a named SDF column does not move.

Pre-bid blocking is spend control, not reporting

Google labels URLs using digital content labels and sensitive topic classifiers, and the resulting signals feed Campaign Manager 360, Display & Video 360 and Google Ads alike. On DV360 specifically, sensitive topic classifiers have been usable for two distinct purposes: reporting on what was bought, and blocking before the bid is placed.

The second purpose is the one that makes this more than a cosmetic cleanup. Pre-bid blocking stops money leaving before an impression is bought. Reporting tells you afterwards. Losing a pre-bid control does not simply degrade a dashboard, it removes a spend-control mechanism, and the replacement has to be evaluated on whether it stops the same spend rather than on whether it produces a similar-looking report.

The unwinding started in September 2024, when DV360 phased out digital content labels for YouTube campaigns and pointed advertisers toward inventory mode settings, placement exclusions and keyword exclusions instead. Two years on, the same logic is being applied to display, video, Connected TV and audio line items. Anyone who went through the YouTube version of this in 2024 already knows the shape of the work, and anyone who did not is doing it for the first time on a shorter fuse.

Compliance and suitability are not the same requirement

Google's stated replacement is inventory modes and content themes. Those operate at a different granularity than a checkbox list of labels. Inventory modes bundle suitability into tiers, and the YouTube implementation of that tiering received MRC brand safety accreditation in June 2026 for in-stream and Shorts inventory bought through Google Ads and DV360. That accreditation is a real signal about the tiering, and it is worth reading for what it covers: it validates the tiering, and it does not restore the ability to exclude a named category.

PPC Land makes the point that a financial services advertiser with a contractual prohibition on a defined content type cannot map that prohibition onto a suitability tier without accepting a broader or narrower blocking footprint than the contract specifies. That is the whole problem stated in one sentence. A tier is a judgement about how sensitive the inventory is overall. A contract clause is a named thing that must not appear. Those two objects do not convert into each other cleanly in either direction: pick the tighter tier and you block inventory the contract permits, which costs reach and money; pick the looser tier and you may serve against the named thing the contract forbids, which costs something harder to price.

The inputs are uneven too. Research published in July 2026 found that age ratings were missing for 60% of 4,346 AI companion apps in the app store data buyers rely on, which is a reminder that category-level controls are only as good as the classification feeding them. That was true before this change and remains true after it, but it matters more once the buyer has fewer levers to compensate with.

What an integration owner should check before 1 October

The checks below follow directly from what Google published. They are ordered so the cheapest one comes first.

• Grep the codebase for the two targeting types. Search for TARGETING_TYPE_DIGITAL_CONTENT_LABEL_EXCLUSION and TARGETING_TYPE_SENSITIVE_CATEGORY_EXCLUSION. If neither appears anywhere in the code that writes targeting, the API half of this does not touch the integration.
• Grep the SDF templates for the three column names. Digital Content Labels - Exclude, Brand Safety Sensitivity Setting and Brand Safety Custom Settings. Column headers tend to live in templates and spreadsheet exports rather than in code, so a repository search alone will miss them.
• Find every hard-coded list of accepted category values. This is where the word "majority" bites. Any validation list, enum, dropdown or lookup table that enumerates sensitive categories needs to be diffed against whatever the Announced Deprecations page states survives.
• Confirm that no version pin protects the integration. There is no version to pin to. If someone on the team believes v4 shields them until a v5 migration, that belief needs correcting before 1 October rather than after.
• Set advertiser-level default business name and logo values. Do this for every advertiser that uploads YouTube responsive ads through Ad SDFs, ahead of 12 October 2026.
• Write down what the campaign actually needs to block, and where that requirement comes from. A requirement that came from a contract or a regulator has to be re-expressed against inventory modes and content themes, and someone has to sign off that the new expression is acceptable. A requirement that was set because it seemed prudent can simply be re-evaluated.

What this means for Thai marketers

Most Thai advertisers reach DV360 through a trading desk or an agency seat rather than through their own API integration, so the practical first move is a question rather than a code change. Ask the desk which of the two removals touches the line items running for the brand, whether any exclusion currently applied is there for a compliance reason, and what the desk intends to put in its place from 1 October 2026. A desk that has already read the Announced Deprecations page will answer specifically. One that answers in general reassurance has not done the work yet.

Regulated Thai categories are where this lands hardest. Financial services, insurance, health and alcohol-adjacent advertisers frequently carry blocking requirements written into a client contract or an internal compliance policy, and those requirements are usually phrased as named categories because that is how legal language works. Those are exactly the requirements that a suitability tier cannot express. Getting compliance and media into the same conversation before October is cheaper than discovering the mismatch in an audit afterwards.

There is a measurement consequence as well. If blocking coverage changes on 1 October, the inventory mix changes with it, and so does the cost profile. Anyone comparing October performance against September should annotate the change rather than read the delta as a creative or bidding effect. Teams that run DV360 alongside Google Ads campaigns and paid social should note that this change is DV360-specific, so a shift visible only in DV360 line items has a plausible structural explanation while the same shift in social campaigns does not. Clean annotation in analytics is what keeps that distinction legible three months later, which is one more argument for having reporting in order before the date rather than after, whether that sits in a warehouse or in a well-configured GA4 property. And for brands whose suitability concerns are really about the environment their message appears in, owned channels remain the one surface where the adjacency is fully controlled, which is part of the ongoing case for content marketing alongside bought media.

What the announcement does not say

Three things are unknown, and pretending otherwise would be worse than saying so.

First, which sensitive categories remain excludable. Google said "the majority" cannot be excluded and did not enumerate the remainder in the post. Second, whether anything migrates automatically. The Q2 2026 roadmap stated that no automatic migration was offered for these deprecations, and the 27 August post does not describe a migration path either. Third, and most useful to an integration owner, the failure mode. The post does not say whether a write that includes a removed exclusion value errors out, or whether it is accepted and silently ignored. Those two outcomes require completely different responses: an error is loud and self-reporting, while a silent no-op means a campaign runs for weeks believing it has protection it does not have. Until that is established, treat the silent case as the planning assumption and verify blocking behaviour directly after 1 October rather than trusting that the configuration still means what it used to mean.

Frequently asked questions

Does staying on Display & Video 360 API v4 protect an integration from these changes?

No. All three changes are unversioned, which means they apply to every supported version at once on the date specified. Version 4 has been the only supported major release since v3 sunset on 7 October 2025, so there is no older version to fall back to and no newer one to delay migrating into.

Which sensitive categories can still be excluded after 1 October 2026?

Google did not enumerate them in the 27 August announcement, saying only that the majority can no longer be excluded using targeting. The Announced Deprecations page for the platform is where Google said the full detail lives, and that page is the only reliable source for validating a hard-coded list of category values before the date.

What replaces digital content label and sensitive category exclusions?

Google's stated replacement is inventory modes and content themes. Inventory modes bundle suitability into tiers rather than exposing a checkbox list of named categories, and the YouTube implementation of that tiering received MRC brand safety accreditation in June 2026 for in-stream and Shorts inventory bought through Google Ads and DV360. The accreditation covers the tiering and does not restore named-category exclusion.

What happens on 12 October 2026 to YouTube responsive ads?

From 12 October 2026, creating or updating YouTube responsive ads requires a business name and a logo when default values have not already been assigned to the parent advertiser, and the affected workflow is the upload of Ad Structured Data Files. Setting the advertiser-level defaults that Google added to the Advertiser resource on 23 July 2026 resolves the requirement in advance.

If a DV360 line item is carrying an exclusion that exists because a contract or a compliance policy demanded it, the useful work between now and 1 October 2026 is establishing exactly what that requirement is and how it will be expressed afterwards. Talk to the team that runs the buy before the date, not after the first October report.