A historical total in a standard GA4 report does not mean the underlying detail is still available for a new exploration. Before changing retention, identify which data and reporting surface your analysis needs.
The practical question is not simply “How long does GA4 keep data?” It is “Will we still be able to reproduce this analysis next year?” Running an independent tool such as Simple Analytics alongside GA4 gives you a second, aggregate traffic history from the day you install it.
Standard reports and explorations are different
Google's retention setting governs user-level and event-level data used in explorations and funnel reports. It does not affect standard aggregated reports, including their primary and secondary dimensions and comparisons. Google's retention documentation.
Do not tell stakeholders that all GA4 reports disappear after two or fourteen months. Equally, do not promise a new detailed breakdown because an older total is still visible.
Specify the intended analysis. A monthly pageview trend and a retrospective exploration of a particular user segment have different requirements.
Check the applicable retention period
Standard properties offer two or fourteen months. Analytics 360 adds twenty-six, thirty-eight and fifty months for other event data; user-level and key-event data have separate limits. Age, gender and interest data have a two-month limit. Large standard properties and XL 360 properties can have event retention reduced to two months. Retention periods and exceptions.
Check your property's current settings and administrator notices. A setting someone remembers choosing is not evidence that it still applies.
Increasing retention cannot restore deleted data
An increase applies to data still retained, not data already deleted. Reductions delete affected older data in the next monthly process. Google provides a twenty-four-hour delay before implementing a setting change. Resetting retention on new activity applies to user-level data; it is not a rolling extension of every historical event. How retention changes work.
Before editing the setting, write down the current value, proposed value, required reporting horizon and owner. Check with the people responsible for your organization's retention policy. Longer storage should answer a defined business requirement.
Manage warehouse retention separately
GA4's BigQuery integration exports event data into a Google Cloud dataset. Standard properties can use it; Analytics 360 is not a prerequisite. Verify the earliest available export date instead of assuming the warehouse contains the property’s full history. BigQuery setup.
Once records are in BigQuery, inspect the dataset and table expiration settings. BigQuery can apply default lifetimes to new tables, with table-level overrides. Changing a dataset default does not retrospectively give every existing table the new expiration. BigQuery expiration settings.
Treat the export as a pipeline that needs an owner. Check that expected tables exist, monitor export failures, and record the earliest available day. A linked project is not sufficient evidence of a usable archive.
Make historical comparisons reproducible
For each recurring report, keep a short measurement record:
| Record | Why it matters |
|---|---|
| Source and query | A report export and an event query are different inputs. |
| Dates, time zone and included pages | Prevents accidental scope changes. |
| Metric definition | Pageviews, users and sessions are not interchangeable. |
| Collection and CMP changes | Helps investigate breaks in the series. |
| Export coverage and expiration | Shows which periods can still be rechecked. |
For a year-over-year review, establish that both periods have the required coverage before interpreting a change. If one period is unavailable, disclose that limitation rather than filling the gap with an assumed trend.
Would an independent baseline solve this?
It answers a different question. Retention concerns data you previously collected. Running Simple Analytics alongside GA4 gives you another measurement of traffic from installation onward. It does not recover GA4 records that expired or traffic neither system recorded.
Use that baseline to compare future counts and trends under documented conditions. Simple Analytics calculates session starts from pageview context without persistent visitor IDs, so keep its definition separate from GA4's Sessions metric. How the measurement works.
Free 30-day proof of concept
Compare Simple Analytics with GA4 on your website
Run a free 30-day proof of concept alongside your existing GA4 setup and CMP.
We help you:
- Agree on the measurement question, metrics, pages and comparison period.
- Set up Simple Analytics, including support for proxies and custom domains where needed.
- Review the counts, trends and methodological differences together.
Tell us what you want to compare. We’ll agree on the scope of the POC together.