Google Display Ads Are Migrating to Demand Gen

digital advertising
Rows of shipping containers at a loading depot at golden hour with one open bay, representing Google Display campaigns being migrated into Demand Gen
Every standalone Display campaign is moving. The only question is whether you drive the migration or Google does it for you.

Google is retiring standalone Display campaigns. Every Display campaign in your account is moving into Demand Gen — the only real decision left is whether you drive the migration or let Google do it for you. The migration tool started rolling out in June 2026, the ability to create new standalone Display campaigns disappears around January 2027, and anything still sitting there afterward gets migrated automatically.

If you run Display for clients, the automatic path is the one to avoid. Not because Demand Gen is worse, but because a hands-off migration is the fastest way to quietly lose the exclusion hygiene that makes Display tolerable in the first place.


What's Actually Changing (and What Isn't)

Start with the part that causes the most panic in client calls: the Google Display Network is not going away. The same sites, the same apps, the same inventory. Nothing is being switched off.

What's changing is how you buy it. Instead of a Display campaign type, GDN becomes one channel inside a Demand Gen campaign, sitting alongside YouTube and Shorts, Discover, Gmail, and Maps. Google puts the combined reach at roughly 3 billion monthly active users, which is a big number that mostly matters as a warning: if you migrate carelessly, your carefully-scoped Display campaign wakes up serving across surfaces you never bought.

The upside is real too. Demand Gen brings formats Display never had — carousel ads, expanded video, lookalike segments, generative image tools — plus per-asset and per-channel reporting that standalone Display campaigns were always bad at. Google's own figure is a 9.5% average ROI increase for advertisers adding GDN into Demand Gen campaigns. Treat that as directional, not as a promise about your account.

The Timeline to Put on Your Calendar

Three dates, and only one of them is genuinely urgent.

June 2026 — the migration tool goes live in a phased rollout for eligible advertisers. This is the window where you're in control.

Around January 2027 — new standalone Display campaigns can no longer be created. Existing campaigns keep running and stay editable, but the campaign type is closed to new builds.

Through 2027 — automatic migration. Google has confirmed that eligible campaigns you haven't moved will be migrated for you, without advertiser action.

The urgency isn't the deadline. It's the queue. Every agency managing Display is going to hit this in the same two quarters, and the accounts that migrate last will be migrating under a hard cutoff with no room to test. We're treating the back half of 2026 as the migration window for every client account running GDN, one campaign at a time.

What Carries Over — and What Silently Doesn't

This is the section worth reading twice, because the unsupported list is where accounts get hurt.

Carries over cleanly: Target CPA, Maximize Conversions, Maximize Conversion Value, Target ROAS, and Maximize Clicks bidding. Lookalike audiences, remarketing lists, and contextual targeting all survive the move.

Does not carry over: Manual CPC. Viewable Impressions bidding. Bid adjustments. Combined audiences. Brand Lift measurement.

Manual CPC is the one that catches people. There are still plenty of long-running Display campaigns on manual bidding — usually the ones nobody wants to touch because they've been quietly profitable for three years. Those accounts have a choice: convert to an automated strategy deliberately, on a normal week, with time to let it stabilize; or get converted during a migration and try to untangle two variables at once.

Do the bid strategy change first, as its own change, and give it a week or two. Then migrate. Two clean experiments beat one confusing one.

Combined audiences are the second trap. If your targeting logic lives in combined audiences, you need to rebuild that intent as supported audience types before migration, not discover it missing afterward.

Why We Migrate Manually Instead of Waiting

The migration tool does something genuinely useful: it stitches data between the old and new campaign and ports performance history going back 42 days. That keeps the new campaign out of a cold start and cuts the learning period to about one to two days instead of the usual multi-week reset.

That alone is worth using the tool rather than rebuilding by hand. Rebuilding from scratch throws the history away and buys you a full learning period for no reason.

But the bigger argument for migrating manually is control over one specific setting: channel controls default to Google Display Network opted in, and Google's own guidance is to keep it GDN-only during migration so the campaign settings transfer properly. That's the setting you want to verify with your own eyes.

