Google Ads Data Retention Just Dropped to 37 Months: Your Backup Playbook

Google Ads data retention quietly changed on June 1, 2026. If you run lead-gen accounts or report on long-term campaign trends, the window for granular reporting just shrank from eleven years to thirty-seven months. That is not a small adjustment. It is a hard ceiling on what you can pull from the platform going forward, and most operators have not noticed yet.

You need a backup plan. Not next quarter. Now. This guide walks you through what the new Google Ads data retention rule changes, why it hits lead-gen accounts harder than ecommerce, and the six-step export routine you can run this week to protect your year-over-year reporting before the gaps show up in your dashboards.

What the Google Ads Data Retention Change Actually Does

Here is the short version of the Google Ads data retention update. The platform now caps granular reporting at 37 months. Hourly, daily, and weekly metrics older than that window are gone from the interface and the API on June 1, 2026 and after.

The aggregated stuff sticks around longer. Monthly, quarterly, and annual rollups stay for 11 years, according to the official Google Ads data retention policy. So if you only ever pull yearly totals, you barely notice. But if your reporting leans on day-level pacing, week-over-week conversion shifts, or hour-of-day bid modifiers, your historical comparisons just lost their long tail.

Reach and frequency metrics get an even tighter limit. Unique users, average impression frequency, and frequency distribution buckets cap at three years. That hits brand and upper-funnel reporting first. If you build cumulative reach reports for a multi-year flight, your 2022 numbers are about to disappear.

The technical detail of this change matters for anyone running scripts. Google Ads API queries that ask for daily or weekly segments older than 37 months return a DateRangeError starting June 1, as documented in the PPC Land technical breakdown. Your old code does not fail gracefully. It just stops returning rows. Same with BigQuery Data Transfer Service backfill runs older than 37 months. They will refuse to populate. The new rule applies to interface, API, and BigQuery transfers in the same stroke.

Why the Google Ads Data Retention Cut Hurts Lead-Gen More Than Ecommerce

Ecommerce teams already plan around short data windows. They optimize on rolling 28-day or 90-day cohorts. Their attribution is event-rich and decisions move fast. A 37-month ceiling is fine.

Lead-gen is different. You sell roofing jobs, plumbing emergencies, insurance quotes, or replacement windows. The sales cycle can be slow, the conversion event might be a phone call rather than a click, and your media plan often rests on seasonal patterns that go back four or five years.

When you compare this April to April four years ago, you are looking for the cost-per-lead drift in storm season, the click-through gap when a competitor reduces spend, or the seasonality curve that tells you when to push budget. Strip out the day-level data older than three years and a chunk of that signal is gone.

Call-heavy lead-gen accounts get hit twice. Your call tracking platform usually holds its own history, but the join between call outcomes and Google Ads cost and click data depends on Google Ads keeping that granular performance data accessible. Lose it on the Google Ads side and the value of the join falls off after 37 months.

The same squeeze applies to enhanced conversions setups that backfill offline events. The conversion uploads will still work going forward, but the historical reconciliation you might want for a five-year audit just got harder. If your offline imports rely on value-based bidding, audit your training window now.

The Six-Step Google Ads Data Retention Export Playbook

You have one job this week. Pull a clean archive of anything granular you want to keep, then build a routine that exports it monthly going forward. Here is the order that works.

Step 1: Confirm what you actually need. Not every account needs four years of hourly data. List the reports your team rebuilds every year. Year-over-year campaign performance, search term history, auction insights, day-of-week pacing, and hour-of-day bid recommendations are the most common. Anything not on the list does not need a backup.

Step 2: Identify your oldest at-risk data. Open each account, set the date range to four years ago, and pull a campaign-level report at the daily segment. That data is closest to the cliff. If your account has been running since 2021 or earlier, prioritize it first.

Step 3: Export through the Google Ads interface for small accounts. The native report editor lets you build a daily-segmented campaign report and download a CSV. It is slow but free. Repeat per account, per report. Save each CSV to a single folder structure organized by account and quarter.

