Google Ads enforced its 37-month granular data retention cutoff on June 1, 2026, and several more deadlines are stacking up fast. Today in Google Ads for June 2, 2026 covers the data retention enforcement now live, the upcoming YouTube auto-link on June 10, API v20's hard shutdown the same day, a major Consent Mode simplification on June 15, AI Max going GA with a forced DSA migration locked in for September, new budget pacing rules already active, and competitive moves from Microsoft Advertising.
As of June 1, 2026, Google Ads no longer retains granular reporting data, including hourly, daily, and weekly breakdowns, beyond a rolling 37-month window. The change is now in effect across the Google Ads API, scripts, the Google Analytics Data API, and the BigQuery Data Transfer Service.
Monthly and annual aggregated data still follows the older 11-year retention window. But for anyone pulling detailed performance breakdowns for year-over-year analysis, anything older than roughly June 2023 is now gone at the granular level.
The most dangerous edge case: manually triggering a GA4 BigQuery backfill for a date older than 37 months can overwrite your existing stored data with empty values. That is not a gap in reporting. It is permanent data destruction. If your BigQuery exports are current and untouched, leave them alone. If they are not, do not attempt a backfill without confirming what is already stored.
As reported by PPC Land, this affects every advertiser, agency, and tool relying on historical Google Ads data. Audit your data pipelines today.
Google announced that starting June 10, 2026, any Google Ads account not already linked to a YouTube channel will be automatically connected. The change removes the manual linking step that many advertisers either skipped or never knew existed.
Once linked, advertisers gain access to organic video metrics directly inside Google Ads and can build audience segments from YouTube engagement, including video views, subscribes, and channel visits. For teams already running YouTube campaigns, this fills a gap that previously required deliberate setup. For a deeper look at running YouTube campaigns effectively, see How To Run YouTube Ads Through Google Ads: The Complete Strategy Guide.
The catch: if you manage separate YouTube channels for different business units or brands and do not want them linked to a particular Ads account, you need to act before June 10. Search Engine Land reported that there is no indication Google will provide a grace period after the deadline.
Agencies managing multiple client accounts through MCC structures should check every account individually. For guidance on managing at scale, Google Ads MCC Management In 2026 covers the operational challenges.
Google Ads API v20 stops functioning on June 10, 2026. Any bidding tool, reporting script, campaign manager, or custom integration still calling v20 endpoints will break silently. There will be no deprecation warning at that point because the deprecation notice was the warning.
This is especially critical for agencies and in-house teams running automated workflows. A single overlooked script pulling data from a v20 endpoint can cascade into missing reports, stalled bid adjustments, or failed campaign launches. As Search Engine Land noted, there is no partial support or fallback. It is a hard cutoff.
The fix is straightforward but non-negotiable: confirm every integration has been migrated to a currently supported API version. If you use third-party tools, check with the vendor directly. If you built custom scripts, audit them now.
Google is simplifying how consent signals flow into Google Ads. From June 15, 2026, Ads data collection will rely solely on the ad_storage consent setting, decoupling entirely from Google Analytics Signals configurations.
This matters because many advertisers unknowingly depended on a layered consent setup where Google Analytics Signals acted as a secondary gate. That layer is being removed. If your consent management platform is properly setting ad_storage when users accept cookies, nothing changes. If it is not, your reporting, attribution, and audience targeting could degrade immediately, and Google Ads will not surface a warning.
As reported by Search Engine Land, this is a clean-up move by Google, but the practical risk sits entirely with the advertiser. Audit your consent banner implementation and verify that ad_storage is firing correctly.
Google officially moved AI Max for Search campaigns out of beta on April 15, 2026, and the clock is now ticking for Dynamic Search Ads. Starting September 2026, campaigns using DSA, automatically created assets, and campaign-level broad match will be automatically upgraded to AI Max. There is no opt-out, and no new DSA campaigns can be created after the migration.
Google claims AI Max delivers an average 7% uplift in conversions at similar CPA and ROAS compared to legacy search-term matching. As announced on the Google Ads Blog, hundreds of thousands of advertisers are already using it.
The practical takeaway: if you are still running DSA campaigns, start testing AI Max now to understand its behavior in your account. Waiting until September means adapting to a new system with no fallback.
Also effective June 1, Google Ads now paces campaigns toward the full monthly budget limit (30.4x daily budget) even when ads are restricted to certain days or hours via ad scheduling. Previously, pacing would scale down to match the number of active days.
This means a campaign with a $100 daily budget running only on weekdays will now target $3,040 in monthly spend, not the roughly $2,200 it would have spent under the old pacing model. Search Engine Land reported the change, and advertisers using limited schedules should adjust daily budgets immediately to avoid overspend.
When Google ships a deadline like the API v20 shutdown, a data retention cutoff, or a consent mode overhaul, most teams find out late and scramble. groas handles it differently. The proprietary engine, trained on over $500 billion in profitable ad spend, updates continuously as Google rolls out changes. API migrations, consent signal adjustments, budget pacing recalculations, and AI Max transitions all get handled before they become problems.
For DFY clients, a dedicated senior strategist owns the entire response. For DWY teams, the strategist flags what changed and what to do on the next call while the engine adjusts underneath. For agencies on the DIY product, the engine adapts automatically across every connected client account. No deadline catches you off guard. No silent failure goes unnoticed. Month-to-month, no long-term contracts.
Today's Google Ads news is dominated by deadlines. The 37-month data retention enforcement is live. API v20 dies in eight days. YouTube auto-linking follows the same day. Consent Mode simplification hits June 15. AI Max's forced DSA upgrade is confirmed for September. And budget pacing already changed under your feet yesterday.
None of these are optional. Each one requires a specific action or a deliberate decision not to act. Check your data exports, audit your API integrations, verify your consent banner, and model your budget pacing under the new rules.
We will be back tomorrow with the next roundup. If you missed yesterday's coverage, catch up on Today In Google Ads: June 1, 2026.
Starting June 1, 2026, Google Ads no longer stores granular reporting data (hourly, daily, weekly breakdowns) beyond 37 months. Monthly and annual aggregated data remains accessible for up to 11 years. The change affects the Google Ads API, scripts, Google Analytics Data API, and BigQuery Data Transfer Service. Critically, triggering a GA4 BigQuery backfill for dates older than 37 months can overwrite your existing historical data with empty values, permanently destroying it. Advertisers should confirm their BigQuery exports are current and avoid backfills that touch data older than June 2023.
Yes. Starting June 10, 2026, Google Ads accounts that are not already linked to a YouTube channel will be automatically connected. This gives advertisers access to organic video metrics and YouTube engagement-based audience segments. If you do not want this auto-link, you must take action before June 10 to opt out. For teams already running YouTube campaigns through Google Ads, the link unlocks additional targeting and reporting capabilities that were previously only available through manual setup.
Every automated system still calling Google Ads API v20 endpoints will stop working entirely on June 10, 2026. There will be no gradual deprecation or warning at that point. Bidding tools, reporting scripts, campaign management platforms, and any custom integrations built on v20 will silently fail. Agencies managing multiple client accounts through MCC structures should audit every integration now. groas monitors API version changes continuously through its proprietary engine, so teams using groas never face silent breakage from deprecated endpoints.
From June 15, 2026, Google Ads data collection will depend solely on the ad_storage consent signal, decoupling from Google Analytics Signals configurations. If your consent banner is misconfigured and does not properly set ad_storage, your reporting, attribution, and audience targeting could break immediately with no dashboard warning. Advertisers should audit their consent management platform settings now and verify that ad_storage is being correctly triggered for users who accept cookies.
AI Max for Search is Google's AI-powered replacement for Dynamic Search Ads, automatically created assets, and campaign-level broad match. It exited beta on April 15, 2026. Starting September 2026, all campaigns using those legacy features will be automatically upgraded to AI Max with no opt-out. Google reports an average 7% conversion uplift at similar CPA and ROAS. Advertisers should begin testing AI Max now to understand its behavior before the forced migration.
groas runs a proprietary engine trained on over $500 billion in profitable ad spend that updates continuously as Google rolls out changes. Whether it is an API version migration, a consent mode shift, or a new budget pacing rule, the engine adapts in real time. Depending on the product, a senior human strategist either owns the response end-to-end (DFY), collaborates with your team on adjustments (DWY), or agencies operate the engine directly (DIY). No deadline catches you off guard, and no silent failure goes unnoticed.
