Google announced that, beginning the week of Dec 1, 2026, the Ads API will drop the campaign-level setting that disables Display for Demand Gen campaigns. The change forces marketers and agencies to manage Display targeting at the ad-group level, affecting existing and new campaigns.
What happened
Google told developers that, starting the week of Dec 1, 2026, the Google Ads API will stop accepting the campaign-level field that keeps Demand Gen campaigns off the Display Network. The post on the Google Ads Developer Blog by Mattia Tommasone of the API team says any request that tries to set the old field will fail with an error. Existing campaigns will be rewritten automatically. A small group of ad groups will be paused so that none of them changes where it serves.
The API will now default the campaign-level field `network_settings.target_content_network` to true for new campaigns. Display targeting will be governed by the ad-group controls `demand_gen_ad_group_settings.channel_controls.selected_channels.display` and by channel strategies. The default overall serving behavior stays the same, according to the post.
Two linked changes are described. First, the default for new campaigns switches to true. Second, the API will reject any attempt to disable Display for an entire Demand Gen campaign. The error message is `OPERATION_NOT_PERMITTED_FOR_CONTEXT`.
Four automatic updates will be applied to existing campaigns that currently have the campaign-level field set to false:
- No-op ad groups: where Display is off at both levels, only the campaign field changes.
- Channel strategy pushdown: ad groups using the ALL_CHANNELS strategy will move to ALL_OWNED_AND_OPERATED_CHANNELS.
- Channel control pushdown: ad groups that include Display with other channels will have `selected_channels.display` set explicitly to false.
- Unservable corner case: ad groups that target only Display inside a campaign that blocked Display will be paused.
Why it matters
The change removes a dual-level configuration that previously let a campaign-level switch override ad-group settings. Marketers now have to set Display preferences for each ad group, adding granularity but also complexity. Agencies and tool makers that build campaigns via the API will see errors if they still use the old field. Existing campaigns will not start or stop serving on Display, but the automatic rewrites could pause some ad groups that only ran on Display, potentially affecting performance.
The shift aligns the API with the Google Ads UI and Editor, where the ad-group control has already been in place since March 2025. It also standardises channel representation across Google’s advertising stack.
What this means for marketers
Marketers should audit their Demand Gen campaigns before Dec 1. Identify any campaign-level Display opt-outs and plan to replicate the setting at the ad-group level. Update automation scripts to use the new ad-group fields and handle the `OPERATION_NOT_PERMITTED_FOR_CONTEXT` error. Consider using ADFLU’s autonomous SEO and GEO service to keep your search presence strong while you re-configure Display settings. Test the new defaults on a small set of campaigns to confirm that performance remains stable.
"Setting this field during campaign creation or update will result in an OPERATION_NOT_PERMITTED_FOR_CONTEXT error" Google Ads API team post
The bottom line
From Dec 1, 2026 Google will require Display targeting for Demand Gen to be managed at the ad-group level. The API will reject old campaign-level settings and automatically adjust existing campaigns. Marketers need to adjust their workflows, update automation, and verify that paused ad groups are re-enabled where needed to avoid gaps in reach.
Sources
- 1.ppc.land