Skip to Content
Sign Up For Code Camp 2026!: June 16-17 Don't miss out, find out more!

Google Data Retention Changes: The Case for Owning Your Own Data Warehouse

DSC 1445
Jeffrey Pinnow
Digital Strategist

The Quiet Email That Just Changed How Marketers Have to Think About Their Data

Why Google's new 37-month data retention policy in Google Ads is the clearest signal yet that the era of "the platform will hold your data for you" is ending — and what marketing leaders should be doing about it now.

If you have a Google Ads account, you likely got an email on May 2, 2026 that you skimmed and filed away. The headline change: Granular reporting data will only be retained for 37 months going forward. probably didn't feel urgent. 37 months is more than three years. That's a lot of runway.

But buried in that email is a meaningful shift in how marketers and sales leaders need to think about their performance data. Read it alongside the other email Google sent the same week, the one about legacy SQL retiring in BigQuery, and a pattern emerges. Google is gently nudging its customers toward a different data architecture. The kind where the platform is no longer the long-term home for your numbers. You are.

Here's what's changing, what it means for marketing and sales organizations, and why this announcement should finally move data warehousing from a "someday" project to a near-term priority.

What the Email Actually Said

The change, which takes effect June 1, 2026, splits Google Ads reporting into two tiers based on how granular it is.

Granular data — anything reported at the hourly, daily, or weekly level, will only be available for the most recent 37 months.

High-level data — monthly, quarterly, and yearly rollups, will stay available for up to 11 years, the same as today.

On the surface that sounds reasonable. Most marketers don't pull hourly data from three years ago. But "granular" is doing a lot of work in that sentence. Daily data is granular. Weekly data is granular. And almost every meaningful question a marketing or sales team wants to answer about long-term performance lives in that granular layer.

Compare daily click-through rates from a 2024 product launch to your current campaign? Granular. See which day of the week historically drives Q4 conversions? Granular. Study the weekly cadence of a competitor-response campaign you ran two years ago? Granular. After June 1, anything older than 37 months gets summarized into monthly totals, and the underlying texture is gone. If you've ever tried to rebuild a story from monthly aggregates, you know it's a different kind of story. Especially in the e-commerce world where annual performance isn’t view by month, its compared by week.

This Isn't an Isolated Change

The Google Ads update is the headline, but it's not happening in a vacuum.

Google Analytics 4 has capped event-level data retention at 14 months since launch in 2023, a sharp departure from Universal Analytics, which allowed indefinite retention. The Explore reports, where most analysts do real in-platform analysis, simply lose access to data older than that window and the ability to connect it to outside visualization loses the same access.

BigQuery is retiring legacy SQL on the same June 1, 2026 date, pushing all customers onto GoogleSQL, the ANSI-compliant standard. A separate change technically, but the timing tells a story. Google is standardizing how customers interact with their cloud data infrastructure on a single deadline.

Looker Studio became Google Data Studio again in April 2026, with Google explicitly repositioning it as the on-ramp for ad-hoc analysis on top of BigQuery, Sheets, and other Google data sources, paired with deeper BigQuery integration including conversational AI agents that query warehoused data directly.

Read those three changes together and the direction is hard to miss. Google's free and mid-tier tools are increasingly designed as views into a warehouse you control, not as the warehouse itself. The company is, in effect, telling its customers: if you want long-term, granular, queryable data, the place for that is BigQuery, or wherever else you choose to build a proper data foundation, but it is no longer free.

Most marketing teams have not been operating that way. They've been operating as if Google Ads, GA4, Search Console, and Meta Ads Manager were the long-term archives. They aren't. They never really were. This announcement just makes it official in a way that's harder to ignore.

Why This Hurts Marketing and Sales Specifically

If you're in finance, you already have a data warehouse. If you're in operations, you probably do too. Marketing and sales are often the last departments in a mid-market organization to formalize their data infrastructure, partly because the platforms have historically been so generous with retention, partly because the cost to a P\&L sheet simply wasn’t worth it when the in-platform retention sufficed

That generosity is what's eroding. A few specific places the 37-month cap will sting:

Long sales cycles get shorter memory. If your business has a multi-month sales cycle, capital equipment and improvements, B2B SaaS, healthcare technology, professional services, you often need to look at touchpoints from three or four years ago to understand what moved a deal. A prospect who first engaged with a whitepaper in 2022 and finally closed in 2026 is exactly the kind of multi-year journey that disappears in monthly summaries where touchpoints become near impossible to plot.

Year-over-year-over-year analysis becomes lossy. "Compare this Black Friday to the last three Black Fridays" is a routine ask in retail and ecommerce. With a 37-month cap, you can do it once or twice and then the earliest comparison year shifts from "I can see the daily curve" to "I have one number for November." The shape of the campaign, when it spiked, when it cooled, how each day of the weekend performed independent to the campaign, is gone.

Attribution and incrementality studies need history. Marketing mix modeling typically wants two to three years of weekly data minimum. A 37-month cap is right at the edge of what's usable, with no margin if your data analyst wants to validate the model against an earlier period, something most enterprise C-suites require.

Sales forecasting loses its longest signal. Forecasts built off historical lead-flow patterns from paid channels will find the underlying inputs quietly thinning. The forecast still runs. The numbers still come out. But the historical comparisons that gave it credibility are now capped at three years of fidelity.

The Other Pressure: Server-Side Tracking and the Slow Death of Browser-Based Measurement

The retention change isn't the only force pushing marketing teams toward owning their infrastructure. There's a parallel shift in how data even gets collected in the first place.

Browser-based tracking is in decline. Third-party cookies are gone or going across most major browsers. Ad-blockers and privacy-focused browsers like Safari and Brave routinely block client-side analytics scripts. In 2025, a German court ruled that simply loading Google Tag Manager in a browser counted as a personal-data processing event under GDPR, requiring prior consent before the script even fires. That ruling didn't single-handedly change global practice, but it accelerated a conversation that was already underway, and in the words of Neil Diamond, it’s Coming to America.

Browser-based measurement is becoming structurally less reliable, not just less accurate.

The industry's answer is server-side tagging. Typically a server-side Google Tag Manager container is hosted in Google Cloud. Yes, the same platform that Google is pushing people to with BigQuery. Instead of the browser sending data directly to a dozen advertising and analytics vendors, the browser sends data to your server, and your server decides what to forward and where. Google's own documentation now positions Consent Mode v2 with server-side GTM as the recommended pattern for advertisers operating under strict consent regimes.

If marketing data is already passing through a server you control, the marginal cost of writing it into a warehouse you control is small, once configured. The marginal benefit, owning a clean, complete, query ready record of every event, is enormous. Server-side tagging and a marketing data warehouse are technically separate decisions. Strategically, they're the same one, like peanut butter and jelly, equally good on their own, but better together.

What the Solution Actually Looks Like

The solution is what people in the analytics community have been saying for years: WAREHOUSE YOUR DATA. All caps required. The longer answer is that, "warehouse your data," hides a lot of decisions. A reasonable starting architecture for a mid-market marketing organization looks like this:

A cloud data warehouse — most commonly BigQuery for organizations already in the Google ecosystem, though Snowflake, Redshift, and Databricks are reasonable alternatives.

Native and middleware connectors — GA4 has a free native BigQuery export. Google Ads can be exported through the Ads Data Hub or third-party connectors. Meta, LinkedIn, HubSpot, Salesforce, and Shopify all have either native connectors or API-based middleware that pipes data on a schedule.

A visualization layer — Google Data Studio (formerly Looker) has a free level that we at Reusser use extensively, but alternatives like Tableau, Power BI, or other BI tools are able on top of the warehouse and let non-technical users explore data without writing SQL.

A governance and access layer — clear rules about who can query what, how access is managed, retention policies for different data types, and how the warehouse stays compliant with GDPR, CCPA, and the growing list of state privacy laws.

