Google Display Ads to Demand Gen: a migration-governance playbook

Short answer: Treat Google's Display Ads transition into Demand Gen as a governed campaign migration, not a simple naming change. Google says advertisers will be able to manage Google Display Network presence directly through Demand Gen, keep channel controls and still serve exclusively on GDN, with the broader transition expected to complete by 2027. Freeze the current Display setup, map targeting and creative controls, preserve conversion definitions and test migrated cohorts before scaling.

What Google announced

Google's 2026 update says Display Ads are moving toward a unified Demand Gen environment. Advertisers can continue reaching people across the Google Display Network while using Demand Gen controls, and Google says a migration tool will support the transition.

Google also reports an average ROI improvement for advertisers adding GDN inventory to Demand Gen under internal-data conditions.

That figure is a vendor claim, not a guaranteed result for an individual account.

Step 1: freeze the legacy Display baseline

Before migration, document:

• campaign IDs;
• budgets;
• bidding strategies;
• audiences;
• placements;
• content exclusions;
• frequency settings where relevant;
• creative assets;
• responsive-display configuration;
• conversion goals;
• geo/language settings;
• historical spend, conversions and value.

The baseline provides evidence if migrated performance or delivery changes unexpectedly.

Step 2: map network and channel intent

Google says advertisers can continue to serve exclusively on GDN and can use channel controls inside Demand Gen.

Record the intended delivery policy for each migrated campaign:

• GDN only;
• broader Demand Gen surfaces;
• test cohort;
• excluded channels;
• brand-safety constraints;
• market limitations.

Do not let migration silently broaden inventory because the business never documented its network intent.

Step 3: map audience controls

Display campaigns often depend on audience logic accumulated over time.

Review:

• remarketing lists;
• customer lists;
• custom segments;
• demographic constraints where permitted;
• exclusions;
• lookalike/similar-audience replacements where relevant;
• consent and eligibility state.

For every control, record the Demand Gen equivalent, whether migration is automatic and how the result will be verified.

Step 4: reconcile creative assets

Demand Gen supports a different creative environment from legacy Display.

Inventory:

• images;
• logos;
• videos;
• copy;
• aspect ratios;
• brand guidelines;
• required disclaimers;
• landing destinations.

Mark assets as:

• reusable;
• needs adaptation;
• unsupported;
• outdated;
• rights review required.

Migration should not revive old creative simply because the asset remains technically available.

Step 5: preserve destination and tracking rules

For every migrated campaign, verify:

• landing-page relevance;
• UTM/tracking parameters;
• conversion tags;
• consent behavior;
• redirects;
• mobile experience;
• excluded destinations;
• market/language routing.

A delivery migration can look successful while measurement or destination quality silently degrades.

Step 6: define comparable tests

Where account conditions permit, migrate in cohorts instead of switching everything simultaneously.

Possible designs include:

• one market first;
• one product category;
• matched Display and Demand Gen campaign cohorts;
• bounded GDN-only Demand Gen test;
• broader multi-channel Demand Gen treatment after initial validation.

Predefine KPI, guardrails and observation window.

Step 7: monitor guardrails

Track more than top-line ROI.

Useful guardrails include:

• placement quality;
• frequency;
• low-quality traffic;
• conversion quality;
• brand-safety incidents;
• invalid or suspicious traffic where observable;
• landing-page mismatch;
• creative rejection/policy issues;
• audience overlap.

A migration can increase attributed conversions while weakening downstream quality.

Step 8: keep vendor benchmarks scoped

Google's announcement cites an average ROI increase for advertisers adding GDN to Demand Gen.

Preserve:

• source;
• date;
• stated population;
• metric;
• internal-data scope.

Do not use the aggregate result as your forecast.

Your account may differ by creative quality, audience, bidding, market, conversion definition and existing campaign maturity.

Step 9: define rollback and exception handling

Keep:

• legacy campaign snapshot;
• migration date;
• settings map;
• migrated campaign ID;
• owner;
• unresolved differences;
• rollback criteria;
• validation result.

Rollback or narrow rollout when:

• destination/tracking breaks;
• audience controls are not preserved;
• brand-safety risk increases;
• conversion quality falls materially;
• the migrated structure cannot be reconciled with the baseline.

Step 10: retire legacy structures deliberately

Do not delete or archive useful historical evidence immediately after migration.

Retain enough information to explain:

• how settings mapped;
• which campaigns were replaced;
• what historical performance means;
• which reports should no longer be compared directly;
• when the new operating baseline begins.

Historical continuity matters for later budget and performance analysis.

Migration states

Use states such as:

• BASELINE_CAPTURED;
• CONTROL_MAP_COMPLETE;
• CREATIVE_REVIEW_REQUIRED;
• TEST_MIGRATION_ACTIVE;
• POST_MIGRATION_REVIEW;
• EXCEPTION_OPEN;
• ROLLBACK_REQUIRED;
• LEGACY_RETIRED.

The migration rule

The Display-to-Demand-Gen transition should be managed as a controlled delivery-system migration with explicit channel, audience and measurement continuity.

Preserve the legacy baseline, map controls, test in cohorts and keep Google's aggregate ROI claim labeled as vendor evidence. Scale only when the migrated setup is operationally and commercially validated in your own account.

Sources reviewed

• https://blog.google/products/ads-commerce/google-display-ads-demand-gen/