Google Analytics Data Retention Settings Explained

Buried in GA4's admin settings is a single dropdown that quietly controls how long a specific slice of your data sticks around — and it trips up a lot of people, because it sounds like it should control everything, but it actually only affects a narrower category of data than most assume. Understanding exactly what this setting does (and doesn't do) matters both for privacy compliance and for making sure your longer-term historical analysis doesn't quietly disappear.

Where to Find the Setting

1. Go to Admin.
2. Under Data collection and modification, click Data settings, then Data retention.
3. You'll see a dropdown labeled Event data retention, with two options: 2 months or 14 months.

New GA4 properties default to 2 months, which surprises a lot of people migrating from Universal Analytics, where data was effectively kept indefinitely. It's worth checking and changing this setting immediately after creating a new property.

What This Setting Actually Controls

This is the critical nuance: the retention setting only affects user-level and event-level data used in Explorations and certain user-scoped reports — specifically, data tied to individual users and events that powers things like:

• Free-form Explorations with granular breakdowns
• Certain audience and cohort analysis features
• Some advanced segmentation

It does not affect:

• Standard aggregated reports (Acquisition, Engagement, Monetization, etc.) — these retain historical trend data indefinitely, regardless of this setting.
• Aggregated data used in the standard dashboard cards and charts — you can still see a 2-year trend line for total users even with retention set to 2 months.

In other words, changing this setting to 2 months does not mean your GA4 property "forgets" your site's history after 60 days — it means the fine-grained event-level data needed for certain detailed explorations expires after that window.

Why Google Defaults to 2 Months

The short retention default reflects a privacy-by-design posture — since event-level data can, in aggregate, be more identifying of individual behavior patterns than rolled-up trend data, defaulting to a shorter retention window limits how long that more granular data persists. It's a sensible default for privacy, but it's not necessarily the right choice for every business's analytical needs.

Changing the Retention Period

1. Go to Admin → Data Settings → Data retention.
2. Change Event data retention from 2 months to 14 months (the maximum available for standard GA4 properties; Google Analytics 360 accounts can configure longer periods).
3. Save.

This change is not retroactive — it only affects how long newly collected data is retained going forward. Data that has already aged out under the previous shorter setting is gone and cannot be recovered by extending the retention period afterward.

Resetting on New Activity

There's a second toggle worth knowing about: Reset user data on new activity. When enabled, a user's retention window resets every time they trigger a new event, rather than counting down strictly from their first-ever recorded activity. For most sites, leaving this on is reasonable — it means an actively engaged, returning user's data doesn't age out just because their first visit happened many months ago.

Working Around the Retention Limit for Long-Term Analysis

If your business genuinely needs event-level detail beyond 14 months — for long-term cohort analysis, year-over-year user-level comparisons, or detailed historical audits — the standard fix is to export raw event data into BigQuery, where retention is entirely under your control (and typically far cheaper to store long-term than most people expect for moderate traffic volumes):

1. Go to Admin → BigQuery Links.
2. Click Link, choose or create a BigQuery project, and configure daily (and optionally streaming) export.
3. Once linked, raw event data flows into BigQuery indefinitely, independent of GA4's own retention setting, giving you full control over how long you keep it and how you query it.

How Retention Interacts With Privacy Requests

Data retention settings are related to, but distinct from, user-level deletion requests under regulations like GDPR's "right to be forgotten." If a specific user requests deletion of their data, that's handled separately through the User Deletion API, which lets you submit a deletion request for a specific client ID or user ID, rather than relying on the general retention window to eventually age their data out naturally. Retention settings control the default lifecycle of data; the deletion API handles specific, on-demand removal requests.

A Practical Recommendation for Most Sites

For the overwhelming majority of businesses without a specific reason to keep the shorter default, setting retention to 14 months (the maximum available on standard GA4) is a reasonable default choice. It gives you enough historical depth to build meaningful year-over-year Explorations (since 14 months covers a full year plus a buffer) without needing to set up a BigQuery export just to answer basic historical questions. Only businesses with unusually long consideration cycles, or a specific need to analyze cohorts older than 14 months in detail, typically need to go further and set up a BigQuery link.

Checking Your Current Setting Right Now

If you've never explicitly looked at this setting, it's worth checking today — new GA4 properties still default to the shorter 2-month window, and it's one of the few settings that's easy to overlook entirely since nothing in the interface actively warns you that granular historical data is expiring in the background.

FAQ about Google Analytics Data Retention Settings

Does the 2-month default delete my standard reports after 2 months?

No — standard aggregated reports (Acquisition, Engagement, and similar) retain historical trend data regardless of this setting. Only certain user- and event-level data used in Explorations is affected.

What's the maximum retention period available in standard GA4?

14 months is the maximum for standard (non-360) GA4 properties. Google Analytics 360 customers can configure longer retention periods.

If I change retention from 2 to 14 months, will my old data come back?

No — the change only applies going forward. Data that already aged out under the shorter setting cannot be recovered.

Why would a business intentionally choose the shorter 2-month retention?

Some organizations, particularly those with strict internal privacy policies or operating in tightly regulated industries, intentionally choose shorter retention to minimize how long granular user-level data persists, even beyond what's legally required.

Does BigQuery export bypass the GA4 retention limit entirely?

Yes — once event data is exported to BigQuery, its retention is controlled entirely by your BigQuery dataset settings, independent of the GA4 property's own retention configuration.

Does changing retention settings require re-verifying tracking code?

No — retention settings are a configuration change only and have no effect on how tracking code or tags fire; no re-implementation is needed.

Conclusion

The data retention setting in Google Analytics is one of the most misunderstood toggles in the entire platform — narrower in scope than it sounds, but still worth setting deliberately rather than leaving on the short default. Extend it to 14 months if you rely on Explorations for historical analysis, and consider a BigQuery export if your website's business genuinely needs event-level data retained even longer.