Google last month confirmed that standalone Display Ads campaigns are being retired, with the Google Display Network folded into Demand Gen as the new unified home for visual advertising across more than 2 million sites, videos and apps. A phased migration tool is now rolling out, and the full transition is expected to complete by 2027.
What is actually changing
The announcement, published on May 26, 2026 on the Google Ads and Commerce Blog, marks the end of Google Display Ads as a standalone campaign type. According to Google, advertisers can now manage their Google Display Network (GDN) presence directly through Demand Gen campaigns. The campaign creation workflow changes, but the underlying network remains unchanged - the same inventory of more than 2 million sites, videos and apps remains accessible.
The move is significant in scale and in what it signals. Display Ads have been part of Google's advertising infrastructure for well over a decade. Folding them into Demand Gen is not a minor interface update. It is a structural consolidation that changes how advertisers set up, manage, and report on their display activity going forward.
What remains available? Advertisers who want to serve ads exclusively on GDN can still do so. According to Google's Help Center documentation, customers looking for Display-only campaigns can continue purchasing them within Demand Gen using channel controls - a feature that lets advertisers isolate specific placements. The difference is that the campaign shell itself is now Demand Gen, not a standalone Display campaign.
The migration tool and how it works
Google is launching a phased rollout of its migration tool in June 2026. Eligible advertisers can begin moving existing Google Display Ads campaigns to Google Display Network on Demand Gen using the tool directly inside their Google Ads account.
The tool is the recommended path. According to Google's Help Center, it allows advertisers to update live campaigns with performance history going back 42 days ported over to the new campaign. That historical data transfer reduces learning time to approximately 1 to 2 days and avoids a "cold start" - the period during which Google's bidding models lack sufficient data and can underperform. The alternative is a manual budget transition, where advertisers gradually shift spend from existing Display campaigns to Demand Gen by decreasing budgets on the former while proportionally increasing them on the latter.
The step-by-step process inside Google Ads involves navigating to the Campaigns menu, filtering by campaign type for "Display," selecting the campaigns to migrate, then choosing "Upgrade to Demand Gen" from the Edit dropdown. The migration can handle multiple campaigns simultaneously, though Google does not recommend batches of more than 100 campaigns at a time.
A few technical details matter here. Migrated campaigns will be renamed following the convention "[Original campaign name] #2." The original Google Display Ads campaigns are not deleted - they are set to "Removed" status and remain in the account for reporting purposes for up to five years under Google Ads' standard retention policy. Advertisers running lift measurement studies - such as Conversion Lift - are advised not to use the migration tool while a study is active, because the converted campaign will not be automatically associated with the ongoing study.
Budget handling on migration day carries a specific wrinkle. According to Google's documentation, any budget spent earlier in the day on the Google Display Ads campaign will not be recognised by the new Demand Gen campaign. If a campaign has spent $10 of a $50 daily budget before migration, the new Demand Gen campaign resets and starts with the full $50 for the remainder of the day. Temporary underdelivery or overdelivery is possible within the first 24 hours.
Performance claims and real-world data
Google is citing two sets of numbers to support the migration. On average, according to the announcement, advertisers adding GDN in Demand Gen campaigns see a 9.5% increase in return on investment (ROI). The company also pointed to GoFood, a food delivery platform, as a case study. According to Google, GoFood saw a 24% decrease in cost per acquisition (CPA) and a 19% higher conversion volume after adding GDN to its Demand Gen campaigns.
These figures come from Google's own data and should be read in that context. The 9.5% ROI improvement and GoFood case study reflect conditions that may not transfer uniformly across industries, account sizes, or competitive environments. Advertisers who have relied on standalone Display campaigns for years will need to test and monitor performance independently after migration, particularly during the first several days when fluctuations are expected.
Feature changes: what is gained and what is lost
The move from Google Display Ads to GDN in Demand Gen involves a meaningful shift in feature availability. Not everything carries over directly, and some capabilities available in Display Ads are not available in Demand Gen.
On the inventory side, Demand Gen expands reach beyond what Google Display Ads offered. Where Display Ads ran across GDN, YouTube, and Gmail, Demand Gen adds Discover and Maps (Maps currently in beta). The ad surfaces available expand from three to five, giving advertisers who opt into them a broader footprint.
Creative formats also expand. Google Display Ads supported Responsive Display Ads, uploaded Display Ads (image ads, HTML5, GIF), and product feeds from Google Merchant Center and Business Data Feeds. Demand Gen adds carousel ads, generative image tools, a wider range of video ad formats, and HTML5 (described in the documentation as "coming soon" for GDN in Demand Gen). GIF support, however, is not listed among the available formats in Demand Gen.
On the audience targeting side, the transition introduces Lookalike segments as a replacement for Similar Audiences. Lookalike segments allow advertisers to reach new users who share characteristics with existing customers. The core targeting options - optimised targeting, remarketing lists, custom segments, first-party data, interest, demographics, and contextual targeting - remain available in both formats.
Bidding changes in specific ways. Manual CPC, Viewable Impressions, and Pay for Conversions are not available in Demand Gen. What replaces them are Max conversions, Max conversion value, tCPA, tROAS, Max clicks, and a new option called tCPC (target cost per click). Demand Gen also introduces Flighted Campaign Total Budgets, which are not available in Google Display Ads.
Pay for Conversions campaigns specifically are handled by the migration tool automatically. According to the documentation, these campaigns will be switched to pay for clicks, while continuing to use target CPA to optimise for conversions at the advertiser's stated target.
Reporting gains one notable capability in Demand Gen: format segmentation reporting. This breaks down performance data at the format level, including In-Feed, Skippable In-Stream, and Shorts, giving advertisers visibility they did not have within standalone Display campaigns.
Logos and business names are pre-populated from existing Google Display Ads campaigns during migration. If a Display Ads campaign lacks a logo, the migration tool creates a placeholder image to ensure continuity. Advertisers can edit this after migration completes.
Key dates and what comes next
The timeline for this migration has three stages, according to Google's Help Center documentation.
June 2026: The phased rollout of the migration tool begins. Eligible advertisers can start moving existing Google Display Ads campaigns to GDN on Demand Gen using the tool in their Google Ads accounts.
Coming later (no specific date provided): New Google Display Ads campaigns can only be created within Demand Gen. Advertisers can still access and edit existing Display Ads campaigns until they are migrated.
Coming later (no specific date provided): Remaining eligible Google Display Ads campaigns will be automatically migrated to GDN on Demand Gen without any advertiser action required.
The full migration is expected to complete by 2027. Google has said it will provide account notifications in Google Ads as key dates approach.
Where the money goes - and does not go
There is a dimension to this migration that sits outside the migration checklist: the question of who ultimately benefits from ad spend flowing into Demand Gen rather than standalone Display, and how the balance between Google-owned and publisher inventory shifts in the process.
Google Display Ads - the format being retired - ran by default across the Google Display Network, a third-party publisher ecosystem spanning more than 2 million sites and apps. When an advertiser ran a Display campaign and ads served on an external publisher's website, a portion of that revenue was shared with the publisher via AdSense or Google Ad Manager. That revenue-sharing model has underpinned publisher monetisation across the open web for over a decade.
Demand Gen has a more layered inventory structure, and understanding it requires separating the surfaces available within the campaign type. The primary surfaces in Demand Gen - YouTube, Discover, Gmail, and Maps - are all Google-owned properties. Discover is Google's personalised content feed. Gmail is Google's email service. Maps is Google's navigation product. According to PPC Land's analysis of Demand Gen placements, unlike traditional YouTube ads where Google must split revenue with video creators, Demand Gen placements on surfaces like Discover and Gmail allow Google to retain a larger portion of advertising revenue. Those surfaces carry no revenue share obligation to external publishers.
GDN is also available within Demand Gen - but the mechanics are different from how standalone Display Ads worked. In a standard Display campaign, GDN was the entire network, and every impression served on a third-party publisher site generated revenue for that publisher. In Demand Gen, GDN is one channel among several, accessed via explicit channel controls at the ad group level. The default campaign configuration points spend toward YouTube, Discover, Gmail, and Maps. Advertisers who want GDN inventory must actively opt into it. That shift from default to opt-in is consequential at scale.
In Display & Video 360, the distinction is encoded directly into the reporting infrastructure. According to PPC Land's coverage of DV360's granular inventory controls, the standard Inventory Source reporting dimension labels YouTube, Discover, and Gmail traffic as "Google Owned Properties," while GDN traffic appears separately as "Google Display Network." Google itself maintains that boundary in its own systems - a clear delineation between inventory where revenue stays with Google and inventory where a share flows to external publishers.
The financial trajectory of Google's Network advertising segment - the one that pays out to publishers - makes the stakes concrete. Google's advertising revenue distribution reached a point in mid-2025 where 90% of revenues were flowing to its own properties rather than through publisher partnerships, according to PPC Land's analysis following Alphabet's Q2 2025 earnings. Network advertising revenue - covering AdSense, AdMob, and Google Ad Manager - declined 1% year-on-year to $7.4 billion in Q2 2025. By Q1 2026, that figure had fallen further to $6.97 billion, a 4% year-on-year drop of approximately $285 million in a single quarter, according to PPC Land's coverage of Alphabet's earnings release.
The Display Ads migration adds structural momentum to that decline. In standalone Display campaigns, GDN publisher inventory was the default and the entire point of the campaign type. In Demand Gen, GDN is an optional channel that requires a deliberate activation step. Every advertiser who migrates without explicitly enabling GDN via channel controls will, by default, direct their visual advertising spend toward Google-owned surfaces where no publisher revenue share applies. Budget that previously flowed to external websites through AdSense now flows to YouTube, Discover, Gmail, and Maps instead.
Google's Network ad revenue decline has also been attributed in part to AI Overviews reducing click-through rates from search results, which reduces traffic to publisher sites and therefore ad impressions served through AdSense and Ad Manager. The Display migration applies pressure from a different direction: it reduces the share of advertiser display budgets that flow to external publishers, independent of what happens to search traffic volumes.
GDN inventory remains technically available inside Demand Gen, and publishers on the network can still earn revenue from advertisers who opt in. That is the honest limit of the claim. But the structural change is real: the campaign type that made GDN the default has been retired, and the one replacing it treats GDN as an elective channel within a portfolio that tilts heavily toward Google's own properties.
Why this matters for the marketing community
This consolidation is one of several structural moves Google has made to reduce the number of distinct campaign types in its advertising platform. The retirement of YouTube Video Action campaigns in favour of Demand Gen completed by April 2025, and Demand Gen was expanded to Display & Video 360 in October 2024. The pattern is consistent: Google is reducing campaign-type fragmentation and concentrating activity inside a smaller set of formats built around its AI-driven bidding and creative tools.
Google quietly removed Display and Video campaign support from Performance Planner on March 9, 2026, eliminating the ability to model those campaigns in its forecasting tool. Taken together with the Display migration announcement, the signals from Google have been clear for months. Standalone Display infrastructure is being wound down.
The Google Marketing Live 2026 announcements in May included Demand Gen's expansion to Google Maps with Promoted Pins, and further AI-assisted campaign creation tools - all pointing toward Demand Gen as the primary canvas for visual advertising across Google's owned-and-operated surfaces.
For advertisers, the operational consequences are real. Campaigns that have accumulated years of performance history inside Google Display Ads will need to be migrated. The migration tool attempts to transfer 42 days of historical data to ease the transition, but the learning reset is not zero - performance fluctuations within the first several days are explicitly flagged by Google's own documentation. Advertisers running lift studies or time-sensitive campaigns will need to plan the migration window carefully.
The removal of Manual CPC and Pay for Conversions bidding in Demand Gen will also require workflow changes for teams that have built their optimisation processes around those options. February 2026 changes to how Lookalike segments function in Demand Gen - converting them from hard targeting constraints to audience suggestions - had already altered the audience control model. The Display migration adds another layer to the adjustment.
Advertisers who re-approve migrated ads should expect them to go through the standard approval process. According to Google, migrated ads are treated as newly created ads regardless of how they are transitioned, which means they must be submitted for approval before they can serve. This is particularly relevant for advertisers planning to migrate close to a campaign's scheduled start date.
What best practices say
Google's Help Center outlines recommended steps for advertisers using the migration tool. On channels, the guidance is to keep GDN-only selected in channel controls during migration to ensure a proper campaign setting transfer - additional channels like YouTube and Gmail can be added after the migration is complete.
On audiences, Google recommends replicating the audience approach from comparable Display campaigns and testing Lookalike segments. On bidding, the advice is to try similar bid levels to existing Display campaigns, set the conversion attribution window to more than 28 days, and limit bid changes to no more than plus or minus 15% - waiting at least a week between adjustments.
On creative, Google recommends expanding the number of assets, including a business logo and video assets. According to the documentation, this allows ads to scale across the widest possible range of inventory slots, which typically leads to stronger overall performance.
Campaign consolidation is also advised: combining similar audience themes across ad groups, and considering merging ad groups with fewer than approximately 30 conversions in 30 days. A consolidated campaign structure allows Google's AI to learn more efficiently.
Timeline
- September 2024 - Google announces Video Action Campaigns will merge with Demand Gen by Q2 2025, with migration tool planned for early 2025.
- September 2024 - Demand Gen expands to Display & Video 360, scheduled for October 2024 rollout.
- February 2025 - Google clarifies distinct roles of Performance Max and Demand Gen, confirming GDN availability for Demand Gen from March 2025.
- March 2025 - Channel placement controls arrive for Demand Gen campaigns, enabling granular selection across YouTube, Discover, Gmail, and Display Network.
- March 2025 - DV360 adds GDN inventory support for Demand Gen line items, announced March 3, 2025, with late April implementation.
- April 2025 - Deadline for YouTube Video Action campaigns; remaining campaigns automatically upgraded to Demand Gen. PPC Land coverage.
- November 2025 - Google launches four new Demand Gen features for holiday campaigns, including brand suitability controls and A/B asset experiments.
- February 2026 - Google converts Lookalike segments in Demand Gen from hard targeting constraints to audience suggestions, effective March 2026.
- March 9, 2026 - Google removes Display and Video campaign support from Performance Planner, eliminating impression share metrics and locking existing plans from view or editing.
- May 20, 2026 - Google Marketing Live 2026 announces Demand Gen expansion to Google Maps with Promoted Pins and AI-assisted campaign creation.
- May 26, 2026 - Google announces Display Ads migration to Demand Gen on the Ads and Commerce Blog.
- June 2026 - Phased rollout of migration tool begins; eligible advertisers can migrate existing Display Ads campaigns using the in-account tool.
- 2027 (expected) - Full migration completes; remaining eligible Display campaigns automatically migrated to GDN on Demand Gen.
Summary
Who: Google, affecting all advertisers currently running Google Display Ads campaigns globally, announced via the Google Ads and Commerce Blog.
What: Google Display Ads campaigns are being retired as a standalone campaign type. The Google Display Network is being folded into Demand Gen as the unified home for visual advertising, expanding the available ad surfaces from GDN plus YouTube and Gmail to also include Discover and Maps. A migration tool is launching in June 2026 to help advertisers transfer existing campaigns, with 42 days of performance history ported over. The full migration is expected to complete by 2027.
When: The announcement was published on May 26, 2026. The migration tool rollout begins in June 2026. A future date - not yet specified - will prevent the creation of new standalone Display Ads campaigns. A second future date will trigger automatic migration of all remaining Display campaigns.
Where: The change applies to Google Ads globally. Advertisers manage the migration from within their Google Ads accounts. Google Display Network inventory - more than 2 million sites, videos and apps - remains available via Demand Gen campaigns after migration.
Why: Google frames the migration as a response to shifting consumer behaviour and a push toward more unified campaign management. The consolidation aligns with a multi-year pattern of reducing standalone campaign types: Video Action Campaigns were absorbed into Demand Gen by April 2025, Display was removed from Performance Planner in March 2026, and Google Marketing Live 2026 confirmed Demand Gen as the primary vehicle for visual advertising across Google's owned-and-operated surfaces. Advertisers adding GDN in Demand Gen campaigns see on average a 9.5% ROI increase, according to Google's own data.
Discussion