GA4 Data Retention: Settings and Reporting Impact

GA4 data retention controls how long user-level and event-level data remains available for certain explorations and analysis features. It is separate from the retention of aggregated data used in standard reports, so changing the setting does not mean every historical report immediately disappears.

Where to review the setting

In a GA4 property, open the Admin area and look for Data collection and modification, then Data retention. The exact labels can vary as the interface changes. Review the available retention period and the option that resets user-based data when new activity occurs. Select the longest period that fits the organization’s needs and applicable data policy.

What the setting affects

The retention window is most visible in analyses that use event- or user-level data, including some Explorations. A long date range may therefore show older data in standard aggregate reporting while an exploration has less detail for the same period. Do not treat those surfaces as identical datasets.

The available event-data retention choices have commonly included shorter and longer windows, such as two or fourteen months, but availability and behavior can vary by property configuration and product updates. Check the current interface rather than assuming every property has the same options.

Set a policy, not just a number

• Document why the chosen period is needed for analysis and how it aligns with data governance.
• Test a saved exploration with a date range that crosses the retention boundary.
• Review linked products and exports separately; their storage and retention settings may be independent.
• Limit access to detailed user-level data and avoid collecting identifiers that are not needed.

Plan before analysis is lost

Retention settings generally govern future availability; extending a window does not restore data that has already expired. If a team needs long-term raw event analysis, consider a governed export and define its access, deletion, and storage rules with the appropriate data owners.

Review the setting during analytics governance changes, not only after a report looks incomplete. A short note in the property documentation helps analysts distinguish a retention boundary from a tracking defect.