Google Ads Just Cut Your Data History to 37 Months — Act Before June 1
Google Ads is cutting granular reporting data retention from 11 years to 37 months starting June 1, 2026. Daily, hourly, and weekly campaign data older than 37 months will become permanently inaccessible. Worse: BigQuery Data Transfer Service backfill runs for dates beyond that window will overwrite existing records with null values — destroying data you’ve already exported. WooCommerce store owners who rely on the Google Ads UI for reporting are about to lose years of campaign history. The permanent fix is streaming your own event data to BigQuery via server-side tracking, where you own the retention policy forever.
In this article:
What Google Ads Just Changed — and Why It Matters
Google reversed its own 11-year retention policy with roughly five weeks’ notice. Here’s what the change means for WooCommerce advertisers who’ve never exported a row of data.
On May 1, 2026, Google’s Ads Developer Blog published a policy update that most WooCommerce store owners will never read: starting June 1, 2026, granular reporting data in Google Ads — daily, hourly, and weekly breakdowns — will be retained for only 37 months. The previous window was effectively 11 years, established when Google extended retention in November 2024.
That’s a 97% reduction in accessible history, announced with 31 days’ lead time.
Monthly and quarterly aggregate data survives. But the granular data that lets you analyze which days drove the most revenue, which hours your ROAS peaked, and which weekly patterns repeated across Black Friday seasons — that disappears permanently for any period older than 37 months from the current date.
Google Ads is cutting granular reporting data retention from 11 years to 37 months for daily, hourly, and weekly data starting June 1, 2026 — and the change is not reversible once data ages past the window.
For enterprise advertisers with dedicated analytics teams, this is a managed inconvenience. For the typical WooCommerce store owner who runs Google Ads through the web UI and has never connected to BigQuery, it’s a permanent loss of campaign intelligence they didn’t know they were about to lose.
Exactly What Data You Lose After June 1
Not everything disappears. Understanding the boundary between what stays and what goes determines your export priority.
| Data Granularity | Before June 1 | After June 1 |
|---|---|---|
| Hourly data | Up to 11 years | 37 months only |
| Daily data | Up to 11 years | 37 months only |
| Weekly data | Up to 11 years | 37 months only |
| Monthly data | Up to 11 years | No change — still available |
| Quarterly data | Up to 11 years | No change — still available |
The 37-month window is a rolling window. Every day that passes, one more day of granular data ages out. Data from January 2024 is accessible today. By July 2026, it won’t be. By December 2026, everything from February 2024 and earlier will be gone from the granular view.
This affects every reporting endpoint that returns date-segmented data: the Google Ads API, Google Ads scripts, the web UI’s custom date ranges, and — critically — the BigQuery Data Transfer Service.
You may be interested in: Your YouTube Shorts Traffic Shows as Direct in GA4 Because the Links Have No UTM
The BigQuery Backfill Trap That Destroys Your Existing Data
If you already export Google Ads data to BigQuery, the retention change doesn’t just block new exports — it can destroy the historical data you already have.
Here’s the thing. The BigQuery Data Transfer Service (DTS) runs scheduled exports that pull Google Ads reporting data into BigQuery tables. When you need to fill gaps, you run a backfill — a one-time export for a specific date range. Before June 1, that backfill can reach back 11 years.
BigQuery Data Transfer Service will permanently block backfill runs for dates older than 37 months — and manual backfills after the deadline will overwrite existing BigQuery records with empty null values, destroying data you already exported.
Read that again. If you already have Google Ads data in BigQuery from 2023 and you accidentally trigger a backfill for that date range after June 1, the DTS won’t skip the request. It will run the backfill, receive empty data from Google Ads (because the granular data no longer exists), and write null values over your existing records. Your historical data doesn’t just become unavailable — it gets actively overwritten.
The mitigation is straightforward but time-sensitive: run a full backfill for all historical data before June 1, then disable automatic backfills for date ranges older than 37 months. After June 1, treat any BigQuery table containing pre-January-2024 Google Ads data as read-only. Do not run backfills. Do not let scheduled jobs overwrite historical tables.
Two Shrinking Windows — Google Ads and GA4 Together
Google Ads isn’t the only retention window getting smaller. GA4’s free tier keeps only 14 months. The combination means WooCommerce stores face two compounding data cliffs.
GA4’s free tier retains event-level data for 14 months. The paid tier (Analytics 360) extends that to 50 months. Google Ads now caps granular data at 37 months. If you’re a WooCommerce store running Google Ads with GA4 free tier, your longest accessible history is 14 months for site behavior and 37 months for campaign data. Year-over-year analysis across both datasets requires at least 24 months. You have a 10-month buffer on ads data and negative headroom on analytics.
GA4’s BigQuery streaming export — the recommended way to preserve analytics data beyond the 14-month window — costs $0.05 per GB and still lacks traffic_source attribution data for new users, which means attribution models built on GA4 BigQuery exports are structurally incomplete even when retention is solved.
73% of GA4 implementations already lose 30-40% of conversion data to privacy restrictions. That incomplete data now flows into a shrinking retention window. You’re keeping less data for less time, and the data you keep is already missing 30-40% of the signal.
| Data Source | Free Retention | Paid Retention | Your BigQuery |
|---|---|---|---|
| Google Ads (granular) | 37 months (NEW) | 37 months (same) | Unlimited — you control it |
| GA4 event data | 14 months | 50 months (360) | Unlimited — you control it |
| Server-side events | N/A — not in Google | N/A | Unlimited — your own pipeline |
The pattern is unmistakable. Every Google data product is tightening retention. The only row in that table with “unlimited” is the one where you own the infrastructure.
You may be interested in: Your WooCommerce Lead Gen Data Lives in Five Systems — One BigQuery Fix
What to Export Before the Deadline
A practical priority list for WooCommerce store owners who have never exported Google Ads data — ordered by what you’ll regret losing most.
Priority 1: Daily campaign performance. Export every campaign’s daily metrics — impressions, clicks, conversions, cost, conversion value — for the full available history. This is the data you use for year-over-year comparisons and seasonal planning. Use Google Ads scripts to automate the export to Google Sheets or BigQuery. The Google Ads API’s reporting endpoint supports date ranges going back to the full retention window — but only until June 1.
Priority 2: Daily keyword and search term data. Search term reports at the daily level show which queries drove conversions and when. This is irreplaceable for seasonal keyword analysis. After June 1, you’ll only see monthly aggregates for terms older than 37 months — too coarse for bid strategy decisions.
Priority 3: Hourly data for high-value periods. If your WooCommerce store runs time-sensitive promotions (Black Friday, flash sales, seasonal launches), hourly data for those periods shows exact conversion timing patterns. Export hourly breakdowns for every major promotional period in your history.
Priority 4: BigQuery Data Transfer Service backfill. If you already use DTS, run a complete backfill immediately for all available historical dates. After June 1, mark every pre-2024 BigQuery table as read-only and remove any scheduled backfills that could overwrite them.
The Permanent Fix: Own Your Data in BigQuery
Exporting before the deadline saves your past. Streaming events to your own BigQuery dataset saves your future.
The June 1 deadline is a symptom. The underlying condition is dependency on platform-controlled data. Google Ads can change retention windows. GA4 can cap its free tier. Meta can restructure its reporting API. Every platform owns the data in their system. The only data you truly own is the data in yours.
Server-side tracking solves this permanently. When your WooCommerce store streams every event — page views, add-to-cart actions, purchases, attribution data — directly to your own BigQuery dataset, the data arrives in real time and stays forever. No retention window. No backfill risks. No dependency on any platform’s policy decisions.
Transmute Engine™ streams WooCommerce events to BigQuery through a first-party server-side pipeline. Every conversion, every attribution signal, every behavioral event lands in your dataset the moment it happens — and it stays there under your retention policy, not Google’s.
The math is simple. Google’s retention windows will continue shrinking. Your data needs will continue growing. The stores that build their own data infrastructure now won’t need to react to the next announcement. They already own everything.
You may be interested in: First-Party Event Collection for WooCommerce: The Complete Vendor Landscape 2026
Key Takeaways
- June 1, 2026 is the hard deadline: Google Ads granular data (daily, hourly, weekly) older than 37 months becomes permanently inaccessible. Monthly and quarterly aggregates remain.
- BigQuery backfills become destructive: After June 1, backfill runs for dates beyond 37 months will overwrite your existing BigQuery records with null values. Mark historical tables as read-only.
- GA4 compounds the problem: With only 14 months of free retention and incomplete attribution in BigQuery exports, WooCommerce stores face two shrinking windows simultaneously.
- Export now, in priority order: Daily campaign performance first, then keyword/search term data, then hourly data for high-value periods. Use Google Ads scripts or the API before the window closes.
- The permanent fix is owning your data: Server-side tracking to your own BigQuery dataset removes dependency on any platform’s retention policy. Google’s windows shrink. Yours don’t.
Daily, hourly, and weekly granular reporting data older than 37 months becomes permanently inaccessible. Monthly and quarterly aggregate data remains available. If you need to analyze campaign performance at the daily level for any period before January 2024, you must export that data before June 1, 2026.
Use Google Ads scripts to automate daily-level exports to Google Sheets or BigQuery. The BigQuery Data Transfer Service can backfill historical data, but only for dates within the 37-month window. For data older than 37 months, run the backfill before June 1 — after the deadline, backfill attempts will overwrite your existing BigQuery records with null values.
Yes. Monthly and quarterly aggregate data is not affected by the 37-month policy. The restriction applies only to granular data: daily, hourly, and weekly breakdowns. If you only need monthly trends, your historical reporting survives. If you need daily-level campaign analysis for year-over-year comparisons, that data must be exported before the cutoff.
BigQuery has no automatic data deletion policy. Once data lands in your BigQuery dataset, it stays until you delete it. You control the schema, the retention period, and the access rules. Google Ads data lives in Google’s system under Google’s rules — and those rules just changed with five weeks’ notice.
Server-side tracking streams every WooCommerce event — page views, add-to-cart, purchases, attribution data — directly to your own BigQuery dataset in real time. This data is independent of Google Ads, GA4, or any platform’s retention policies. When any platform changes its retention window, your data is already in your warehouse with unlimited history.
References
- Google Ads Help Center — Data Retention Policy Update (2026)
- Google Ads Developer Blog — New Data Retention Policy (Nadine Wang, May 2026)
- PPC Land — Google Ads Cuts Granular Data Access to 37 Months (2026)
- Surfside PPC — Google Ads Reduces Data Retention (2026)
- Calibrate Analytics — 37-Month Limit for Historical Data (2026)
- Google Analytics Help — Data Retention Settings
- Seresa — Why Your GA4 Attribution Is Wrong (SR Analytics data, 2025)
Ready to stop depending on Google’s shrinking data windows? Talk to Seresa about streaming your WooCommerce events to BigQuery — where your data stays as long as you need it.