Step 4: Use Google Ads Scripts for larger portfolios. If you manage more than ten accounts or want a recurring export, write a Google Ads Script that pulls the campaign and keyword performance reports at daily granularity and pushes them into a Google Sheet on a weekly schedule. The script keeps a rolling archive in your Drive without you touching the interface.

Step 5: Set up BigQuery Data Transfer Service before the deadline if you have not already. The Data Transfer Service can backfill historical data into BigQuery, but as of June 1, 2026, backfill runs for dates older than 37 months will return empty. Start any pending backfill now, run it to completion, and then schedule daily incremental loads so you never lose another day of granular data. This is the durable path for any agency that wants a real archive, and it is exactly the BigQuery archive lead-gen advertisers need before the 37-month cap.

Step 6: Document the new ceiling for your team. Add a note to your reporting playbook that any analysis pulling data older than 37 months should explicitly use monthly or quarterly aggregates, not day-level segments. Train the analyst who builds your year-over-year decks. The data is not gone for high-level summaries. It is gone for the daily detail underneath them. You can borrow patterns from our real-time policy review playbook to make this a recurring quarterly check.

What to Tell Your Client About the Google Ads Data Retention Window

You will get questions this month. Some clients read the same announcement you did. Others noticed their custom dashboards started returning errors when they tried to pull a five-year view. Give them the short answer first.

The short answer: nothing the client did wrong. Google capped granular reporting at 37 months on June 1, 2026. Your agency is preserving the data through an external archive. Year-over-year reporting still works. The platform just stopped being the single source of truth for anything older than three years.

Then give them the next step. Tell them which reports you have already backed up, where the archive lives, and how often you refresh it. If you have not started yet, give a timeline. Most lead-gen clients accept the change without pushback when they hear there is a plan that starts this week. If you have Google Ads terms changes coming in July on the same account, bundle this into that update.

The Hidden Risks of Letting the Google Ads Data Retention Clock Run Out

The obvious risk is the missing data itself. There is also a quieter risk that hits later. Three of them, really.

First, attribution model drift. If you use a custom attribution model that trains on multi-year click paths, those models start to skew once the underlying source is truncated. The model still runs, but the training window is shorter than the comparison window, and the outputs drift. Audit your models in the next 90 days and document the data window each one assumes.

Second, lost auction insight history. Auction insights are part of the granular reporting that disappears on the 37-month line. If you compete with a specific advertiser and have been watching their impression share trend for years, you lose the long view. Competitive audit workflows that lean on auction insights need a new home for that historical data.

Third, scripted reporting failures. Any Google Ads Script or third-party tool that queries beyond 37 months returns errors starting June 1. Some of those scripts run silently in the background and feed client-facing dashboards. The dashboard does not crash. It just stops updating the long-range tiles. Find every scheduled script in your stack and confirm it does not request granular data older than the new ceiling. Teams running nightly PPC search term mining should add the same audit to their pipeline checklist. The same pipelines also need to brace for the API v20 sunset and its data-export endpoint changes, which removes legacy endpoints your export jobs may still depend on.

What the Google Ads Data Retention Change Means for the Next 90 Days

The pattern is clear. Google is narrowing the platform’s role as a data warehouse. Reach and frequency cut to three years. Customer Match capped at 540 days last spring. AdMob retention slashed last summer. Now granular reporting at 37 months. Your platform is not a long-term archive anymore. It is a working window.

The agencies that handle this well in the next 90 days look the same in 2027. They have an external archive outside Google Ads. They run incremental loads on a schedule. They train new analysts on the 37-month rule from day one. Their reporting decks include data older than three years because they pulled it out and stored it themselves.

The agencies that ignore it lose a piece of every long-cycle account. They try a four-year retrospective in 2027 and the daily data is gone. They scramble. The client notices.

Pick the path now. The export takes a few hours per account this week, and a few minutes per account every month after. The cost of skipping it is a slow leak in your reporting credibility that you will not see for two or three quarters.

If you want help setting up the BigQuery pipe or running your first batch of exports across a portfolio of lead-gen accounts, book a free consultation. We will walk you through what to pull first and how to structure the archive so it stays useful as the platform keeps tightening the window.

Let’s Grow!