Key details

  1. Google developer announcement: November 9, 2026; transition starts the week of December 1, 2026.
  2. Demand Gen campaign-level target_content_network=false will trigger OPERATION_NOT_PERMITTED_FOR_CONTEXT.
  3. Ad-group selected_channels.display or ALL_OWNED_AND_OPERATED_CHANNELS replaces the campaign opt-out.
  4. Google says existing campaign serving is preserved by automatic backfill.
  5. Previously unservable Display-only ad groups are paused.
  6. This differs from October's Google Ads channel prioritisation and February 2027 Search Display Expansion migration.

What builders should take away

  1. Search Google Ads integration code for Demand Gen writes to network_settings.target_content_network=false.
  2. Set Display reach through ad-group channel controls and verify the resulting channel strategy.
  3. Audit existing Demand Gen ad groups after backfill; a campaign-level true flag does not prove Display is serving.
  4. Test create/update calls and error handling around the December rollout.

What changed

Google's November 9, 2026 developer notice says that from the week of December 1, campaign-level Demand Gen Display targeting will default to true, while Display participation is controlled by ad-group channel settings. Setting network_settings.target_content_network=false during campaign creation or update will return OPERATION_NOT_PERMITTED_FOR_CONTEXT. Existing opted-out campaigns will be automatically backfilled to equivalent ad-group channel controls.

Why it matters

Agencies and developers with campaign creation scripts, bulk management pipelines or templates may see previously valid API writes fail. The visible campaign-level true flag is not evidence that Display advertising has been newly enabled: ad-group defaults and backfill preserve existing serving. Auditing only the campaign field risks false alarms and wrong remediation.

The breaking API write

For Demand Gen, do not write network_settings.target_content_network=false. Instead configure demand_gen_ad_group_settings.channel_controls.selected_channels.display=false or use ALL_OWNED_AND_OPERATED_CHANNELS to opt out of Display at the ad-group level. Google documents the exact error OPERATION_NOT_PERMITTED_FOR_CONTEXT for forbidden campaign-level writes. This change is specific to Demand Gen, not a blanket rule for every Google Ads campaign type.

What happens to existing campaigns

Google says campaigns with target_content_network=false are changed to true and their ad groups adjusted to preserve serving. ALL_CHANNELS becomes ALL_OWNED_AND_OPERATED_CHANNELS; selected Display channel flags can be explicitly disabled. Display-only ad groups previously suppressed by campaign-level opt-out become PAUSED rather than accidentally serving. The migration changes configuration representation, not intended reach.

Audit automation and avoid false positives

Search code and saved payloads for target_content_network, then inspect the corresponding Demand Gen ad-group channel controls and strategies. Google supplies a GAQL query listing campaign and ad-group IDs, channel_config, channel_strategy, selected channel flags and status. Test campaign creation and mutation in a controlled account when the change becomes available. Do not infer live delivery or spending effects solely from the campaign-level flag.

What to watch next

  • Actual start and account-by-account completion of the December rollout.
  • Any changed Google Ads API client-library validation or examples.
  • Independent evidence of migration errors or unexpected ad-group status changes.

Still unclear

  • Google says existing serving remains unchanged; no independent account-level backfill audit was performed.
  • Rollout begins the week of December 1, so exact account cutover timing may vary.
  • No verified performance or spend changes are attributable to this configuration migration.

Sources

Direct reading behind this dossier.

2 sources

Discussion

Discussion is reader-contributed. Comments are not part of the BTN dossier or its editorial evidence.

0 visible comments

Join the discussion

Keep comments useful and relevant. Reader contributions may be moderated and are not BTN editorial evidence.

Sign in to comment