Google's October API changes strip exclusion targeting from Display & Video 360
Starting October 1st, advertisers lose the ability to exclude content labels through Google's Display & Video 360 API. Here's what changes and why your existing campaigns may need rebuilding.
The 5-second version
- Google removes content label exclusion targeting from Display & Video 360 API on October 1st, forcing manual campaign adjustments.
- Changes are unversioned, meaning existing integrations break immediately rather than giving you time to migrate to a newer version.
- YouTube responsive ads will face new requirements under the same October rollout.
On October 1st, Google is making three unversioned changes to its Display & Video 360 API that will affect how you target and exclude content in your campaigns. Because these are unversioned, meaning they apply to all existing integrations immediately, advertisers who built content exclusion logic into their systems won't have the luxury of staying on an older API version until they're ready to migrate.
The immediate break: losing content label exclusions
Starting October 1st, you'll no longer be able to use targeting to exclude specific digital content labels through Display & Video 360. This feature let you keep your ads off certain types of content, whether by category, age-appropriateness, or brand safety criteria, through API integrations. Once it's gone, any exclusion logic you built into your ad buying workflow will stop working.
YouTube responsive ads get new rules too
Google is also introducing new requirements for YouTube responsive ads as part of the October rollout. The exact requirements weren't detailed in this announcement, but any business running YouTube ads through Display & Video 360 should expect to adjust their creative setup or targeting when the change goes live.
What you need to do before October 1st
- Audit your Display & Video 360 campaigns and any API integrations you've built to identify where you're using content label exclusions.
- Document your current exclusion rules so you can replicate them using whatever alternative methods Google offers.
- Review your YouTube responsive ads to understand what new requirements apply.
- Test any changes on a small budget before the October 1st deadline to make sure your campaigns still run as intended.
The core problem is timing: unversioned changes don't give you the option to delay until you're ready. If your exclusion logic is built into your API workflow, it will stop working on October 1st whether you've prepared for it or not. Advertisers who wait until after October 1st to respond will find their campaigns running against content they intended to avoid, burning budget without the safety guardrails they'd designed.
Questions owners ask
Will my Display & Video 360 campaigns break on October 1st?
If you're using content label exclusion targeting, yes, Google is removing that option without a phased migration period. Campaigns using that targeting will need to be rebuilt or reconfigured before October 1st to avoid unintended ad placements.
Why is this called an unversioned change instead of a new API version?
Unversioned changes apply to all existing integrations immediately rather than letting you stay on an older version until you're ready to upgrade. It means you can't wait for a convenient migration window, the change happens whether you're ready or not.
What should I do if I'm using content label exclusions right now?
Audit your campaigns and exclusion rules before October 1st. You'll need to either remove those exclusions or find alternative targeting methods to keep your ads away from unwanted content types.
Are there new YouTube responsive ad requirements I need to know about?
Google is introducing new requirements for YouTube responsive ads as part of the same October rollout, but the source doesn't specify what those requirements are. You should check Google's official announcement for the full list of changes.
