How to Get GA4 Data Retention and Thresholding Right
How long Google Analytics 4 keeps user-level data and when reports hide small numbers to protect identity.
What is at stake
Default retention settings can lose historical detail, and data thresholding can silently change reported numbers.
The playbook
- Set retention deliberately
- Export raw data to BigQuery for long-term analysis
- Watch for thresholding notices in reports
- Document reporting limitations
- Review settings after property changes
Where it goes wrong
Avoid:
- Leaving defaults unchecked
- Comparing thresholded reports without noticing
- Relying on the interface for historical analysis
- Deleting properties with unexported data
The numbers behind it
| Measure | Figure |
|---|---|
| Retention options | GA4 offers retention periods for user-level data |
| Aggregate reports | standard reports remain available beyond retention limits |
| Thresholding | reports can withhold data when numbers are small |
| Signals | enabling Google signals can trigger thresholding |
Getting outside help
When to hand it over: Bring in help when long-term reporting matters.
Where this comes from
- Google Analytics Help — Data retention
- Google Analytics Help — Data thresholding
The figures and practices above come from the sources listed.
Working on something like this?
We take on Digital Marketing & CRO work for teams who want it done once, properly. Tell us what you are building and we will tell you honestly whether we are the right studio for it. Start a project.
Where to go next
Spotted something wrong? Report an error on this page. We correct on the page and say what changed.