Google moves Demand Gen Display opt-out to ad groups from the week of 1 December 2026

Google will stop accepting a campaign-level Display opt-out for Demand Gen campaigns from the week of 1 December 2026. In a Google Ads Developer Blog post dated 9 November 2026, Mattia Tommasone of the Google Ads API team said that the campaign field network_settings.target_content_network will default to true for new Demand Gen campaigns, that setting it to false will return an OPERATION_NOT_PERMITTED_FOR_CONTEXT error, and that Display reach will be controlled only at ad group level through channel controls. Existing campaigns that opted out of Display at campaign level will be backfilled automatically, and Google says none of them will change how they serve.

The change matters most to anyone who builds or edits Demand Gen campaigns through the Google Ads API, bulk tools or in-house automation. A creation payload that still sends target_content_network = false will fail once the change lands. Ad groups that were set to serve only on Display inside a campaign that blocked Display will be paused. This article sets out what the Google Ads Developer Blog announcement says, what Google's channel-controls documentation adds, and what it leaves open.

What Google announced on 9 November 2026

According to the 9 November post, Display network targeting in Demand Gen will be "managed directly at the ad group level using channel controls" through the field demand_gen_ad_group_settings.channel_controls.selected_channels.display, together with channel strategies. The campaign-level switch that used to sit above those settings stops being something an advertiser can turn off.

Google gave its reason in one sentence. Until now, disabling Display at campaign level overrode whatever the ad groups said. Moving the decision entirely to the ad group removes that two-level configuration and, in Google's words, ensures "consistent channel representation across the Google Ads API, Google Ads UI, and Google Ads Editor."

The post also states that "overall default campaign serving behavior will remain unchanged." The logic is that the campaign default flips from false to true, but ad group channel controls default to Display off, so a new campaign still targets Google-owned and operated inventory unless someone opts it into Display.

The error developers will see

From the week of 1 December 2026, Google says, setting network_settings.target_content_network to false "during campaign creation or update will result in an OPERATION_NOT_PERMITTED_FOR_CONTEXT error." This applies to both create and update operations. A sync job that rewrites campaign settings on a schedule, and not only a one-off launch script, can therefore start failing.

How the backfill treats existing campaigns

Campaigns currently set to target_content_network = false will be switched to true, and Google will apply automatic changes to their ad groups so that serving stays the same. The post lists four cases. The table below restates them as published.

The fourth row is the one to look for in your own accounts. Google explains that Demand Gen ad groups must target at least one channel. Turning Display off in an ad group whose only channel is Display would leave it with no channels, which is an invalid configuration, so Google pauses it instead. Those ad groups were not serving anyway, because the campaign-level opt-out blocked them. The practical effect is that they will now show as PAUSED, and anyone who later re-enables one will find it serving on Display.

What the channel-controls documentation adds

The 9 November post is short, so it helps to read it next to Google's existing reference material. Google's API guide to Demand Gen channel controls describes three configurations held in a channel_configuration oneof, where an ad group uses either a high-level channel_strategy or granular selected_channels, never both:

• ALL_CHANNELS, which the guide calls the default, serves on every channel Demand Gen supports.
• ALL_OWNED_AND_OPERATED_CHANNELS serves on Google-owned surfaces such as Discover, YouTube, Gmail and Google Maps, and disables third-party channels such as the Google Display Network.
• selected_channels takes boolean flags for youtube_in_stream, youtube_in_feed, youtube_shorts, discover, gmail, display and maps. The guide says to specify every field explicitly when updating selected_channels.

The 9 November post confirms that ALL_OWNED_AND_OPERATED_CHANNELS can be used "as a high-level way to opt out of Display" without listing every channel. Its own JSON example shows an ad group serving only on YouTube Shorts, with display set to false.

A default worth testing yourself

There is one point where the two documents read differently. The channel-controls guide says that if channel_controls is omitted when an ad group is created, it defaults to ALL_CHANNELS, which includes the Display Network. The 9 November post says ad group-level channel controls "default to turning off Display targeting." The documents do not reconcile the two statements. A careful developer should not rely on either default. Set channel_strategy or selected_channels explicitly in every ad group payload, then read the result back with a query.

The Google Ads Help Center article on Demand Gen channel controls describes the same model from the interface side. Channels are set in the ad group settings, under a Channels panel. "All Google channels" selects channels automatically, with the Google Display Network listed as an optional extra. "Let me choose" lets an advertiser pick from YouTube in-stream, in-feed and Shorts, Discover, Gmail, Maps and the Google Display Network. Reporting by channel is available at campaign, ad group and ad level through network segmentation.

Timeline: how Display ended up at ad group level

This is the last step in a move Google has been making for more than a year. Google's Help Center page on the Display Network integration with Demand Gen says channel controls arrived from March 2025, when Google Video Partners inside Demand Gen was renamed Google Display Network and the opt-in moved from campaign to ad group level in the interface. From April 2025, ad groups opted into the Google Display Network with image assets began serving on it.

