Google Display is moving to Demand Gen: the answer in 90 seconds
What SMEs should prepare now
Google is moving existing Display campaigns into Demand Gen in stages. As of 25 August 2026, eligible advertisers can transfer existing campaigns with the migration tool, while further steps will come later. The official announcement about the Display migration describes Demand Gen as the new home for the Google Display Network and says the transition is expected to be completed by 2027. It does not establish one binding shutdown date for every account. Notices in the individual Google Ads account and the current Help documentation remain decisive.
For an SME, moving Display to Demand Gen is therefore more than a change of name. Campaign type, available bidding strategies, exclusions, creative assets, feeds, reporting and measurement methods do not match one for one in every case. Google's recommended tool can carry over settings and a limited amount of performance signals. Unsupported features must still be identified in advance and then replaced appropriately, removed or deferred.
The core working document in this guide is the Display Migration Register. For every campaign, it records the original purpose, budget, bid, audiences, exclusions, ads, data sources, risks and sign-off criteria. A 90-day migration plan then builds on that record: 30 days to prepare, 30 days to pilot and stabilise, and 30 days to transfer controlled waves. These periods organise the work; they guarantee neither a specific learning period nor better performance.
Record every active and paused Display campaign together with its purpose, settings and accountable owner.
Document supported features, necessary equivalents and genuine migration blockers as separate findings.
Transfer one representative, manageable campaign first and observe it across its conversion cycle.
Migrate further campaigns in traceable cohorts only after the sign-off criteria have been met.
Display to Demand Gen: what Google has announced for 2027
Confirmed milestones and dates that remain open
The current Google Ads guidance for migrating existing Display campaigns sets out three stages. Since June 2026, the migration tool has been rolling out gradually to eligible advertisers. At a later point, new Display campaigns are expected to be created only within Demand Gen. Also later, remaining eligible campaigns are expected to migrate automatically without further action. For both later stages, the current Help page says only ‘Coming later’.
A timeline graphic published by Google identifies January 2027 as an initial reference point. It must not be presented as a universal, immutable deadline: Google says the timeline and feature availability may change, accounts may move in different waves, and the live Help page currently gives no precise date for the later stages. The editorially accurate position is therefore that the transition is expected by 2027, while account notices and current product documentation determine the specific time to act.
Existing campaigns do not disappear from an account immediately merely because the transition has been announced. Until they migrate, the current guidance says they can still be accessed and edited. Waiting is nevertheless not risk-free. An automatic migration leaves less room to resolve incompatible features, address policy issues, preserve comparison data and choose a suitable pilot window in advance. Preparation does not mean migrating every campaign immediately; it means not leaving the decision until the last available day.
January 2027 remains an initial reference point from the published timeline, not a claimed shutdown date for your account. Check the current Help page and Google Ads account notices before every wave.
What this migration guide covers — and what it does not
A technical transition, not a new channel strategy
This article starts with an existing Google Display campaign. It explains how to document its function, assess migration eligibility, select a transfer route, protect the cutover day and validate the new Demand Gen campaign. It does not reconsider which role YouTube, Discover, Gmail or Display should play in the overall media strategy. The first job of a migration is to preserve the campaign's existing business role as traceably as possible, not to redesign the entire media plan at the same time.
For subsequent channel planning, use the separate Demand Gen channel-task map for SMEs. It distinguishes YouTube, Discover, Gmail and the GDN by user state, creative asset, landing page and diagnostic signal. In this migration project, by contrast, the source campaign initially remains limited to the GDN whenever comparability with the previous Display delivery is the immediate requirement. Additional channels are a later extension that must be justified separately.
Avoid rebuilding several dimensions during the pilot. If the campaign objective, primary conversion, bidding strategy, audience, creative, landing page and channels all change together, a deviation can no longer be attributed with confidence. The Display Migration Register protects this boundary by separating necessary technical equivalents from optional strategic changes. Every optional change receives its own date, hypothesis and sign-off criterion.
Inventory every Display campaign before the upgrade
The Display Migration Register as a reliable baseline
Filter the account by the Display campaign type and first record every campaign that has not been removed. Enabled and paused campaigns both matter because recent activity may make either group eligible for a later migration. Removed campaigns are not planned as an operational cohort, but they remain important as historical references. Record the account, campaign ID, status, name and accountable owner before any setting is changed.
Do not stop the entry at budget and CPA. Document the business objective, primary conversion, attribution model and conversion window, bidding strategy, target, daily budget, shared budgets, locations, languages, audiences, optimised targeting, placement and topic exclusions, content suitability, ad types, logos, feeds, measurement studies and known policy restrictions. Add a baseline period that covers at least the typical conversion cycle, and preserve the columns needed for later evaluation.
The register is not simply an export. Add the business purpose, expected value and disruption risk for each campaign. This keeps seasonal revenue campaigns, always-on remarketing and reach activity in appropriate, separate migration waves.
| Campaign | Business objective | Bid and budget | Audiences and exclusions | Ads and feeds | Migration risk |
|---|---|---|---|---|---|
| Always-on customer acquisition | Qualified enquiry or purchase | Strategy, target, daily budget and conversion cycle | Signals, expansion, locations and safeguards | Responsive Display ad, static images, logo and landing page | Reporting gap, re-approval or changed optimisation |
| Remarketing | Relevant re-engagement | Budget appropriate to list size | List source, duration, buyer and lead exclusions | Sequence, validity and consent context | Overly broad delivery or missing exclusions |
| E-commerce with a feed | Revenue or conversion value | tROAS or value-based strategy | Product interest, existing customers and locations | Merchant Center, filters and product data | Unsupported filters or Business Data Feed |
| Seasonal or promotional | Result within a limited window | Budget, start, end and target | Current segments and geographic boundaries | Deadline, price, availability and rights | Too little time for renewed review and stabilisation |
Upgrade tool or manual budget transfer?
Eligibility, not convenience, determines the route
Google describes two routes. The recommended migration tool converts an eligible existing Display campaign to Demand Gen and transfers settings together with performance signals from up to 42 days. Google says this can avoid a complete cold start and shorten initial learning to approximately one or two days. That statement is a product estimate, not a promise that cost, volume or conversion quality will be stable after two days.
For a manual transition, create a new Demand Gen campaign and shift budget gradually: reduce the budget of the existing Display campaign while increasing the new campaign's budget proportionally. This route may be necessary if certain features block the tool or if a fundamentally different campaign architecture is intended. It needs its own learning and comparison plan. Running an identical new campaign alongside the historical source campaign can produce a difficult start because the older campaign has more performance history and both campaigns may compete for the same delivery.
Select the route for each register entry. The tool prioritises continuity; a manual rebuild requires a complete new set of checks. If a business-critical feature is only temporarily unsupported, documented waiting may be the more appropriate choice.
For eligible campaigns when history and comparable source settings should be carried forward as closely as possible.
For a genuine restructure or blockers that cannot be resolved acceptably, with a separate budget, learning and acceptance plan.
When a business-critical feature has been announced but is not yet reliably available and no immediate deadline applies.
Check migration eligibility: resolve blockers before starting
Map features instead of copying them blindly
Not every difference has the same significance. The current Demand Gen specifications and format requirements help teams verify required components such as the final URL, business name, logo, headlines and suitable image formats in advance. The migration guidance also lists specific tool errors, including a Responsive Display ad using the former disclaimer format, a missing logo, unsupported custom promotional text, click-to-call or lead-form assets, ad-group-level bid adjustments, product filters, a shared budget and certain exclusions.
Assign each finding to one of four classes. First: supported without change. Second: supported through a different or broader equivalent. Third: currently unsupported and requiring removal or an appropriate replacement before the upgrade. Fourth: announced but not yet reliably available. Only the Google Ads interface in the relevant account determines whether the tool actually accepts a campaign. A general comparison table does not replace a pre-check in the account.
Every remediation step must remain auditable. Replace removed lead forms with a tested conversion path, document dissolved shared budgets and assess the account-wide effects of content-suitability exclusions. Each correction needs the original value, rationale, accountable owner and evidence.
| Existing feature | Status in Demand Gen | Closest equivalent | Does it block the tool? | Action before migration | Evidence |
|---|---|---|---|---|---|
| Responsive Display ad without a logo | Logo required | A verified business logo instead of a placeholder | May require an addition | Prepare the logo and business name | Preview and policy status |
| Shared budget | Not supported for tool migration | Dedicated campaign budget | Yes, according to the current error list | Set the budget share and monthly allocation | Budget sign-off in the register |
| Lead form or click-to-call | Cannot transfer in the previous form | Suitable CTA and tested landing page | May prevent migration | Remove the asset and test the conversion path | Test enquiry or test click |
| Product filter | Different product logic | Product scopes or listing groups | May prevent migration | Document the filter and rebuild its logic | Approved product selection |
| HTML5 or third-party ad | Planned, subject to change | Verify the current account status | Depends on availability | Do not rely on announced dates | Successful creation and approval |
A feature planned for late 2026 is available only when the current Help documentation and the relevant account show that it can actually be used. Timelines may change.
Transfer bidding without distorting the optimisation logic
When manual CPC or pay for conversions cannot carry over
Target CPA, Maximize conversions, Maximize conversion value, Target ROAS and Maximize clicks are included among the supported strategies in the current comparison table. That does not mean every historical target remains appropriate automatically. Verify the actual primary conversion, conversion values, delay, budget constraint and previous volume. A transferred target can be technically identical yet commercially unsuitable if measurement or campaign logic has changed at the same time.
Manual CPC is not supported in Demand Gen; Google identifies Target CPC as an alternative. The official explanation of Target CPC bidding in Demand Gen describes an automated strategy intended to manage clicks around an average CPC target. It is therefore not manual control over individual bids. Viewable impressions are also not retained as the previous strategy; Google names Maximize clicks as the alternative. Campaigns using pay for conversions must change the payment event from conversion to interaction before migration and then continue with Target CPA.
Bid adjustments, seasonality adjustments and portfolio bidding are not available according to the current overview. Record their former purpose and a possible equivalent. Start with targets that are as comparable as practical, avoid changing the target and budget at the same time, and allow for the full conversion cycle.
- Confirm the primary conversion technically and commercially; do not allow micro-actions to become the optimisation basis unnoticed.
- Preserve the previous strategy, target, actual result, budget status and conversion delay in the register.
- Do not merely delete unsupported control; document its intended effect and the closest available equivalent.
- After the upgrade, make exactly one material bidding or budget change at a time.
- Reconcile CPA and ROAS with lead quality, revenue, margin or confirmed order value outside the platform.
Control how audiences, context and exclusions carry over
GDN-only as the first safety boundary
When a campaign is migrated with the tool, the Google Display Network remains selected by default and cannot be deselected during the process. Other surfaces can be added afterwards. The current channel controls in Demand Gen are managed at ad-group level. For the first comparison, restricting delivery to the GDN is usually the cleanest boundary because it prevents the technical transfer and a new cross-channel strategy from being mixed in the same observation.
Carry over the audience approach from a comparable Display campaign where the features and business purpose allow it. Review remarketing lists, Customer Match, custom segments, demographic settings, optimised targeting, contextual targeting and exclusions separately. An existing segment is not automatically a hard boundary; automated expansion may serve beyond the supplied signals. The register should therefore describe both the intended input and the expansion that is actually permitted.
Placement and topic exclusions are supported, while the migration overview says content-suitability exclusions in Demand Gen are available only at account level. Moving a control from campaign level to account level may affect other campaigns. Check the scope of the change, document the protection rationale and accountable owner, and inspect the report of actual delivery locations after migration. Ad-group-level exclusions or bid adjustments may block the tool and require a deliberate correction first.
Do not activate YouTube, Discover, Gmail or Maps in the same step when the first question is whether the previous GDN role continues to operate stably in technical and commercial terms.
Prepare ads, logos and feeds for re-approval
Migrated ads undergo a new policy review
Migrated ads are treated as newly created and must be approved again. Allow time between the upgrade and expected delivery for policy review and any required corrections. The Demand Gen asset report shows the status and performance data of individual text, image, video and logo assets, but notes that asset data is not updated in real time. It supports post-launch diagnosis; it does not replace a structured pre-launch review.
Before migration, verify the business name, logo, final URL, mobile landing page, copy, images, usage rights and required disclosures. If a logo is missing, the tool may generate a placeholder image; it should never become the permanent brand presentation without review. If an asset or destination is rejected under a policy, Google explains how to resolve or appeal a policy decision. Address the documented reason first. Repeated appeals without new grounds are not a quality-assurance process.
For e-commerce campaigns, distinguish Merchant Center product feeds from business data feeds. Product feeds receive partial support, while business data feeds are not yet supported according to the current migration overview. The guidance on product feeds in Demand Gen refers to requirements including a linked Merchant Center, approved product data and suitable filtering logic. Existing product filters may block migration and must then be reconstructed appropriately through product scopes or listing groups.
- Check the logo and business name against the brand, domain and policy status.
- Retest final URLs, language versions, forms, purchases and the mobile experience.
- Confirm disclaimers, promotional claims, deadlines, prices and availability against a current source.
- For every asset, document its source, usage rights, validity, approval status and accountable owner.
- Compare feed filters before and after migration against a saved product selection.
- Define a contingency plan in case important ads are not approved after the upgrade.
Preserve history, tracking and lift studies correctly
Forty-two days of learning signals are not five years of reporting
The migration tool can transfer up to 42 days of performance history to the new campaign. Google associates this with a shorter start-up period and links the source and destination campaigns to support performance continuity. That is not the same as a complete export of every historical setting, change and business outcome. After a successful migration, the original Display campaign is set to Removed, but under the Google Ads standard it remains available in the account for reporting for up to five years.
Before the upgrade, preserve your own baseline report with its date range, conversion cycle, cost, impressions, clicks, primary conversions, conversion value, targets and relevant quality data. Validate the technical measurement foundation at the same time. The SaleStudia guide to Google Ads conversion tracking with GA4 and Consent Mode explains how primary conversions, GA4, tags, consent status and later business data work together. A migration does not repair a duplicate, missing or commercially incorrect conversion.
Google does not recommend using the tool while a lift study is running because the destination campaign is not linked to it automatically. Record the study and the earliest migration date. Apply the same caution to seasonal tests or simultaneous landing-page changes.
Limited performance signals that the tool can carry into the new campaign to support continuity.
Potential availability of the removed source campaign for historical Google Ads reporting.
A saved comparison of settings, period, conversion maturity and business data before the upgrade.
Date, person, reason, old value, new value and expected effect for every correction.
Protect the migration day from budget surprises
Spend already used that day is not carried across
The campaign budget transfers during the upgrade, but the amount already spent by the old Display campaign on the same day is not taken into account by the new campaign. If, for example, the old campaign has used part of its daily budget, the new campaign may start the remainder of the day with the full transferred daily budget again. Google therefore warns of possible temporary underdelivery or overdelivery during the first 24 hours.
Schedule the migration in a controllable, commercially less critical window and record the spend so far that day immediately before starting it. Google's general explanation of average daily budgets in Google Ads makes clear that the amount is an average. For many campaigns, daily spend can reach up to twice the average daily budget, while a separate monthly charging limit applies. A daily budget is therefore not a guaranteed hard cap for each calendar day.
Set the accountable owner, tolerance and stop rule in advance. One unusual first day does not justify several spontaneous changes. First establish whether the cause is the budget restart, ad approval, status or delivery. A different migration day may be more appropriate for a time-sensitive offer.
The register must contain current spend for the day, transferred budget, accountable owner, observation window and stop rule before the migration is triggered.
The 90-day migration plan for SMEs
30 days to prepare, 30 days to pilot, 30 days to scale
This plan is an operating framework, not an official Google deadline. Pace and observation time depend on complexity and the conversion cycle. A phase ends only when its sign-off criterion has been met; the calendar does not resolve an open blocker.
During the first 30 days, build the register and baseline, verify tracking and feature compatibility, and define acceptance checks. Then select a campaign that is relevant but not business-critical as the pilot, outside any running lift study and essential seasonal peak.
Days 31 to 60 cover the upgrade, renewed ad review and stabilisation. Days 61 to 90 transfer prioritised cohorts. Although several campaigns can be handled at once, Google advises against a batch of more than 100; substantially smaller waves are usually more controllable for SMEs.
| Period | Cohort | Mandatory check | Action | Safeguard | Sign-off criterion |
|---|---|---|---|---|---|
| Days 1–10 | All non-removed Display campaigns | Purpose, status, IDs, baseline and owners | Build the Display Migration Register | Do not trigger any migration yet | Register complete and formally confirmed |
| Days 11–30 | Candidates grouped by risk | Blockers, tracking, assets, feeds and lift studies | Correct, test and select the route | Log each change individually | Pilot is eligible for the tool and approved |
| Days 31–45 | One representative pilot campaign | Spend for the day, status and re-approval | Migrate with the tool and keep it GDN-only | No simultaneous channel expansion | Delivery is technically stable |
| Days 46–60 | Pilot under observation | Cost, conversions, quality and delay | Evaluate at least one conversion cycle | No rushed multi-variable changes | Deviations are explained or resolved |
| Days 61–90 | Further prioritised waves | Approval for each register entry | Migrate and document small cohorts | Stop the wave if a systemic error occurs | Every campaign has completion evidence |
Run the migration with the Google Ads tool step by step
An operating procedure for the cutover day
In the campaign area, open the table, set the campaign-type filter to Display and select only campaigns signed off in the register. Then open the Edit menu and choose Upgrade to Demand Gen. The account displays a notice that settings and learning signals will transfer and that spend already used that day will not count towards the new daily budget. Stop if the selected campaigns, budget or warning do not match the register sign-off.
After selecting Apply, processing may take several minutes. Keep the wave within your actual review capacity and below Google's recommendation of no more than 100 campaigns in one operation. Record the time, IDs and warnings. The upgrade cannot be reversed to the old campaign type.
Under Bulk actions, verify the initiating user, status and changed campaigns. The destination campaign must have the Demand Gen type; its name and migration label support reconciliation. The source campaign is set to Removed, while its Enabled or Paused status is retained in the destination campaign.
- Immediately before starting, confirm register sign-off, ad status, spend for the day and accountable owner.
- Apply the Display filter and reconcile campaign IDs with the approved cohort.
- In the Edit menu, choose Upgrade to Demand Gen; read and document every warning in full.
- Select Apply only when the budget, status and campaign selection are correct.
- Check the bulk action for errors, initiator and the campaigns that were actually changed.
- Verify Demand Gen campaign type, name, label, GDN selection and status for every destination campaign.
- Link the removed source campaign and the saved baseline in the register.
- If errors occur, do not improvise by starting more campaigns; stop the wave and classify the cause.
Keep the first days after the upgrade stable
Separate the short tool learning period from longer conversion cycles
For eligible campaigns migrated with the tool, Google describes a shortened learning period of approximately one or two days. The general guidance on the Demand Gen learning phase also explains that new campaigns or material changes may need more calibration. Google does not guarantee one fixed duration for every account: relevant factors include conversion volume, the length of the conversion cycle and the bidding strategy; existing data may shorten calibration. These statements are not contradictory: the tool reduces the cold start but does not eliminate the need for observation or conversion delay.
During the first 24 hours, focus mainly on technical states: status, policy approval, budget, GDN selection, landing page, conversion firing and obvious delivery errors. An unusual CPA in this window is rarely a reliable strategic conclusion. During the following days, verify whether impressions, clicks and conversions are arriving at all and whether the campaign remains marked as Learning. Resolve urgent technical problems; give ordinary fluctuations enough observation time.
Avoid making major changes to bidding, budget, conversion objective, audience and creative at the same time. Any of those changes can trigger recalibration and obscure the cause of later deviations. Waiting is not inactivity: review policies, landing pages, forms, product availability, CRM feedback and conversion lag without reconfiguring the optimisation system every day. The register specifies the earliest substantive review after one complete conversion cycle.
Verify status, budget restart, approval, GDN selection, landing pages and conversion firing.
Observe delivery and learning status; correct only evidenced technical or policy errors.
Review cost, placements and early results without making a final judgement on immature conversions.
Connect platform values with mature leads, purchases, revenue and the company's quality data.
Validate status, delivery, cost and quality after migration
The post-migration record for every campaign
The documentation for Demand Gen metrics and reporting allows reporting to be segmented by network, among other dimensions. For a GDN-only migration, actual delivery must remain within the planned GDN boundary. Also verify the campaign type, name, label, status, budget, bid, primary conversion, audiences, exclusions, ad approval and final URLs. A technically active campaign is accepted only after its operational safeguards have also been confirmed.
Use the ‘Where ads showed’ report to inspect actual environments. Google warns against treating it as a complete placement list or an exact billing source: infrequent delivery may be omitted, and thresholds and invalid traffic affect what appears. Use it to identify recurring patterns and brand suitability, not to make rushed exclusions after isolated observations. Billing records remain authoritative for billed costs.
Compare against the documented baseline using similar seasonality and conversion maturity. Separate volatility, technical error and commercial deterioration. A lower CPA loses its value if lead quality or margin falls, while B2B outcomes may arrive with a longer delay.
| Review window | Control signal | Expected deviation | Stop signal | Decision |
|---|---|---|---|---|
| Migration day | Type, status, label, budget and GDN selection | Budget restarts in the destination | Wrong campaign, wrong status or uncontrolled spend | Pause and resolve the technical mapping |
| Day 1–2 | Approval, impressions, landing page and conversion test | Review and brief calibration | Rejection, broken page or missing measurement | Resolve the error; do not scale strategically yet |
| Day 3–7 | Cost, delivery, early conversions and placement patterns | Volatility and reporting delay | Repeated brand risk or systematic malfunction | Isolate the cause and change one variable |
| Full conversion cycle | Mature conversions, value, lead quality and margin | Late attribution and small sample | Business quality consistently below the sign-off threshold | Continue observing, correct or stop |
| Day 30 | Baseline comparison and documented deviations | Seasonality and market conditions may limit comparison | Unexplained deterioration despite correct implementation | Hold the pilot or approve the next cohort |
When additional Demand Gen channels may be added
Secure the baseline before extending reach
The migration is complete when the previous GDN role is running traceably and every acceptance field has been completed. That does not automatically justify expansion to YouTube, Discover, Gmail or Maps. New inventory changes creative requirements, reporting and budget allocation.
Expand only with a defined user state, suitable creative, an appropriate landing page and a diagnostic signal. Record the GDN baseline separately from the expansion date so that later changes can be attributed to the new inventory rather than the technical migration.
For re-engagement or the use of first-party data, audience and consent logic must also remain valid. The guide to planning remarketing audiences and consent explains segment meaning, exclusions, time windows and measurement limits. A migrated campaign does not legitimise unlimited repetition or expansion beyond the intended audience. Recheck optimised targeting and exclusions after every structural change.
Record every expansion in the change log with its hypothesis, creative, landing page, budget effect, measurement window and reversion rule. Otherwise the migration baseline loses its value.
Frequently asked questions about the Display-to-Demand-Gen migration
Eight answers before selecting ‘Upgrade’
These answers reflect the documented position as of 25 August 2026. Rollout, account eligibility, dates and supported features may change. Before taking operational action, check the current Google Ads Help documentation and the notices in the affected account.
Will existing Display campaigns be switched off immediately?
No. Existing Display campaigns can be accessed and edited until they migrate. The tool has been rolling out gradually since June 2026; restrictions on new campaign creation and automatic migration come later. Account notices are expected to communicate important dates.
Is there already a binding shutdown date in January 2027?
No. The timeline graphic identifies January 2027 as an initial reference point, while the current Help page uses only ‘Coming later’ for the next stages. Timelines may change. Do not claim a universal January date; check current guidance and account notices.
Can the migrated campaign remain exclusively on the GDN?
Yes. During tool migration, the GDN is selected by default and cannot be deselected. Additional channels can be added later. For comparability, begin GDN-only and give each subsequent expansion its own hypothesis.
Can the upgrade be reversed?
No. A migrated campaign cannot be converted back to the former Display type. The source is set to Removed and remains available for historical reporting. Confirm the selection, budget, status and blockers before choosing Apply.
Are historical data and learning signals preserved?
The tool can transfer signals from up to 42 days. The removed source remains available for reporting for up to five years. Preserve a separate baseline and change log as well; learning signals and historical reporting views do not replace your own documentation.
Do ads need to be approved again?
Yes. Migrated ads are treated as new and reviewed again. Also check any placeholder generated automatically for a missing logo. Allow time for review, correction and, where justified, an evidence-based appeal.
What happens to Manual CPC, Pay for Conversions and HTML5 ads?
Manual CPC is replaced by automated Target CPC logic. For Pay for Conversions, change the payment event from conversion to interaction before continuing with Target CPA. HTML5 and third-party formats were planned for late 2026; verify actual availability before relying on them.
When is the migration tool better than a manual rebuild?
The tool is recommended for eligible campaigns that need continuity. A rebuild suits blockers that cannot be resolved acceptably or a genuine restructure. Do not run an uncontrolled identical copy in parallel; define the budget, learning window and acceptance criteria first.
Manage the Display migration through 2027 with clear controls
A reliable transition produces five evidenced outcomes: a complete Display Migration Register, documented feature mapping, a signed-off pilot campaign, a validated post-migration record and prioritised remaining cohorts. A campaign is marked complete only after its purpose, status, budget, bid, audiences, exclusions, creative assets, tracking and accountability have been confirmed. An approved policy status alone is not sufficient.
For SMEs, a small and traceable wave is usually more valuable than a rapid account-wide switch. It limits budget risk, creates time for ad re-approval and shows which deviations are systemic rather than campaign-specific. The 90-day model gives the work an order without making rigid performance promises. If Google changes dates or features, update the register; the operational safeguard and acceptance rules remain in place.
Once the GDN migration is stable, additional Demand Gen channels may be considered, but only as a new and separately measurable test. The decisive question is not whether every available feature has been activated, but whether the campaign still supports a relevant business objective with controllable cost and demonstrable quality.
If you want to assess existing Display campaigns, document migration risk and prepare a controlled transition to Demand Gen, SaleStudia can support strategy, tracking, creative and your ongoing online advertising for businesses.