Google Ads AI Max Migration: What Changes in September 2026 (And What To Do Now)

The Migration Timeline You Need on the Calendar

Google has published a staged timeline rather than a single switch-over date. Campaigns are migrated in place using equivalent AI Max settings, and existing brand inclusions and exclusions carry over automatically — but "carried over automatically" is not the same as "configured correctly for your business".

• →Through September 2026 — automatic migration of campaign-level broad match and automatically created assets (ACA) to AI Max
• →Early September 2026 — creation of new legacy structures is switched off; anything you were planning to build the old way has to be built now or built differently
• →September 2026 onward — in-account notices begin encouraging voluntary Dynamic Search Ads upgrades
• →Mid-January 2027 — reminder notifications about the DSA migration
• →February 2027 — automatic DSA migration; the ability to create new DSA ad groups is permanently removed
• →Around September 2027 — older API versions supporting legacy features reach sunset, which matters if you run scripts or third-party integrations

What AI Max Actually Changes in the Account

AI Max moves Search campaigns from a keyword-list model toward an intent-matching model. Google expands the queries a campaign can serve against using your landing pages, assets and existing keywords as signal, then generates and assembles ad copy to match. The practical effect is that the boundary of your campaign is no longer defined solely by the keywords you typed in. For a business with wide margins and broad appeal, that is usually upside. For a business selling one specific high-ticket service in one region, it is a budget risk until it is constrained properly.

The Controls You Still Have — And Should Be Using

The single most common mistake we see is treating AI Max as all-or-nothing. It is not. The controls that protect spend are still there, and they matter more now than they did under manual keyword targeting, because the system is generating reach you did not explicitly ask for.

• →Negative keywords — still the primary lever. Lists should be rebuilt before migration, not after you have paid for the search terms that taught you.
• →Brand inclusions and exclusions — these carry over, but audit them; an exclusion list built for broad match may not cover the queries AI Max reaches.
• →Location targeting — tighten to your actual service area. Presence-based targeting rather than presence-or-interest is usually the right setting for local service businesses.
• →Final URL expansion — decide deliberately whether Google may send traffic to pages you did not nominate. For most lead-gen accounts, restrict it.
• →Asset-level controls — pinning and asset exclusions still govern what the system can assemble.
• →Audience signals — feed it your converter lists and customer match data so the expansion starts from good examples rather than guesses.

Why Conversion Tracking Quality Decides Whether AI Max Works

Every automated bidding and matching system is a function of the conversion data you feed it. Under manual keywords, bad tracking produced mediocre results. Under AI Max, bad tracking produces confidently wrong results at scale, because the system is expanding reach in the direction your conversion data points. If you are counting every form fill as a conversion — including the spam, the job applicants and the vendors — AI Max will find you more of exactly that. Before migration, we make sure conversions represent qualified business outcomes: offline conversion import from the CRM where the sales cycle is long, value-based bidding where project sizes differ materially, and conversion actions that exclude the low-quality paths.

What We Are Doing in Client Accounts This Month

The pre-migration audit is not complicated, but it has to happen before the migration rather than after. This is the sequence we run.

• →Export 12 months of search terms and build an expanded negative list from everything that produced spend without qualified enquiries
• →Verify every conversion action actually represents a business outcome, and remove or downgrade the ones that do not
• →Push offline conversion data back to Google Ads for any account with a sales cycle longer than a week
• →Tighten geography to real service areas, switching to presence-based targeting
• →Decide final URL expansion deliberately per campaign and document the decision
• →Set a clean pre-migration performance baseline — CPL, qualified lead rate, cost per qualified lead — so post-migration change is measurable rather than anecdotal
• →Diarise a structured review at 14 and 30 days post-migration, because the learning period will move numbers before it settles them

If You Run Scripts, an API Integration, or a Third-Party Tool

The API sunset is the part that tends to get missed until something breaks silently. Older API versions supporting legacy features are scheduled to sunset around September 2027, which sounds distant until you account for how many reporting dashboards, bid scripts and CRM integrations were built once and never revisited. Audit now: list every script and integration touching the account, identify which API version each depends on, and schedule the updates. A reporting dashboard that quietly stops updating is worse than one that visibly breaks.

Key Takeaway

AI Max is not optional and the timeline is not negotiable, so the only variable you control is how prepared the account is when the migration lands. The accounts that do well will be the ones with clean conversion data, disciplined negatives, honest geography and a documented performance baseline. The accounts that struggle will be the ones that let the migration happen to them and then try to diagnose a drop with no "before" to compare against. If you want a pre-migration audit on your account, we will run one and send you the findings — whether or not you work with us afterwards.