Demand Gen display targeting moves to the ad group starting the week of December 1, 2026. Google Ads removes the campaign level Display switch, so whether a Demand Gen campaign serves on the Google Display Network is decided only by the channel controls of each ad group. Default serving does not change.
Demand Gen display targeting is the choice of whether Demand Gen ads serve on the Google Display Network, the network of third party sites and apps that Google sells ads on. The short recommendation from this Google Ads hub explainer: audit the Display setting of every Demand Gen ad group, find the ad groups Google pauses, and remove the campaign level Display flag from any API payload before December 1. A Demand Gen campaign is a Google Ads campaign type that serves image and video ads on YouTube, Discover, Gmail, Maps and the Google Display Network, according to Google's Demand Gen help page.
What changes for demand gen display targeting on December 1, 2026?
Demand gen display targeting loses its campaign level switch starting the week of December 1, 2026. The campaign setting for Display defaults to on for new Demand Gen campaigns and can no longer be turned off. Display reach is then set only per ad group, and Google says default serving behavior stays the same.
The facts come from two places, and they carry different weight.
- Officially confirmed. The Google Ads Developer Blog post of November 9, 2026 by Mattia Tommasone of the Google Ads API team announces the change. Google says it ensures "consistent channel representation across the Google Ads API, Google Ads UI, and Google Ads Editor."
- Reported. PPC Land reported the change on November 9, 2026 and placed it in the wider move of Display into Demand Gen. It quotes Google: "Managing Display targeting exclusively at the ad group level eliminates this dual-level configuration."
- Open. As of November 2026, Google has not said whether advertisers get a notification when ad groups are paused by the backfill. PPC Land flags this as unanswered.
The change fits a longer trend. Google is also moving standalone Display campaigns into Demand Gen, with a migration tool that eligible advertisers could start using in June 2026, per Google's GDN integration help page.
Where do you control Display in a Demand Gen campaign now?
Display in a Demand Gen campaign is controlled in the ad group's channel controls from the week of December 1, 2026. Channel controls are the ad group setting that picks the Google surfaces an ad group serves on. They sit in the "Channels" panel of the ad group settings and, in the API, under demand_gen_ad_group_settings.
Google's channel controls help page describes two options in the interface:
- "All Google channels" uses all channels and inventory, with an option to include the Google Display Network. Google recommends this for most advertisers.
- "Let me choose" lets you tick channels one by one: YouTube in-stream, YouTube in-feed, YouTube Shorts, Discover, Gmail, Maps and Google Display Network.
The API channel controls guide mirrors this with a choice between a channel strategy and selected channels, never both. ALL_CHANNELS delivers on every channel Demand Gen supports. ALL_OWNED_AND_OPERATED_CHANNELS serves on Google owned channels such as YouTube, Discover, Gmail and Maps, and disables "channels operated by third parties, such as the Google Display Network." Selected channels uses seven true or false flags, one of them named display.
What happens to campaigns that had Display turned off?
Demand Gen campaigns that had Display turned off at campaign level are backfilled by Google: the campaign flag moves to on, and each ad group is adjusted so that it still does not serve on Display. Google states that none of the backfilled campaigns change their serving behavior. What changes is where the opt out lives.
The developer blog lists four cases. Campaigns that already had Display on at campaign level are not part of the backfill.
| Ad group setting before | What Google changes | Serves on Display after |
|---|---|---|
| Display already off at campaign and ad group level | Nothing (no-op) | No |
| Channel strategy ALL_CHANNELS | Strategy becomes ALL_OWNED_AND_OPERATED_CHANNELS | No |
| Selected channels with Display plus other channels | Display set to false, other channels kept | No |
| Selected channels with Display only | Ad group status set to PAUSED | No (paused) |
The pause rule follows from one constraint that PPC Land quotes from Google: "Demand Gen ad groups must target at least one channel." A Display only ad group with Display removed would have no channel left, so Google pauses it instead.
Will Display start serving on your Demand Gen campaigns?
Display will not start serving on your Demand Gen campaigns because of the backfill itself, since Google keeps every affected ad group off the Google Display Network. The exposure comes afterward. With the campaign switch on, the only things keeping Display out are the channel settings of each ad group, including the ad groups Google paused.
Google's blog says ad group channel controls "default to turning off Display targeting," which matches the interface, where Display is an extra box to tick under "All Google channels." The API guide reads differently: an ad group created without channel controls defaults to ALL_CHANNELS. PPC Land points out that Google has not explained how that API default behaves once the campaign flag is always on. Treat it as unresolved as of November 2026 and set channel controls explicitly on every ad group you create through the API.
The paused Display only ad groups need the same care. They did not serve on Display before December, because the campaign blocked it. If someone unpauses one after the change, nothing blocks it anymore and it serves on the Display Network.
What do API workflows need to change?
API workflows need to stop sending the campaign level Display flag for Demand Gen campaigns. From the week of December 1, 2026, a create or update request that sets network_settings.target_content_network to false returns an OPERATION_NOT_PERMITTED_FOR_CONTEXT error. The Display decision belongs in the ad group payload instead.
Google's own advice in the blog is short: "Update your application to rely on ad group channel controls." In practice, that means three edits.
- Remove the false value from campaign create and update payloads for the DEMAND_GEN channel type.
- Set channel controls on every ad group. Use channel_strategy ALL_OWNED_AND_OPERATED_CHANNELS to exclude Display without listing channels, or selected_channels with display set to false. The API guide says to specify all fields when updating selected_channels.
- Add the paused status to your sync logic, so a tool that mirrors ad group status does not reactivate Display only ad groups.
The blog ships a GAQL audit query, but PPC Land notes that the published version misses a comma after ad_group.status. This version uses the field paths from the API guide:
SELECT
campaign.id,
campaign.network_settings.target_content_network,
ad_group.id,
ad_group.status,
ad_group.demand_gen_ad_group_settings.channel_controls.channel_config,
ad_group.demand_gen_ad_group_settings.channel_controls.channel_strategy,
ad_group.demand_gen_ad_group_settings.channel_controls.selected_channels.display
FROM ad_group
WHERE campaign.advertising_channel_type = 'DEMAND_GEN'
Google names Google Ads Editor among the tools the change aligns, so recheck Demand Gen channel settings in Google Ads Editor after the backfill before you post bulk edits.
How do you audit Demand Gen ad groups for Display before and after the change?
The Display Exposure Check is a five-step audit that shows, per Demand Gen ad group, whether it can serve on the Google Display Network once the campaign switch is gone. Run it once before December 1, 2026 to capture the current state, and once after the backfill to confirm that Google's changes match your intent.
- Export the current state. Run a GAQL query on ad_group, filtered to campaign.advertising_channel_type = 'DEMAND_GEN', that returns campaign.network_settings.target_content_network, ad_group.status and the ad_group.demand_gen_ad_group_settings.channel_controls fields, or download the Demand Gen campaigns and ad groups in Google Ads Editor, and save the file with the date.
- Mark campaigns with Display off. These are the campaigns Google backfills, so their ad groups are the ones that change.
- List Display only ad groups in those campaigns. They are the ones Google pauses, so note them before they disappear into the paused filter.
- Decide per ad group. Use the decision table below to choose whether each ad group should include Display.
- Rerun the export after the backfill. Compare it with the saved file and check every paused ad group and every new ad group.
The decision table is a rule set built on Google's documented behavior, not on measured results.
| If the ad group... | Then | Why |
|---|---|---|
| Was paused by the backfill and Display was never the goal | Remove it or label it "do not enable" | Unpausing it now serves on Display |
| Was paused by the backfill and Display is now wanted | Move its assets to a separate test campaign | Keeps Display spend visible on its own |
| Uses ALL_OWNED_AND_OPERATED_CHANNELS | Leave it | Display stays excluded |
| Is new and created through the API without channel controls | Set the channel strategy explicitly | The API default is ALL_CHANNELS |
| Should reach Display for video only | Tick Display in the video ad group, not the image ad group | Google documents this split per ad group |
How should reporting and naming handle Display per ad group?
Reporting and naming need to follow the ad group once Display becomes a per ad group choice, because the campaign flag no longer shows which Demand Gen campaigns reach the Display Network. PPC Land notes that the campaign field stops separating Display enabled campaigns after December 2026. Network segmentation and ad group names take over.
Google's channel controls page says channel level reporting is available at the campaign, ad group and ad level through network segmentation. Display Network traffic appears as "Google Display Network" in that segment, per the GDN integration page.
Three habits keep the data readable:
- Name ad groups by channel scope, for example with a short "GDN" or "O&O" suffix, so filters and scripts can find Display ad groups without reading settings.
- Annotate the week of December 1, 2026 in your reports, so a change in network mix is not blamed on bids or creatives.
- Judge Display separately. Compare Display Network results with the other channels under one attribution model before you cut or scale Display.
The same idea of setting channels explicitly also applies to Search campaigns, where Google Ads Display Expansion moves to channel prioritization in February 2027.
Common mistakes with demand gen display targeting
The most common mistakes with demand gen display targeting after December 2026 come from assuming the old campaign switch still protects new ad groups, or from reading the backfill as a change in reach. Each mistake below either sends budget to the Display Network without a decision or breaks automated workflows.
- Unpausing a backfilled ad group. Google paused it because it targeted only Display. Once enabled, nothing stops it from serving there. Check the Channels panel first.
- Keeping the campaign flag in API payloads. A false value now returns OPERATION_NOT_PERMITTED_FOR_CONTEXT. Move the setting to ad group channel controls.
- Relying on the API default for new ad groups. The API guide says omitted channel controls default to ALL_CHANNELS. Set the strategy or selected channels on every create call.
- Expecting a performance shift from the backfill. Google says serving behavior does not change for backfilled campaigns. Run the Display Exposure Check, then look elsewhere for the cause of a December swing.
- Running the published audit query as is. It misses a comma and fails. Use a corrected query before you trust its output.
- Confusing this with the Display campaign migration. Migrated Display campaigns arrive in Demand Gen with Google Display Network selected by default, per Google. They are not excluded by this change.
