GA4 data retention: the setting that is quietly deleting your data
GA4 defaults to a short retention window for the granular data behind explorations. If you have never changed it, you may be losing year-over-year analysis you assume is there.
GA4's event-level data retention defaults to two months on a standard property, and it can be raised to fourteen. Anything past the window is deleted permanently — not archived, not recoverable. Aggregate reports keep working, so nothing appears broken, but the moment you try to build an exploration comparing this year to last, the older half is simply gone. This is a two-click setting that most properties never touch, and the cost of missing it is unrecoverable.
What actually gets deleted
The distinction that matters: user- and event-level data expires; aggregated standard reports do not.
So after the retention window:
- Standard reports still show historical totals. Sessions, users, conversions by month, going back years.
- Explorations cannot reach past the window. Funnels, path analysis, cohorts, segment comparisons — all of these query event-level data.
- Custom dimension breakdowns disappear beyond the window.
- Audience definitions based on older behaviour stop finding those users.
The practical experience is a report that renders with a suspiciously flat or empty older section, which people usually attribute to a tracking problem rather than to retention.
Change it now, not later
Admin → Data settings → Data retention → Event data retention → 14 months.
Also enable Reset user data on new activity, which extends retention for users who keep coming back rather than expiring their history on a fixed clock.
Two reasons to do this immediately:
- It is not retroactive. Raising the window does not resurrect deleted data. Anything already past two months is gone.
- It costs nothing. There is no charge and no downside to the longer window on a standard property.
If your property has been running for a year at the default, you have already lost ten months of event-level detail. Change the setting anyway — the next fourteen months are worth having.
Why fourteen months matters specifically
Fourteen months is the smallest window that supports a genuine year-over-year comparison with the month either side for context. Thirteen would technically compare, but leaves no margin for a partial month or a late analysis.
If you need longer than fourteen months — and any business with seasonality or multi-year cohort questions does — the standard property cannot give it to you. That is what the BigQuery export is for: raw events, kept as long as you pay for storage, entirely outside GA4's retention policy.
| Need | Solution |
|---|---|
| Explorations over the last year | 14-month retention |
| Year-over-year with context | 14-month retention |
| Multi-year cohorts or seasonality | BigQuery export |
| Compliance-driven deletion | Shorter retention, deliberately |
The compliance side
A shorter retention window is sometimes the correct choice rather than an oversight. If your privacy posture or legal advice calls for minimising personal data retention, two months may be the deliberate answer — and pairing it with a warehouse export would defeat the purpose.
The point is that it should be a decision with a rationale, not a default nobody noticed. Document whichever way you go.
What to do if you have already lost data
Honestly: not much within GA4.
- Deleted event-level data is unrecoverable. No support request retrieves it.
- Aggregate reports remain, so high-level historical trends are still available.
- Enable BigQuery export now. It is not retroactive either, but every day you delay is another day of history you will not have.
- Export what you can while it exists. If something in the current window matters for a future comparison, extract it to a spreadsheet or warehouse now rather than assuming it will be there.
How to work out what you have already lost
Before assuming the worst, check what your property is actually set to and what that means in practice:
- Read the current setting. Admin → Data settings → Data retention. If it says two months, every exploration you build is silently limited to the last two months of event-level data regardless of the date range you select.
- Test the boundary. Build a simple exploration — any dimension, any metric — and set the date range to twelve months ago. If it returns nothing while the equivalent standard report shows healthy numbers, you have confirmed the limit rather than a tracking failure.
- List what depended on it. Cohort analyses, year-over-year funnel comparisons, audience definitions reaching back more than two months. Each of those has been quietly returning partial answers.
The third step is the one worth doing carefully, because reports that silently return less data than you asked for are more dangerous than reports that error. Nobody double-checks a chart that rendered.
While you are in that settings screen
Two adjacent settings are worth checking at the same time, since they belong to the same category of things nobody looks at:
- Google signals data collection, if still enabled anywhere in your configuration.
- Data filters — internal traffic and developer traffic filters, and specifically whether any are still sitting in Testing mode and therefore doing nothing. Filtering bot traffic covers this properly.
FAQ
What is GA4's default data retention?
Two months for event-level data on a standard property. It can be raised to fourteen months at no cost, and doing so is the right default for almost every property.
Is GA4 data retention retroactive?
No. Raising the window preserves data going forward; anything already deleted is gone permanently. This is why changing it early matters.
Does data retention affect my standard reports?
No. Aggregated standard reports continue showing historical data. Retention limits explorations, funnels, path analysis, and anything else that queries event-level data.
How do I keep GA4 data longer than 14 months?
Enable the BigQuery export. Raw events stored there are outside GA4's retention policy and persist as long as you keep paying for storage.
Should I ever choose a shorter retention window?
Yes, if data minimisation is a deliberate part of your privacy posture. Make it a documented decision rather than an unnoticed default.
While you are auditing settings, confirm the collection side is healthy: the free tracking audit checks GA4 presence, duplicate properties, and consent signals on any URL.
See where your tracking stands
Run the same 13-check audit referenced in this post against any URL. No signup, results in seconds.