The same page now carries a notice that Google Display Ads campaigns are moving into Demand Gen. It says eligible advertisers could begin moving existing Display campaigns with a migration tool from June 2026. Later, new campaigns will only be creatable within Demand Gen and remaining eligible campaigns will be migrated automatically. The page gives no date for that later step.

The 9 November change closes the gap left over from that history. The interface already treated Display as an ad group choice. The API still let a campaign-level flag override it. From December, the API follows the interface.

What the announcement does not say

Several details are missing from the post, and they are worth naming so nobody fills them in by assumption:

• No exact day. Google says "the week of December 1, 2026." 1 December 2026 is a Tuesday, so the week starts on Monday 30 November, in the run-up to the December retail peak.
• No API version. The post does not tie the change to a Google Ads API release, which suggests it applies across versions, but Google does not say so directly.
• No list of affected accounts. Google does not say how many campaigns or ad groups the backfill will touch, and it does not say whether advertisers will be notified in the interface.
• No performance claims. The post is about configuration, not results, and it makes no statement about how Display affects Demand Gen performance.

What to check in your own account before 30 November

Google's recommended actions are to review campaign creation payloads and to audit ad group channel configurations. In practical terms, that means the following checks.

1. Search your code and templates for target_content_network. Any Demand Gen create or update call that sends false needs to stop doing so. Move the Display decision into the ad group's channel_controls instead.
2. Run Google's audit query. The post supplies a GAQL query over the ad_group resource, filtered to campaign.advertising_channel_type = 'DEMAND_GEN', that returns the campaign-level flag, ad group status, channel_config, channel_strategy and each selected channel. As published, the query is missing a comma after ad_group.status, so add one before running it. It also omits the maps field, which the channel-controls guide includes.
3. List Display-only ad groups in campaigns that block Display. These are the ones Google will pause. Decide now whether they should be deleted, rebuilt with other channels, or kept paused, so that a re-enable in December does not surprise anyone.
4. Check ALL_CHANNELS ad groups in opted-out campaigns. Google will switch them to ALL_OWNED_AND_OPERATED_CHANNELS. If your reports or rules filter by channel strategy, update them.
5. Brief whoever uses Google Ads Editor. Google names Editor as one of the surfaces this change aligns. Staff who habitually untick Display at campaign level will need to do it in the ad group instead.
6. Watch the new blog address. On 10 November Google said the Developer Blog moves from Blogger to developers.google.com/ads/blog from 11 November 2026, with a new RSS feed at developers.google.com/ads/blog/rss.xml. Google says all new posts will be published only on the new site, and the old feed no longer receives updates after 10 November.

RA has covered several recent Demand Gen changes, including Google's help page saying performance-based cost adjustments now run up to 60 days, and seasonality adjustments being extended to Demand Gen. This change is different in kind. It is a configuration rule, not a bidding feature, and it can break automation that worked last month. For teams running YouTube and Demand Gen at scale, it belongs in the pre-December checklist next to budget and creative reviews. Our YouTube advertising service covers Demand Gen as part of video planning.

What this means for Thai marketers

Google's post does not mention any country, and the change is described as an API and product rule, so the reasonable reading is that it applies to Demand Gen campaigns in every market, Thailand included. That is an inference from the wording, not something Google stated about Thailand.

The groups most likely to be affected are those with automated campaign builds: agencies and in-house teams that launch Demand Gen from templates, feed-driven scripts or third-party platforms. A Thai retailer that clones a December campaign from last year's template could hit the OPERATION_NOT_PERMITTED_FOR_CONTEXT error on launch day if the template carries the old false flag. Teams that only work in the Google Ads interface are less exposed, since the interface already handles Display at ad group level.

The timing is the real risk. The week of 30 November falls just before December promotions and year-end campaigns. A failed launch or an ad group that is unexpectedly paused costs more in that window than in a quiet month. Running the audit query now and fixing templates before the change lands takes little effort. If you want help with that review, our Google Ads management team can go through Demand Gen setups with you.

Frequently asked questions

When does the Demand Gen Display change take effect?

Google says it starts the week of 1 December 2026, which begins on Monday 30 November. The 9 November Developer Blog post gives no exact day within that week.

Can I still opt a Demand Gen campaign out of Display?

Yes, but only at ad group level. Set selected_channels.display to false, or use the ALL_OWNED_AND_OPERATED_CHANNELS strategy, in each ad group. Setting target_content_network to false at campaign level will return an error.

Will my existing campaigns start serving on Display?

Google says no. Campaigns that opted out of Display will be backfilled with ad group changes, and Google states that none of them will change serving behavior. Display-only ad groups in those campaigns will be paused rather than switched on.

Do I need to do anything if I only use the Google Ads interface?

Probably very little, because the interface already sets Display per ad group. You should still check for Display-only ad groups that Google may pause. If anyone on your team uses Google Ads Editor or the API, review those workflows too.

Which API version is affected?

The source does not say. Google's post names no Google Ads API version, so treat the change as applying to any integration that writes the campaign-level field until Google says otherwise.

Display inventory is moving into Demand Gen alongside YouTube, so the channel settings in each ad group now decide where these campaigns serve. If you would like a second pair of eyes on your channel controls before December, talk to Relevant Audience.