If your Google Display Network (GDN) retargeting is stable and CPA is predictable, the idea of moving it into Demand Gen probably feels like unnecessary risk. Fair. But Google has been clear about the direction: standalone Display campaigns are moving into Demand Gen, with migration tools starting in June 2026 and the full transition continuing into 2027.
So the constraint is simple: teams need to keep qualified pipeline steady while the campaign object changes under their feet. No drama. No “wait and see.” One controlled test that gives an answer.
If you only change one thing, change this: treat “Display has a new home in Demand Gen” as a measurement problem first, and a creative/targeting problem second.
What actually changed (and what didn’t)
Google positioned Demand Gen—launched in June 2023—as the newer home for “Display-style advertising” across YouTube, Discover, and Gmail. Translation: Google wants advertisers buying discovery placements in feed-like environments, not just the classic banner-and-remarketing mental model tied to GDN alone.
The under-discussed part is reporting and evaluation. Google’s documentation frames Demand Gen measurement around engagement across multiple placements and video interactions, not just a GDN-only view. That’s a different success shape. Clicks and last-click conversions will still show up, but the product is built to care about more signals than that.
And yes, GDN inventory is now part of the story. Google’s current position is that Google Display Network inventory can be integrated into Demand Gen (and it’s referenced alongside Video Action Campaigns), rather than being managed only through standalone Display campaigns.
Here’s the twist that matters operationally: Google is rolling out channel controls in Demand Gen so advertisers can choose placements across YouTube, Discover, Gmail, and the Google Display Network. This isn’t “everything is automated now, good luck.” There’s a knob. It just lives in a different place than your old Display workflow.
The one tactic: run a controlled “GDN inside Demand Gen” holdout
Google has published performance claims for adding Display inventory into Demand Gen / related campaigns. In a Google support note cited in the research brief, advertisers who added Display saw a statistically significant average lift of +16%, and a Google blog post cited a 9.5% ROI increase. Directionally interesting. Not proof for a B2B SaaS account with long sales cycles and messy attribution.
So the move is to test the consolidation on your terms: a holdout-based experiment that isolates the incremental value (or cost) of bringing GDN inventory under Demand Gen, while keeping placement governance tight enough that the readout means something.
The hypothesis (make it falsifiable): If we migrate a defined slice of our Display activity into a Demand Gen campaign with channel controls and separated asset groups, then blended conversion value (or qualified lead volume) will increase at a similar spend level because Demand Gen optimizes across YouTube/Discover/Gmail/GDN using richer engagement signals than standalone Display reporting.
But the context is more complex. Demand Gen and traditional Display are widely framed by practitioners as complementary but not interchangeable: Display can still be the cheap-reach hammer; Demand Gen is pitched as more immersive and more conversion-oriented. If the account has been using Display purely for low-cost awareness, expecting Demand Gen to behave the same way is how teams create “the channel stopped working” stories that are really setup mistakes.
Run it this week: setup, launch, readout, next test
Here’s the 5-minute version you can run this week:
- Owner: Paid media lead (setup) + RevOps/analytics partner (measurement) + creative ops (assets).
- Timeline: 14–28 days for an initial directional read; longer if your conversion lag is real.
- Budget range: Keep it meaningful but bounded—enough to exit learning, small enough that a miss doesn’t crater pipeline. (Exact dollars depend on your baseline; the point is guardrails.)
Setup
- Define the slice: pick one stable Display use case (usually retargeting or a single prospecting audience) that already has a baseline.
- Build Demand Gen with channel controls: set up Demand Gen and explicitly control channels to avoid “mystery mix” during the test. Google says channel controls are rolling out to choose placements across YouTube, Discover, Gmail, and GDN.
- Separate assets for control: Google advises separating video and image assets if you want placement control. Do it at the ad-group level so the readout isn’t polluted by asset-type drift.
- Holdout design: keep a portion of your existing Display activity unchanged as the baseline comparator. The goal is a blended read, not a screenshot of one campaign’s dashboard.
Launch
- Keep audiences constant: don’t “improve” targeting mid-test. Same lists/segments where possible.
- Match spend and cadence: aim for similar weekly spend to your pre-test baseline. Big budget swings make the analysis useless.
- Document exclusions and brand safety: consolidation can reduce the old standalone granularity some teams relied on. Write down what changed so surprises aren’t misdiagnosed as performance issues.
Readout
- Success = incremental lift in your primary outcome versus holdout. For many B2B teams that’s qualified lead volume or downstream conversion value (directional), not CTR.
- Guardrails = spend efficiency (CPA/CPL), plus one leading indicator Demand Gen is designed to capture (engagement across placements, video interactions) without over-weighting it.
- Stop-loss = if primary outcome drops materially versus baseline for two straight weeks at comparable spend, pause and revert. (Define “materially” internally—don’t freestyle it mid-flight.)
Next test
- Channel isolation: once the blended test is stable, run a follow-up where one channel is excluded to see what’s actually doing work.
- Asset fatigue check: Demand Gen is visual and feed-based by design; if you only port static assets, creative fatigue can show up fast. Plan refreshes like it’s paid social, not like it’s legacy display.
Trade-offs (and when this is wrong)
The trade-off is control versus consolidation. Demand Gen is built to span YouTube, Discover, Gmail, and now GDN inventory, with reporting designed around multi-surface engagement. That can be a win for performance. It can also feel like losing the clean, single-network simplicity of old Display when you’re trying to explain results to Finance.
When this is wrong: if Display in your account is purely a cheap reach layer and you don’t have the creative capacity to feed a more visual, feed-style environment, forcing a migration early can reduce volume before it improves quality. That’s not a moral failure. It’s unit economics.
Still, the migration timeline doesn’t care about preferences. Google is moving standalone Display campaigns into Demand Gen starting with tooling in June 2026, with the transition continuing into 2027. The teams that win won’t be the ones who “wait for the dust to settle.” They’ll be the ones who build a baseline now, so when the UI forces the move later, the numbers already have a spine.
