Starting the week of December 1, 2026, Google will manage Display targeting for Demand Gen campaigns only at the ad group level. If you build or edit campaigns through the Google Ads API, a campaign-level setting you may use today will start returning an error.
What changed
Demand Gen is Google's campaign type across YouTube, Discover, Gmail and Display. Until now, Display could be switched off at two levels: the campaign and the ad group. Google's developer blog says the campaign-level switch overrode the ad group setting. From the week of December 1, Display is controlled through ad group channel controls alone. (Google Ads Developer Blog)
Three details from the post matter most:
- New Demand Gen campaigns that don't specify the setting will default to Display on at the campaign level. Google says overall serving stays the same, because ad groups default to Display off.
- Setting the campaign-level flag to false will return an OPERATION_NOT_PERMITTED_FOR_CONTEXT error, both when creating and updating a campaign.
- Existing campaigns that had Display switched off at campaign level will be switched on at that level. Their ad groups will be adjusted where needed. Google says none of these campaigns will change how they serve, since they were already opted out of Display.
The adjustments are where the real work is. Ad groups using the ALL_CHANNELS strategy move to ALL_OWNED_AND_OPERATED_CHANNELS. Ad groups that target Display alongside other channels get Display set explicitly to false. Ad groups that only targeted Display get paused, because a Demand Gen ad group needs at least one channel. Google says those were already not serving.
What it means for you
Who should care: anyone whose campaigns are created or changed by an API connection, a script, or a third-party tool that sets the campaign-level Display flag. Those workflows will error or behave differently once the change lands.
Also care: if you have a Demand Gen ad group that only ever targeted Display, the backfill will pause it. It wasn't serving before, but a paused ad group is easy to forget, so check whether you meant to keep it.
Who can ignore it: if you manage Demand Gen by hand in the Google Ads interface and haven't touched Display settings, Google says serving doesn't change for you.
Cost of doing nothing: a broken API job, a campaign launch that fails, or an ad group you expected to be live sitting paused. The post doesn't say whether the backfill runs on the same day as the new default or later, so don't assume you have extra time.
What to do
- If you use the API or a tool that builds campaigns, search your code and settings for network_settings.target_content_network on Demand Gen campaigns. Replace it with the ad group setting channel_controls.selected_channels.display.
- Run the audit query in Google's post against your Demand Gen ad groups. It pulls the campaign flag, the channel strategy, and each channel setting, so you can see what is actually switched on.
- Look for paused ad groups that only targeted Display, and decide whether they should stay paused.
- If you only use the Google Ads interface and haven't changed Display settings, there's nothing you need to change. A quick look at your Demand Gen ad groups before December 1 is still worth it.
Google's post gives API examples, not interface menu paths. I can't give you exact clicks for the interface, and Google hasn't published any here.
If you'd like Pebble to check your Demand Gen ad groups before December 1, a free scan will show whether any of this touches your account.
Scan my site