Add to Preferred Sources
GA4 data retention settings explained: Google Analytics 4 stores detailed event and user data for either 2 months or 14 months depending on your configuration — and because the platform defaults to 2 months, many South African marketing teams are quietly losing the historical data they need to run serious conversion rate optimisation.
This single setting governs how long raw user-level data remains available in Explorations, funnel reports, and audience builders. Change it to 14 months and you protect a full year of comparable data; leave it at the default and your funnel analysis has a two-month horizon.
If your team is running A/B tests, analysing checkout drop-off points, or building retargeting audiences from behavioural data, two months of history is rarely sufficient. A properly configured GA4 property is the foundation for evidence-based CRO — and data retention is one of the first admin settings to lock down. This guide walks you through exactly what the setting controls, how to change it in four steps, what it means for POPIA compliance, and when 14 months still isn't enough.
Quick Answer
GA4 data retention settings control how long Google Analytics 4 keeps raw event and user-level data before automatically deleting it. The default is 2 months — far too short for meaningful year-over-year analysis or deep funnel work. Change it to 14 months via Admin > Data Settings > Data Retention to maximise your Exploration and funnel report history. Standard aggregated reports are not affected by this setting and retain data indefinitely. For South African businesses, setting 14 months is almost always correct, provided your Privacy Policy and consent mechanism cover analytics data collection under POPIA.
Jump to a section
Is Your GA4 Property Configured Correctly?
Send us your property URL and we'll check your data retention setting, event tracking, and conversion setup — and show you exactly what's missing before it costs you data you can't recover.
Get a Free GA4 ReviewWhat GA4 Data Retention Actually Controls
The GA4 data retention setting does one specific job: it determines how long Google stores raw, user-identifiable event data on its servers before deleting it permanently. Understanding what falls inside and outside this setting is critical — because many businesses assume the setting affects everything in GA4, when in reality it only applies to a specific category of reports.
| GA4 Feature | Affected by Retention Setting? | Why |
|---|---|---|
| Explorations (free-form, funnel, path) | Yes — limited to your chosen window | Uses raw user-level event data |
| Audience builder (segment conditions) | Yes — history limited to retention window | References user-level event records |
| Standard Reports (Acquisition, Engagement, etc.) | No — data is retained indefinitely | Uses permanently aggregated daily tables |
| Standard Report date comparisons | No | Aggregated totals, no raw identifiers |
| Demographic data (age, gender, interests) | Hard 2-month limit regardless of setting | Privacy requirement — cannot be extended |
| Google Signals data | Hard 26-month maximum regardless of setting | Platform-enforced cap for signed-in user data |
The practical implication: if you use standard reports (the Acquisition, Engagement, and Monetisation tabs in the left sidebar), you are working with aggregated data that accumulates from day one regardless of retention settings. But the moment you open the Explore tab, build a funnel report, or create a custom audience based on past behaviour, you are querying raw event data — and that data disappears after your retention window expires.
Key Takeaway: The Explore Tab Is the Issue
Standard GA4 reports are permanently safe. The 2-month default only destroys data that powers Explorations, funnel visualisations, and audience conditions built from raw events. If your team runs any of those — change the setting today, because the data lost during the default period is gone permanently.
GA4 Data Retention Settings Explained: Your Two Available Options
Free Google Analytics 4 properties offer exactly two choices for user-level and event-level data retention: 2 months (the default) or 14 months (the maximum for the standard product). There is no middle ground, and there is no option to retain indefinitely as Universal Analytics once allowed. A mandatory expiry is baked into GA4's architecture.
Standard GA4 vs GA4 360 Retention
Free GA4: 2 months or 14 months only.
Google Analytics 360 (paid enterprise): Event data can be retained for 26, 38, or 50 months. GA4 360 is available by contract through Google Sales — pricing is not published publicly and should be obtained directly from Google for SA terms. It is designed for large enterprises with high traffic volumes and complex attribution needs.
All properties: Demographic data (age, gender, interests) expires at 2 months regardless of any setting. Google Signals cross-device data caps at 26 months across all tiers.
The case for 14 months is straightforward for most SA marketing teams: it gives you a rolling 13-month window in Explorations, which means you can compare July 2025 behaviour against July 2024 behaviour directly inside GA4's Explore tab without exporting anything. That kind of year-over-year funnel comparison is impossible on the default 2-month setting.
One important limitation: changing from 2 months to 14 months is not retroactive. GA4 will not recover data that has already been deleted under the 2-month window. The 14-month clock starts from the date you make the change, so the sooner you update the setting, the better.
How to Change Your GA4 Data Retention Settings: Step by Step
You need Editor role access at the property level to make this change. Account-level Viewer or Analyst roles cannot access Data Settings. Here are the exact steps:
| Step | Action |
|---|---|
| 1 | Sign in to Google Analytics and click Admin (the gear icon) in the bottom-left navigation |
| 2 | In the Property column, click Data Settings, then select Data Retention |
| 3 | Change the Event data retention dropdown from 2 months to 14 months |
| 4 | Toggle Reset user data on new activity to ON — this resets the retention clock each time a known user returns, extending their data life for another 14 months from their most recent visit |
| 5 | Click Save and allow up to 24 hours for the change to take effect |
Best practice: Make this change when you first create a new GA4 property, before any meaningful data accumulates. Teams that build a year of GA4 data on the 2-month default then change the setting are protected from that point forward — but they permanently lose the year of exploration-level history they accumulated beforehand.
Common mistake: Changing only the User data retention without checking the Event data retention, or toggling "Reset user data on new activity" to OFF. Both leave gaps. With the toggle OFF, a user who visits in January and doesn't return until March (beyond the 14-month reset window) would be treated as a new user — breaking continuity in audience and funnel data.
Why the 2-Month Default Setting Damages CRO Analysis
The 2-month default limits every GA4 Exploration and funnel report to 60 days of raw data — too short for year-over-year funnel comparison, seasonal diagnosis, or evaluating a redesign against prior behaviour. A two-month horizon is enough to spot weekly fluctuations; it is not enough to separate a seasonal trough from a structural problem or compare a campaign's impact against the same period last year.
The numbers make this concrete. Research by Baymard Institute, compiled across 50 cart abandonment studies, puts the average documented abandonment rate at 70.22%. SA ecommerce stores tracking cart abandonment need historical funnel data to separate signals: with 14 months of retention, you can build a funnel in GA4 Explore that compares Black Friday 2025 drop-off against Black Friday 2024, isolating a payment-friction issue from seasonal volume. A two-month window makes that comparison impossible.
GA4 Data Retention Settings Explained: What You Lose at 2 Months
At the default 2-month retention window, you lose: year-over-year funnel comparisons in Explore, full-journey path analysis for users with longer consideration cycles, audience conditions based on behaviours more than 8 weeks old, and the ability to evaluate seasonal patterns. For most SA businesses running any form of CRO programme, the 2-month setting effectively means your Exploration workspace is a rolling snapshot, not a strategic tool.
Audience building is equally affected. If your retargeting audiences in GA4 are built from event conditions ("users who viewed a product but didn't purchase in the last 6 months"), the 2-month default quietly truncates that to 2 months — without any warning in the interface. You may believe you are targeting a 6-month window when GA4 is actually working with 8 weeks of raw data.
Running CRO Without the Right Historical Data?
Tell us your current GA4 setup and CRO goals — we'll assess whether your analytics configuration supports the depth of analysis your programme actually needs, and whether the timeline makes sense before you commit.
Check My Analytics SetupGA4 Data Retention and POPIA: What South African Businesses Need to Know
Under POPIA, South African businesses must justify how long they keep identifiable user data — 14 months is defensible for a marketing analytics purpose, provided your Privacy Policy and cookie consent mechanism are in place. Section 14 of South Africa's Protection of Personal Information Act — the retention and restriction of records provision — prohibits organisations from retaining personal information for longer than is necessary to achieve the purpose for which it was collected. GA4 collects user-level data — session identifiers, event sequences tied to cookies — which qualifies as personal information under POPIA.
Whether 14 months is appropriate depends on your specific use case, data flows, and any sector-specific requirements — if you are uncertain, consult a POPIA-registered information officer or privacy attorney. For a typical marketing analytics purpose (optimising website performance, understanding conversion behaviour), 14 months is a defensible retention period. The key requirements are:
- Your Privacy Policy must describe analytics data collection, the purpose, and the retention period
- Your cookie consent mechanism must give users a genuine choice about analytics tracking before data is collected
- GA4 tags should fire only after consent is given — not on initial page load
- If a user withdraws consent, their data should be deleteable on request (GA4 offers user deletion via the Admin API)
POPIA Practical Note
POPIA does not require you to minimise retention to the point where it prevents legitimate business operations. It requires that retention be proportionate to purpose. A marketing analytics purpose supports 14 months. What POPIA does not permit is retaining identifiable user data indefinitely "just in case" — which is exactly the Universal Analytics model that GA4 was designed to replace. The 14-month ceiling is one of the ways GA4's architecture happens to align with privacy regulation by design.
When 14 Months Isn't Enough: The BigQuery Route
For businesses with longer sales cycles, multi-year seasonal patterns, or compliance audit needs, 14 months of Exploration data inside GA4 is the ceiling — not a sufficient answer. There are two options beyond it.
BigQuery Export (recommended): GA4 can stream raw event data continuously to a linked BigQuery project, where it is stored permanently under your own data governance rules. This is available on the free GA4 tier. The data in BigQuery is queryable with SQL and can be connected to Looker Studio for visualisation.
The cost is minimal at typical SA business traffic volumes — BigQuery charges on query volume, not storage at small scale. This is the most practical long-term solution for teams that want more than 14 months of raw event data without paying for GA4 360.
Google Analytics 360: The paid enterprise version of GA4 extends event data retention to 26, 38, or 50 months within the GA4 interface itself. GA4 360 also removes data sampling in standard reports at high traffic volumes. At local pricing, this is a significant annual investment appropriate for large SA enterprises or high-volume ecommerce businesses — not typical for SMEs and growth-stage businesses.
Key Takeaway: BigQuery Is Your Friend
If your business needs more than 14 months of historical event data for funnel analysis or reporting, connect GA4 to BigQuery before your retention window expires. The link is set up in Admin > Product Links > BigQuery Links. Data streams to BigQuery from the link date forward — it does not backfill, so early connection is critical. This is free to set up; BigQuery charges apply only as your query volume grows.
Not Sure Which Data Setup You Actually Need?
Share your business context — traffic volume, sales cycle, CRO programme maturity — and we'll give you a direct recommendation on whether free GA4 at 14 months, BigQuery export, or a different analytics architecture fits your situation.
Get a Tailored Analytics RecommendationWhy South African Businesses Work with Growth Pulse Media on Analytics and CRO
Analytics configuration is not a one-time task. GA4 has shifted the measurement landscape significantly — from session-based to event-based tracking, from permanent UA data to mandatory retention windows, from simple goal funnels to Exploration-based analysis. Many SA marketing teams are still running GA4 the way they ran Universal Analytics, and the result is months of misconfigured tracking and missing conversion data.
Dirk built and scaled an SA ecommerce business before founding Growth Pulse Media. That means our GA4 work is done by someone who has run the campaigns, paid the invoices, and lived with the reporting gaps when tracking wasn't right. We configure GA4 for conversion rate optimisation outcomes — event schemas that map to real conversion steps, funnels that reflect actual user journeys, data retention and BigQuery export set up correctly from day one.
We work with a limited client load so that every property gets senior attention, not a junior checklist. Our stack includes GA4, Google Tag Manager, Looker Studio, and BigQuery where needed — and we integrate with SA payment gateways (PayFast, Peach Payments, Yoco) to ensure transaction data flows correctly into ecommerce tracking.
Who GA4 Data Retention Settings Are NOT the Priority For
You launched your GA4 property this week. Data retention is worth setting immediately, but it is not your urgent task. Your first priorities are event tracking verification, conversion event marking, and linking to Google Search Console. Set retention to 14 months on day one and move on.
You only use GA4 for top-level traffic reporting. If your team exclusively uses standard reports — Acquisition, Engagement, and Overview tabs — the retention setting has no practical impact on your current workflow. Standard reports are not affected. Changing the setting is still good practice, but it will not change anything you see today.
Your business has a very short customer lifecycle and no need for historical segmentation. A business running purely transactional, high-frequency, low-consideration products where user behaviour this month has no connection to last quarter has limited use for 14 months of exploration history. Two months may genuinely be sufficient. The default is still worth changing as a precaution, but it is a lower-priority config item.
You are planning to move your analytics stack entirely to BigQuery or a first-party data warehouse. If your architecture decision is to treat GA4 as an input into a centralised data warehouse rather than as your primary analysis tool, the in-platform retention setting matters less. BigQuery export is your retention mechanism and the in-GA4 window becomes secondary. Focus on the BigQuery link configuration instead.
Frequently Asked Questions: GA4 Data Retention Settings Explained
What is the default GA4 data retention setting?
The default GA4 data retention period is 2 months for both user-level and event-level data. This means all raw event data — the data that powers Explorations, funnel reports, and audience builders — is permanently deleted after 60 days unless you change the setting. Standard aggregated reports are not affected by this default and accumulate data indefinitely from the day you set up the property.
Does changing GA4 data retention to 14 months recover old data?
No. Changing the retention setting from 2 months to 14 months is not retroactive. Data that has already been deleted under the 2-month window cannot be recovered. The 14-month protection applies only to data collected from the date you make the change forward. This is the core reason to update the setting as early as possible after creating a GA4 property — the longer you wait, the more historical exploration data you lose permanently.
Does GA4 data retention affect standard reports?
Standard reports — the pre-built reports under Acquisition, Engagement, Monetisation, and Retention in the GA4 sidebar — are not affected by the data retention setting. These reports use permanently aggregated daily tables from which identifying information has been removed, so they accumulate data indefinitely from your property's start date. Only Explorations, custom funnels, path analysis, and audience conditions built from raw event data are subject to the retention limit.
What should South African businesses set their GA4 data retention to?
For most South African businesses using free GA4, the correct setting is 14 months — the maximum available. This enables year-over-year comparisons in Explorations, supports deeper funnel and audience analysis, and is a defensible retention period under POPIA's data minimisation requirement for a marketing analytics purpose, provided your Privacy Policy and cookie consent mechanism are in place. For businesses needing more than 14 months of raw event history, linking GA4 to a BigQuery project is the recommended next step.
What is the "Reset user data on new activity" toggle in GA4 data retention?
The "Reset user data on new activity" toggle, found in the same Admin > Data Settings > Data Retention screen, restarts the retention clock each time a known user returns to your site. With the toggle ON and a 14-month retention period, a regular visitor can expect at least 14 months of data to be retained, since each new session resets the expiry date. With the toggle OFF, data is deleted exactly 14 months after the user's first recorded event, regardless of whether they have returned since. For most businesses, turning this toggle ON is the correct configuration.
Your GA4 Should Be Working Harder Than It Is
Many SA businesses are running GA4 with the wrong data retention setting, incomplete event tracking, and funnels that don't reflect how their customers actually buy. Growth Pulse Media configures GA4, Google Tag Manager, and Looker Studio for SA businesses — with proper ecommerce event schemas, POPIA-compliant consent, and the conversion data you need to run real CRO. No obligation — we'll get back to you within 24 hours.
Get a GA4 Configuration Review