FAIRFAX, Va. — September 9, 2026 — A contractor can retain the same Google Ads campaign ID while the campaign's operating settings change underneath it. That is the central contradiction in Google's automatic migration of eligible legacy Search campaigns to AI Max: the reporting object can look continuous even when important matching and asset controls are no longer configured the same way.
Google began the phased migration on September 1, according to Google Ads documentation published that day. Search Engine Land and PPC Land subsequently reported that the transition applies to Search campaigns using legacy Automatically Created Assets or the campaign-level broad match setting. For contractors buying leads through Search, the immediate issue is not whether artificial intelligence is useful. It is whether pre-migration and post-migration results still represent the same operating conditions.
Continuity in the dashboard can conceal a structural break
A new campaign ID would create an obvious dividing line. Retaining the existing ID does the opposite. Historical and current performance remain attached to the same campaign, which can encourage an advertiser to read the series as though targeting, asset behavior and landing-page delivery were unchanged.
They may not be.
Google's documented migration behavior depends on the legacy configuration. Campaigns using Automatically Created Assets are moved to AI Max with search term matching and text customization enabled by default. Campaigns using campaign-level broad match are moved with search term matching enabled, while text customization remains off by default.
That difference matters because "migrated to AI Max" does not describe one uniform post-migration state. Two campaigns can receive the same AI Max label while carrying different active settings based on what they used before September 1.
Bottom line: Campaign identity is no longer enough to establish campaign comparability. The configuration before and after migration must be recorded separately.
The first control task is reconstructing what changed
The practical audit begins with scope. Google's September transition does not apply indiscriminately to every Search campaign. The documented migration path covers the legacy campaign-level broad match and Automatically Created Assets configurations.
Dynamic Search Ads are a separate case. Google postponed their automatic migration until February 2027 after advertiser feedback, according to the September reporting. The creation of new Dynamic Search Ad groups was nevertheless prohibited beginning in September 2026. That distinction helps resolve a possible source of confusion: Dynamic Search Ads are moving toward the same broader framework, but they are not part of the automatic September migration described here.
Existing brand inclusions and exclusions were designed to carry over. Contractors should still verify them rather than assume that a carried setting is producing the same practical outcome under expanded matching.
The timing also limits the available response. Reporting on the transition said advertisers could disable the affected legacy features before migration and thereby avoid the automatic upgrade. Once an eligible campaign had migrated, there was no campaign-level opt-out that restored the former configuration. Individual AI Max settings can still be reviewed, but the legacy operating state should not be treated as recoverable by default.
Measurement must begin with a dated baseline
The cleanest response is to mark the migration as a measurement event. Record the date each campaign changed, its prior legacy configuration, the AI Max settings active afterward and any subsequent manual adjustments.
Without that record, a contractor may attribute a change in lead volume or cost to seasonality, competition or budget when the campaign's matching or text behavior also changed. The point is not to presume that AI Max will perform worse. It is to prevent a platform transition from being mistaken for an ordinary fluctuation.
Google introduced reporting fields intended to make the expanded system more visible. The documented options include a search-term match-source segment and an AI Max search-term-and-ad-combination view. Those reports should be examined alongside the ordinary campaign totals because aggregate performance can conceal which new query and asset combinations are producing the result.
Final URL behavior deserves the same attention. September reporting advised advertisers to monitor expanded-final-URL data because a served landing page can differ from the URL configured in the ad when Final URL Expansion is in use. That can also affect tracking templates. A contractor evaluating Search leads should therefore verify not only that a conversion was recorded, but also which query, ad combination and landing page preceded it.
Lead quality is the operational test
AI Max can broaden the system's role in deciding how demand is matched and how text is customized. That makes input quality and conversion measurement more consequential, not less.
A campaign optimized against weak or incomplete conversion signals can appear efficient while producing outcomes the business does not value. Contractors should compare spend and conversion volume with qualified-lead and revenue outcomes available in their own records. The platform's reported conversion should be the beginning of the review, not the final verdict.
Negative keyword lists also require renewed attention. September coverage warned that expanded query matching can direct spending toward irrelevant traffic when controls and inputs are weak. Search-term review therefore remains a control function even when more campaign decisions are automated.
This is also where the company website becomes part of campaign governance. Landing pages need to make the offered service and intended customer action unambiguous. A managed option such as Trade Web Pro at tradewebpro.site can support that foundation, but the advertising account still requires its own migration log, conversion checks and search-term review.
Treat September 1 as a change in operating conditions
The durable conclusion is narrower than the AI debate surrounding it. Contractors do not need to decide whether automation is inherently good or bad. They need to determine whether the post-migration campaign is producing better business outcomes under a different set of controls.
That determination requires a defined break in the data, confirmation of the settings enabled by migration, inspection of match-source and ad-combination reporting, verification of delivered landing pages and comparison against qualified outcomes outside the headline campaign totals.
The risk is not simply that AI Max could spend differently. The more immediate risk is that the campaign can look like the same campaign while no longer operating under the same assumptions. Preserving the ID preserves history. It does not preserve the validity of an undifferentiated before-and-after comparison.
Sources: Google Ads official documentation, September 1, 2026; Search Engine Land, September 2, 2026; PPC Land, September 3, 2026