Five platform deadlines that land inside your next plan

Most marketing plans are written around campaigns. The things that will actually disrupt the next twelve months are platform changes with dates attached, and they rarely appear in the document at all.

Here are five. Two have hard dates, two have already landed and are probably unaudited in your account, and one is a migration you should be tracking inside your own interface. Each needs a name against it.

September 2026: the AI Max auto-upgrade

Google begins auto-upgrading campaigns to AI Max for Search from September 2026 if they use Automatically Created Assets or the campaign-level broad match setting. New Dynamic Search Ads campaign creation ends at the same point.

The trap is the trigger. Teams have the DSA transition in a calendar and have missed that automatically created assets and campaign-level broad match pull you into the earlier group whether or not you have ever run a DSA campaign.

Owner: whoever runs paid search. Do before September: list which campaigns use those two settings; decide whether to upgrade on your terms or be upgraded on Google's; trim heavy negative keyword lists, because Google's own guidance says to use negatives sparingly under AI Max so you do not filter the matched traffic; and move search term review to a fortnightly rhythm.

Worth knowing what you are getting. Google's cited result for the full suite, search term matching plus text customisation plus final URL expansion, is 7 per cent more conversions or conversion value at similar cost per acquisition against search term matching alone. Final URL expansion means the machine picks the landing page, so audit your pages before it does.

February 2027: the remaining DSA sweep

The mandatory auto-upgrade for remaining Dynamic Search Ads campaigns lands in February 2027, extended from an earlier date. If you have DSA campaigns that survive September, this is when they go.

Owner: paid search. Do before February: decide which DSA campaigns are worth carrying across as structured AI Max campaigns and which should be retired. A campaign that has been running unattended for two years is not a candidate for automatic migration, it is a candidate for deletion.

Already landed, 15 June 2026: the GA4 consent split

This one is behind you and almost certainly unaudited.

The ad_storage signal is now the sole control over whether GA4 shares cookies and identifiers with linked Google Ads accounts. The Google Signals toggle in Admin, Data Settings only controls signed-in behavioural reporting: demographics, interests, cross-device.

Two ways to be wrong. Accounts with Signals off but ad_storage granted now collect more than intended, because the backstop is gone. Accounts that relied on Signals being on while ad_storage defaulted to denied are quietly losing Ads data.

Owner: analytics. Do this week: DevTools, Network tab, filter google-analytics.com, compare the gcs parameter and the gcd parameter on a reject and an accept. Do not use Tag Diagnostics, it lags 48 to 72 hours. Server-side tagging flows are unchanged by this update.

Already landed, July 2026: Privacy Sandbox removal

Google announced on 17 October 2025 that it is retiring the remaining Privacy Sandbox APIs, with deprecation in Chrome 144 in January 2026 and removal in Chrome 150 in July 2026. That covers Attribution Reporting, Topics, Protected Audience, IP Protection, Related Website Sets, Shared Storage, Private Aggregation, Protected App Signals and SDK Runtime. Third-party cookies remain enabled by default in Chrome under a user-choice model, following the April 2025 decision not to ship a standalone prompt.

Owner: analytics. The action is a deletion. Any workstream in your roadmap about Sandbox readiness or cookie deprecation contingency comes out, and the hours move to first-party server-side collection, enhanced conversions and offline conversion import. That is the durable signal now, and it always was.

If your agency is still presenting a slide about the cookieless future, it is a two-year-old slide.

Tracked in your own account: the Display and data connection migrations

Two more shifts do not have a public date you can put in a plan, which is exactly why they get missed.

Google has been consolidating Display into Demand Gen, and the upgrade notices appear at campaign level in your account rather than in a press release. Separately, the connection layer for conversion and customer data is being consolidated into Data Manager, which changes who sets up and owns those connections.

Owner: paid media plus analytics jointly. Do monthly: open the notifications and recommendations surface in Google Ads, read the campaign-level upgrade notices, and log any with a date. Confirm who in your business, not your agency, has admin on the data connections. A migration completed by an agency account that later leaves is a migration you will redo.

How to use this list

Put the five in your plan as line items with a name and a month next to each. Then add one recurring calendar entry, once a month, thirty minutes, to read the platform notices in your own accounts.

The changes that hurt are never the ones that were announced loudly. They are the ones that were announced quietly to an account nobody was watching.