A migrated campaign that stays GDN-only is doing exactly what the old campaign did. That's the point. Migration should be a campaign-type change, not a media-plan change. Once it's stable, adding YouTube or Discover is a deliberate test you can actually read, because you changed one thing.

Wait for automatic migration and you get the campaign-type change and the settings audit at the same time, on Google's schedule, probably in a week when you're busy.

The Pre-Migration Checklist We Run on Client Accounts

The single most valuable asset in a mature Display account isn't the creative or the audiences. It's the exclusion list.

Most agencies with real GDN tenure have spent years pruning junk — made-for-advertising sites, garbage mobile apps, placements that burn budget and never convert. That list represents hundreds of hours of cleanup, and it is the thing most likely to get lost in a rushed migration. Search Engine Journal's Brooke Osmundson flagged exactly this when the retirement was announced, and it matches what we see in accounts: the exclusions don't become less important in Demand Gen, they just become easier to forget about.

So before anything moves:

Export everything. Placement exclusions, app exclusions, topic and content exclusions, account-level brand safety settings. Get them out of the interface and into a file you control.

Screenshot the baseline. Cost per conversion, conversion rate, and traffic quality patterns for the trailing 30 days. You need a before to argue about the after.

Clear the unsupported settings. Manual CPC, bid adjustments, combined audiences — handled and stabilized ahead of the migration, not during it.

Migrate one campaign, not the account. Pick the campaign you understand best. Watch it. Then do the rest.

Audit within 24 hours. Confirm the exclusions, audiences, bid strategy, targets, and budget all landed. Assume nothing transferred until you've seen it.

One thing to expect on day one: budget spent earlier in the same day isn't recognized by the new campaign, so delivery can look strange for the first 24 hours. That's documented behavior, not a broken migration. Don't panic-edit into it.

What to Watch in the First Two Weeks

Placement reports, first. Demand Gen's per-channel reporting is better than anything standalone Display offered, so use it — confirm GDN is where the spend is actually going and that no new surface crept in.

Then cost per conversion against your screenshot. A day or two of noise is normal given the learning reset. A sustained shift after week one is a signal, not noise.

And watch for new junk placements. A fresh campaign shell can surface inventory your old exclusion list was already handling. If your conversion tracking is soft, none of this is readable — which is its own problem, and one we've written about in the context of Google Ads and GA4 attribution mismatches.

Should You Just Move the Budget to Performance Max?

We get asked this every time, and the honest answer is usually no.

Performance Max hands placement decisions to Google across every surface it owns. That's the exact opposite of what a mature Display advertiser has been building — controlled placements, clean exclusions, predictable traffic quality. Migrating to Demand Gen preserves that work. Jumping to PMax discards it and calls it a strategy.

PMax may well deserve a slot in the account. It's a legitimate campaign type with real strengths, and it's part of the same broader push toward automated buying that's also reshaping search — see our take on Google AI Max for Search and the Google Ads Data Manager API migration. But it should earn its place through a test you designed, not become the default landing spot for budget you were forced to move.

Migrate Display to Demand Gen. Test PMax separately. Don't let a forced deadline make a strategy decision for you.

The Short Version

Standalone Display campaigns are being retired. The migration tool ports 42 days of history and keeps the learning period to a day or two, so use it rather than rebuilding. Keep channel controls at GDN-only so the migration changes the campaign type and nothing else. Export your exclusions before you touch anything, get off manual CPC and combined audiences first, and migrate one campaign at a time while you still have room to be wrong.

The accounts that get hurt here won't be the ones that migrated wrong. They'll be the ones that didn't migrate at all and let Google decide when.

Sources worth reading directly: Google's announcement on the Ads & Commerce blog and the Google Ads Help documentation on the migration.


Running Display for clients and not sure which campaigns are exposed? We audit Google Ads accounts for migration risk — unsupported bid strategies, exclusion lists that need exporting, and campaigns that should move first. Get a Free Automation Audit and we'll map your account's migration order, or see how we handle paid ads management end to end.