Google's AI Max Auto-Migration Is Live: What Changes If You Don't Touch Your Account

What is AI Max, and how is it different from Performance Max?

They sound alike and get confused constantly, but they're not the same product. Performance Max is a standalone campaign type that runs across Search, Display, YouTube, Gmail, Maps, and Discover from one budget, with Google's system handling channel allocation. AI Max is narrower: it's a layer that sits on top of Search campaigns specifically, adding two things: expanded query matching that goes beyond your literal keywords, and AI-generated headlines and descriptions assembled from your existing assets and landing page content.

If Performance Max is "let Google run the whole account," AI Max is "let Google loosen the matching and writing inside a Search campaign you still control the structure of." That distinction matters for the migration: a Performance Max campaign is unaffected by this specific rollout, because AI Max only touches Search.

Which campaigns are actually being auto-migrated this month?

Two categories, and it's worth checking both against your own account rather than assuming.

Campaign-level Broad Match. If a Search campaign has Broad Match set at the campaign level rather than per-keyword, Google is converting it to AI Max during this window.

Standalone Automatically Created Assets. If you're running Automatically Created Assets without AI Max already layered on, that campaign gets upgraded too.

What's not in this wave: Dynamic Search Ads campaigns, which get in-account nudges now but aren't force-migrated until February 2027, at which point the ability to create new DSA ad groups is removed entirely. If your account leans on DSA for long-tail coverage, that's the deadline to actually plan around, not this month's.

The edge case that catches people: campaigns that look like they qualify but were manually opted into AI Max already. Those aren't "migrated" in the sense of a visible change this month. They're already there, and this rollout just closes the gap for everyone who hadn't opted in.

What happens to language targeting in the same window?

A second, related change lands in the same September window and gets missed because it's not branded as part of the AI Max story: Google is removing the campaign-level language targeting setting for Search and AI Max campaigns. Going forward, Search ads match based on the language of the ad itself and the landing page, not a manual language criterion you set at the campaign level.

Performance Max is split by channel here: on Google Search, the behavior mirrors Search campaigns (language setting no longer applies); on other channels inside PMax (YouTube, Display, Discover, Gmail), the campaign-level language setting still governs visibility. If you manage PMax accounts, that channel split is the detail to flag to whoever owns reporting, because it means "language targeting" now means two different things depending on which surface inside the same campaign you're looking at.

On the API side: existing language criteria persist in read queries but stop being used for targeting, and attempting to add or update one on a new Search campaign now returns an error. If you have scripts or a management layer that sets language criteria programmatically, that's a break worth testing for before the change lands, not after a script starts failing silently.

What should you actually check before the migration reaches your account?

Four things, in order of how often they get skipped.

Audit which campaigns qualify. Pull every Search campaign with campaign-level Broad Match or standalone Automatically Created Assets. Don't assume your account team already did this. The notification is in-account, not proactive outreach, and it's easy to miss inside a busy Google Ads UI.

Check asset quality before AI Max starts generating from it. AI Max assembles headlines and descriptions from your existing assets and landing page. If your asset library is thin or your landing page copy is inconsistent with your ad copy, that's what gets amplified, not fixed. Review before the migration, because after it, you're evaluating live traffic instead of a hypothesis.

Decide what "broader matching" means for your negative keyword list. Expanded query matching finds more of the query space around your keywords: some of it relevant, some of it not. Your negative keyword list is the lever that controls the downside, and it's worth a fresh pass timed to the migration rather than reacting to spend after the fact.

Confirm nothing in your reporting stack assumes the old campaign structure. If a dashboard or script keys off "Broad Match campaign" as a category, that label may not mean what it used to once AI Max reclassifies the campaign underneath it.

Does this change who approves what in an agent-run account?

No. This is the distinction worth being precise about. AI Max changes what Google's own systems do inside a Search campaign: how broadly it matches queries, what assets it writes. It does not change who has to sign off on a bid change, a budget increase, or a new campaign in an execution layer sitting on top of the account.

That's a real boundary to keep visible, though, not an assumption to make. Platform-native automation, AI Max included, changes your account without appearing as a proposal in any external system, the same way Smart Bidding and Performance Max asset rotation always have. A complete record of what happened in an account marks where platform automation ends and where your own approved changes begin, rather than treating the account as a single black box. That's the same principle behind an audit trail for AI-driven ad spend: the record needs to distinguish "the platform did this" from "we decided this," because a finance review or a client conversation will eventually ask which is which.