Once that foundation is in place, the value compounds. You're no longer asking, "what does Google Ads say happened?" and, "what does GA4 say happened?” You are able to reconcile the multiple sources together and you ask the warehouse one question, and it can answer using all your sources at once. Paid spend joins to organic traffic joins to email engagement joins to CRM pipeline joins to closed revenue. That's the analysis marketing leaders have wanted for years and that platform-bound reporting has never quite been able to deliver.

The Considerations Worth Naming Out Loud

This isn't a drop-everything-and-build-a-warehouse-this-quarter pitch. There are real tradeoffs, and any leader evaluating this should walk in with eyes open.

Cost

BigQuery's free tier covers the first 10 GB of storage and 1 TB of query processing per month, enough for many small and mid-sized businesses to get started without a credit card. Beyond that, costs scale with usage. Most well-architected marketing warehouses are a real but manageable line item, provided schemas and dashboards don't accidentally scan terabytes every time someone opens a report.

Data governance and privacy policy alignment

Centralizing data also centralizes responsibility for it. Who has access? What's the retention policy for raw event data versus aggregated reports? How do you handle a GDPR deletion request that touches a row in a three-year-old export? Your privacy policy probably needs an update too, most are written assuming data lives in vendor platforms and not touched for years or decades. None of these are reasons not to warehouse, but they're questions that need answers before the warehouse gets built.

Technical lift

Setup is more accessible than it was even three years ago. Managed connectors and middleware have brought what used to be a custom engineering project down to something a marketing operations team can stand up in weeks rather than quarters. But "more accessible" isn't "trivial." Schema design, identity resolution across sources, and dashboard architecture all benefit from someone who's done it before.

How Reusser Approaches This With BRUIN

This is the strategic shift Reusser has begun advising clients towards, and it's the reason BRUIN exists. BRUIN: the Business Reporting & User Insights Nexus, is our visualization and reporting platform built on Google Data Studio, designed as the single nexus where a client's data sources come together and are modeled in a simple digestible way anyone from the C-suite to the specialist can understand and leverage strategically. Paid media, organic search, email, CRM, ecommerce, all visualized in one place.

The data is yours. Reusser facilitates the setup of the underlying storage: typically BigQuery, sized and structured to your business, but the warehouse, the data, and the ownership all sit with the client. If you parted ways with us tomorrow, your warehouse would still be yours, your historical data would still be intact, and any BI tool you wanted to point at it would still work. That isn't a marketing line; it's the architecture. No hostage negotiation.

Reusser charges a monthly fee for middleware API management and access to the visualization layer, the part that makes the warehouse useful day-to-day rather than just a place data sits. The middleware keeps connections to Google Ads, GA4, Meta, LinkedIn, and other sources flowing reliably. The visualization layer turns the warehouse into something a marketing director or CEO can open and read. Our analyst support service, available as an add-on, provides strategic interpretation: what the numbers mean and what to do next.

The point of BRUIN isn't to lock you into a Reusser-shaped ecosystem. It's the opposite. It's to make the transition from platform-bound reporting to client-owned infrastructure as low-friction as possible, so when the next Google policy change lands, you're already on the right side of it.

The Bigger Picture

If history is a guide, the Google Ads retention change is unlikely to be the last announcement of its kind. GA4 already has a 14-month cap. Search Console retention has sat at 16 months for a long time. It would be surprising if Google didn't, at some point in the next few years, harmonize retention practices across the broader Google Marketing Platform.

That's not a prediction worth panicking over, it's one worth preparing for. Marketing and sales leaders who treat the May 2 email as the prompt to finally formalize their data infrastructure are going to be fine. The ones who file it away and assume the platforms will keep being the long-term archive are setting themselves up to lose institutional memory in slow motion, three months at a time, until one day someone asks for a five-year comparison and the answer is "we can give you a high level monthly summary."

The platforms aren't your warehouse. They never were. Google is being unusually direct about that now, and the smart move is to listen.

Thinking through what a marketing data warehouse should look like for your business?

Reusser helps marketing and sales leaders move from platform-bound reporting to a data foundation they own. If the May 2 announcement got you thinking about your data strategy, we'd be happy to walk through what a BRUIN setup looks like for your organization. Schedule a consultation or reach out to the team directly.