In this article
Migration is a continuity problem before it is an optimization problem
A general AI Max introduction explains capabilities. A migration audit asks whether the business meaning of an existing campaign survived the transition. That includes destinations, exclusions, conversion actions, asset claims and the connection between old and new reporting entities.
Check the actual notification and state in your account. Eligible campaigns can transition at different times. Do not infer the effective migration date solely from the month in the announcement. Record the date you can verify, the campaign identifiers and the relevant account-level settings.
Google's announcement describes migration tools and account notifications. Use current native guidance for the exact operational steps. This article provides an audit framework rather than pretending one static checklist covers every account configuration.
Preserve the baseline before editing
Export the settings and performance context you will need for comparison. Keep the original campaign and ad-group identifiers, destinations, goals, exclusions and the reporting window. Save both the business interpretation and the native configuration labels; future reviewers may not remember which object replaced which.
| Baseline item | Audit question |
|---|---|
| Campaign and ad-group mapping | Can performance before and after be compared meaningfully? |
| Conversion goals | Is the campaign still optimizing toward the same outcome? |
| Destination scope | Are relevant and excluded pages treated as intended? |
| Creative claims | Does generated messaging match the approved offer? |
| Targeting controls | Are business restrictions represented correctly? |
| Effective change date | Can a reporting discontinuity be located? |
Do not rely on screenshots alone when exportable configuration is available. Screenshots are useful context, but they can omit nested controls or the identity of the object being viewed. Retain the account, date and ownership information with the evidence.
Audit destination eligibility with the website owner
A campaign drawing meaning from website content can inherit outdated pages. Review service coverage, discontinued products, duplicate location pages and old promotion URLs. The business may want those pages accessible for customers while excluding them from advertising destinations.
Ask whether a generated headline accurately describes the destination. A page about general plumbing maintenance should not become an emergency repair offer because that theme sounds commercially attractive. The website and campaign owners need to agree on what the page represents.
Check mobile completion. An eligible destination can still have a broken booking action or an offer hidden under several navigation steps. That is a conversion problem independent of migration, but it becomes more visible when destination coverage changes.
Compare mature periods and retain an unchanged reference
Use equal weekdays and a consistent named conversion. Distinguish the migration date from later budget, target or asset changes. If a recent period has incomplete conversion data, disclose it rather than comparing it with a fully mature baseline.
An unchanged campaign can provide context, but it is not automatically a valid control. Different audiences, auctions or offers can create different trends. Use it to identify alternative explanations, not to claim experimental causality.
For a hypothetical account, a migrated campaign's CPA rises while its conversion definition also changes from enquiry to qualified lead. The apparent deterioration may represent a more demanding outcome. Reconcile the goal before concluding that AI Max made the traffic worse.
Prioritize defects by exposure
A missing business restriction on a high-spend campaign deserves urgent review. A cosmetic naming difference does not. Sort findings by spend exposure, commercial risk and confidence in the evidence. Attach the proposed remediation and the owner who can approve it.
Do not turn every audit finding into a simultaneous edit. Correct the verified configuration issue, record it and establish the next observation window. If you change several uncertain settings together, you may erase the evidence needed to assess the original migration.
Use 1ClickReport for the before-and-after review
Connect Google Ads to the AI marketing analyst and supply the native migration exports where relevant. Ask for campaign metrics and change history only where supported. The new migration controls or journey reports may not be available through a connector.
Review these campaigns around their verified DSA-to-AI-Max transition dates. State the old-to-new mappings, named conversion actions, timezone and later edits. Compare mature performance windows. Use the attached native settings exports for destination and control details. Separate verified configuration defects from hypotheses about performance, and propose a review order without making changes.Keep this audit with the campaign's decision record. A useful migration review gives the next marketer a stable explanation of what changed, rather than a story assembled after the monthly totals moved.
Frequently asked questions
Did every DSA campaign migrate on the same day?
The announcement describes eligible upgrades beginning in September and account notifications. Verify your own campaign's state and effective date.
Should I increase budget immediately after migration?
Not solely because the campaign upgraded. Establish settings continuity and mature performance first.
Can 1ClickReport certify every new native setting?
No. Use supported data plus native exports, and mark controls that require an account-level inspection.
Sources and research notes
Platform statements are linked below. The checklists, worked examples and analyst prompts are original editorial frameworks. Examples labeled hypothetical are not customer results. Research checked October 13, 2026; account availability may differ.