Google Ads Management Needs DSA Baselines Before AI Max

Google restored DSA creation and moved automatic upgrades to February 2027. Good Google Ads management should use that window to preserve query, URL-rule, and exclusion baselines before AI Max changes the account's behavior.

What This Means: The Practical Takeaway

Google's June 11, 2026 DSA update buys managers more time, but the real opportunity is not delay. It is evidence. With DSA creation returning on June 15 and auto-upgrade pushed to February 2027, good teams should freeze their search-term patterns, URL rules, and exclusion logic now so AI Max can be judged against a baseline they trust. If that baseline is missing, every migration result becomes harder to explain.

The Timeline Change Creates A Management Window

Google said on June 11, 2026 that DSA automigration moves to February 2027 and that new DSA campaign creation returns on June 15. Google also told advertisers not to wait for the automatic upgrade. It recommended account audit, side-by-side testing, and voluntary upgrade tools.

That is the part managers should notice first.

This update is not just more time.

It is one more clean window to decide what the current DSA setup is actually worth before AI Max changes the matching and landing-page behavior around it.

Why Waiting Quietly Is The Risk

Dynamic Search Ads are useful because they expose search demand keyword campaigns miss. They are also messy in exactly the places managers need to remember during migration: which query classes were productive, which URL paths over-expanded, which exclusions carried the account, and where discovery traffic was only pretending to be commercial.

If that evidence stays trapped inside memory, teams will still migrate.

They just will not know what they are comparing against.

Good [Google Ads management](/articles/google-adwords-management) Should Freeze The Baseline First

Before any DSA account moves to AI Max, managers should save four things:

- the search-term baseline that shows which query themes were useful, borderline, or waste - the URL-rule and page-target logic that shaped where DSA was allowed to land - the exclusions and negatives that kept broad discovery from turning into expensive drift - the parity checks that define what a safe migration would have to preserve

That list is more useful than a generic migration checklist because it gives the account a before-state.

Without that before-state, AI Max gets the credit or blame for changes nobody can untangle later.

Google's Own Guidance Points To Controlled Comparison

The developer blog explicitly recommends auditing accounts, running side-by-side testing, and using voluntary upgrade tools. The Ads & Commerce update also says upgrade tools are meant to port historical settings and data into new standard ad groups.

That support is helpful.

It does not replace management discipline.

A ported setup still needs a documented baseline. AI Max also brings search term matching, text customization, and final URL expansion. If the account does not know what DSA was doing before those controls widen, the test is already weaker than it looks.

The Better DSA Migration Standard

Managers should not ask only whether AI Max lifts conversions.

They should ask:

- did high-value query themes survive the transition - did low-fit search demand expand faster than useful demand - did landing-page behavior stay inside acceptable URL boundaries - did the same exclusions still matter, or did the migration surface new waste patterns - did the account gain scale without losing explainability

That is the standard that turns a platform migration into an actual management decision.

Why This Matters For AdgOptz

AdgOptz is strongest where search demand needs structure before teams act on it. A DSA-to-AI Max change is exactly that moment. The migration should be judged through query intent, exclusion history, and landing-page fit, not only through topline output after the fact.

When the baseline is preserved, teams can tell whether AI Max improved the account or simply changed what the account could match. That is the difference between optimization and guesswork.

How To Do It

Copy this prompt into ChatGPT or Claude:

```text You are a senior Google Ads manager preparing a Dynamic Search Ads account for AI Max migration. I need a practical baseline-preservation workflow before DSA creation returns on June 15, 2026 and before automigration begins in February 2027. Use my search-term exports, URL rules, page targets, negative-keyword lists, landing pages, and recent performance notes to build a checklist that freezes the current DSA baseline, groups queries into keep/watch/block lanes, records landing-page and exclusion logic, and defines parity checks so I can compare AI Max against the original DSA behavior without losing control. ```

Sources

- [Google Ads Developer Blog: Dynamic Search Ads (DSA) Automigration Delayed to February 2027 and Campaign Creation Restored](https://ads-developers.googleblog.com/2026/06/dynamic-search-ads-dsa-automigration.html)

- [Google Ads & Commerce Blog: We're upgrading Dynamic Search Ads to AI Max](https://blog.google/products/ads-commerce/dsa-upgrade-to-ai-max-2026/)

- [Google Ads Help: About Dynamic Search Ads](https://support.google.com/google-ads/answer/2471185?hl=en)

- [Aira: The Beginner's Guide to Google Dynamic Search Ads (DSA)](https://aira.net/blog/beginners-guide-to-google-dynamic-search-ads-dsa/)

- [SavvyRevenue: DSA to AI Max: A Pragmatic Guide to Migrating Without Breaking Your Account](https://savvyrevenue.com/blog/dsa-to-ai-max-migration/)

- [WordStream: Dynamic Search Ads: Everything You Need to Know](https://www.wordstream.com/blog/ws/2023/07/10/dynamic-search-ads)