Demand Gen’s December channel change: what should your agency check?
A business-facing review of the announced move to ad-group Display controls, especially for campaigns created by scripts or integrations.
In this article
A business-facing review of the announced move to ad-group Display controls, especially for campaigns created by scripts or integrations.
Treat the effective date as a preparation window.
Google’s 9 November 2026 developer announcement schedules Demand Gen Display-targeting changes for the week of 1 December 2026. It moves the relevant control to ad groups and says the default serving behaviour remains unchanged. A changed campaign-level default should therefore not be presented to a client as proof that all campaigns will suddenly expand to Display.
This is particularly relevant when software, templates or an agency platform creates campaigns. The practical question is whether the integration expresses the intended channel choice at the level Google will use. This article is a review brief for the owner and implementation team, not a substitute for the current API migration instructions.
Write the intended reach in ordinary language.
For an illustrative education provider, one campaign may be intended for a particular set of Google-owned surfaces, while a different campaign deliberately explores wider reach. Record that intention for each campaign before inspecting technical fields. A setting cannot be judged correct without knowing the business decision it is supposed to represent.
Also distinguish a campaign’s permitted channels from where it has actually served. A screenshot of an enabled option does not demonstrate delivery, while a short reporting period without impressions does not prove that a channel was excluded. Keep configuration evidence and delivery evidence in separate parts of the review.
- List campaigns created manually, through reusable templates and through API integrations.
- Name the owner of the campaign-creation workflow, not just the account manager.
- Record the approved channel intention and the date it was last reviewed.
Ask for a controlled migration check.
Have the technical owner compare current ad-group channel selections with the intended reach, then inspect how the integration creates and updates them. A paused test campaign can help review the payload and the resulting account configuration without turning a software test into an unapproved media-spend experiment.
Google describes transformations for existing opted-out campaigns to preserve their behaviour. Ask the team to verify the resulting state rather than declaring the migration complete solely because a backfill was announced. If an integration encounters errors, its status should remain visible to the operator; a silent retry loop is not a useful control.
Keep performance changes separate from maintenance.
A channel-control migration and a new acquisition experiment answer different questions. Complete and document the maintenance task first. If the business wants to test additional reach, give that decision its own approved scope, creative requirements, measurement plan and review period.
Finish with a short handover: which workflows were checked, which campaigns were reviewed, who can approve future changes and where exceptions are recorded. That is more valuable than a claim that an API change has improved results before any suitable observation exists.
What would this
look like for you?
Choose the channel, offer and campaign handoff your business is ready to support. Explore our digital advertising service, or tell us what you are working on so we can discuss the scope.
Put the thinking into practice.
Sources & further reading
Platform references support the factual background. The planning recommendations are AdzUp’s editorial interpretation.
A useful read.
A clearer next move?
Keep exploring, or bring your questions to AdzUp.

