.png)
Google's Consent Mode overhaul went live on June 15, 2026, stripping out the GA4 Signals override and making ad_storage the sole gate for advertising data flowing to Google Ads. That is the biggest change landing today. Alongside it: Google pushed the DSA-to-AI Max forced migration to February 2027, the limited ad serving policy now covers Search, PMax gets new A/B experiment types, and the API v20 sunset is already breaking laggard accounts. Here is everything that matters for your Google Ads account this Monday, June 16, 2026.
As of June 15, Google Consent Mode now treats ad_storage as the single, binary control for whether advertising data reaches Google Ads. The previous dual-gate system, where GA4 Google Signals settings could independently pass some advertising data even when Consent Mode restricted it, is gone.
This is a meaningful shift for any advertiser relying on GA4-fed audiences or conversion data in Google Ads. If your consent banner sets ad_storage to denied for a session, that session is invisible to Ads. No remarketing list inclusion. No conversion attribution. No signal override from GA4.
As reported by UniConsent and The Drum, the change was announced in April but enforcement began yesterday. What to do now:
We covered the initial implications of this change in yesterday's roundup. Today it is live, and the measurement impact starts showing up in your data this week.
Advertisers who were bracing for a September 2026 hard cutover from Dynamic Search Ads to AI Max now have significantly more runway. As reported by Search Engine Land, Google has extended the timeline:
The destination has not changed. DSA is being replaced by AI Max. But the pace has slowed. This matters for advertisers who have complex DSA structures with extensive negative keyword lists, custom landing page feeds, or tight category targeting that needs careful translation into AI Max's more automated format.
The smart move is to use the voluntary window to run parallel tests. Stand up an AI Max campaign alongside your DSA campaigns, compare performance on matched traffic segments, and document where AI Max under-delivers so you can flag gaps before the forced migration.
Google announced on June 12 that its limited ad serving policy, which previously applied to YouTube and other ad surfaces, now extends to Search results pages. Enforcement began this month and will phase in fully through 2028.
The policy creates a qualification tier for newer or unverified advertisers. Until an account builds enough trust history, Google may restrict its ability to serve ads on Search. For established accounts with clean histories, near-term impact should be minimal. But the expansion to Search, the core of most performance budgets, signals that Google is tightening identity and trust requirements across all inventory.
As reported by PPC Land, the phased enforcement timeline means the real bite comes later. Still, advertisers launching new accounts or new brands should factor in a ramp-up period where impression volume may be constrained.
Google expanded native asset experimentation in Performance Max on June 8, adding new experiment types that let advertisers compare asset groups, test individual asset additions, and pit seasonal creative against evergreen content in structured A/B tests.
As reported by Search Engine Land, the capability originated as a retail-only beta in October 2024, broadened to all PMax campaign types in January 2026, and this June 8 update adds the new experiment types. Constraints remain: only one experiment per campaign at a time, and asset groups lock once a test starts.
This is a direct improvement for advertisers frustrated by PMax's opacity around creative performance. Structured experiments give you cleaner reads on which assets actually move results, rather than relying on Google's automated asset selection and the often unhelpful asset performance labels.
Google Ads API v20 stopped accepting requests on June 10. Any advertiser or agency that has not migrated to a supported version is now operating with broken automation: bidding scripts, reporting pipelines, and campaign management workflows are all affected.
As reported by Search Engine Land, this is not a warning. It already happened. If you are seeing unexplained data gaps or stalled bid adjustments, an unsupported API version is the likely culprit. The fix is to upgrade immediately to a supported version and backfill any data gaps from the downtime window.
Platform changes like the Consent Mode overhaul, API sunsets, and new PMax experiment types hit every advertiser at once. The difference is how fast you absorb them. The groas engine, trained on over $500 billion in profitable ad spend, processes these shifts continuously. When Google rewrites the rules on a Sunday, the engine adapts before your Monday morning.
For DFY clients, a dedicated senior strategist owns the response end to end: auditing consent implementations, migrating API versions, structuring new PMax experiments, all without a single Slack message from you. DWY clients get the same engine plus a strategist working alongside their in-house team. Agencies on DIY connect unlimited client accounts and run the engine themselves. No long-term contracts, $0 onboarding, cancel anytime.
If you want to stop scrambling every time Google ships a change, apply for DFY or get started with DWY.
The Consent Mode overhaul is the item that needs action this week. Audit your consent implementation, watch your conversion and audience data, and do not assume GA4 Signals is still filling gaps, because it is not. The DSA extension gives you breathing room but not an excuse to delay testing. And if you have not migrated off API v20, that is an emergency.
We will be back tomorrow with the next roundup. See you then.
Google removed the ability for GA4 Google Signals settings to override ad_storage consent decisions in Consent Mode. Before June 15, advertisers had a dual-gate system where Signals could still pass some advertising data even when Consent Mode restricted it. Now ad_storage is the single control: granted or denied, with no workaround. This directly affects conversion campaigns, remarketing audiences, and any account feeding GA4 data into Google Ads. Advertisers should audit their Consent Mode implementation immediately and verify that consent banners are correctly setting ad_storage to granted for users who opt in.
Google has pushed the forced Dynamic Search Ads to AI Max migration to February 2027. A voluntary testing window runs from June 2026 through January 2027, and new DSA campaign creation ends in January 2027. The original timeline had pointed to a September 2026 hard cutover. The end destination has not changed: AI Max will fully replace DSA. Advertisers should use the extended window to run structured tests rather than waiting for the automatic migration.
Google's limited ad serving policy restricts how new or unverified advertisers can serve ads until they build trust with the platform. Previously applied to YouTube and other surfaces, Google expanded it to Search results pages starting June 2026, with full enforcement phasing in through 2028. In practice, newer advertiser accounts may see reduced impression volume on Search until they clear qualification thresholds. Established accounts are unlikely to feel immediate effects, but the policy signals tighter identity and trust requirements ahead.
groas runs a proprietary engine trained on over $500 billion in profitable ad spend. When Google ships changes like the Consent Mode overhaul, API sunsets, or new PMax experiment types, the engine adapts continuously. For DFY clients, a dedicated senior strategist handles everything end to end, so advertisers never scramble to react. DWY clients get the same engine plus a strategist working alongside their in-house team. Agencies on DIY access the engine directly and apply updates across unlimited client accounts. The result is that platform changes get absorbed the moment they go live, not weeks later.
Yes. Google is enforcing a 37-month data retention window starting June 2026. Any reporting data older than 37 months is being deleted. If you rely on historical data for year-over-year trend analysis, compliance, or benchmarking, you should export it immediately using the Google Ads interface or API. Once deleted, there is no recovery. This is especially important for accounts with multi-year histories used for seasonal planning.
Google expanded PMax asset experimentation on June 8, 2026. Advertisers can now compare new asset groups against existing ones, test individual asset additions, and run seasonal creative against evergreen content in structured A/B tests. Only one experiment can run per campaign at a time, and asset groups lock once a test begins. This gives advertisers more structured ways to validate creative changes before committing, rather than relying on Google's automated asset selection alone.
