Google Analytics Active Users: What GA4 Counts

Olamide Sule, founder of Dolphin Analytics: a digital analytics expert based in London who sets up and audits GA4 tracking for agency and in-house clients most weeks.

A client sends a screenshot with two numbers that should match and don’t. GA4 says one thing about users, Shopify or a CRM says another, and a monthly figure built from daily ones says a third. We sort out this exact confusion in client properties most weeks. Often nothing is broken: the numbers answer different questions. This is the walkthrough we give, metric by metric, with the places to check your own property.

What are active users in Google Analytics 4?

Active users in Google Analytics 4 are the distinct people who engaged with your site or app during the date range you picked. On a website, GA4 counts a user as active when they have an engaged session, or when their visit sends a first_visit event or engagement time, per Google’s user metrics documentation.

An engaged session is one that Google defines as lasting longer than 10 seconds, firing a key event, or including two or more page views. Our bounce rate and engaged sessions guide covers that definition in full, because it sits under several GA4 metrics.

The detail that trips most people up is the label. In GA4’s standard reports, the metric called “Users” is active users. It is not a count of everyone who loaded a page. If you want that wider number, you need a different metric.

How are active users, total users and new users different?

GA4 has four user metrics, and each one filters the same visitors in a different way. Active users is the default in reports; the others live in explorations and some report cards.

Metric	Who it counts	Where you usually see it
Active users	Distinct users who engaged in the date range	Labelled “Users” in standard reports
Total users	Distinct users who logged at least one event, engaged or not	Explorations, the Data API
New users	Users interacting for the first time (the first_visit event on web)	Acquisition reports
Returning users	Users who had at least one earlier session	Explorations, the “New / established” dimension

Total users will always be equal to or higher than active users. The gap is mostly returning visitors who had no engaged session and sent no engagement time. A new visitor who leaves fast still counts as active, because the first_visit event qualifies them. On most properties the two figures sit close together.

New users and returning users do not always add up to active users either. A returning visitor who bounces is a returning user but not an active one, so the categories overlap rather than slicing one pie.

What are daily, weekly and monthly active users in GA4?

Daily, weekly and monthly active users are the active users metric measured over rolling windows. In GA4 they are named 1-day active users, 7-day active users and 28-day active users; people usually shorten them to DAU, WAU and MAU. Note that GA4’s “monthly” figure is 28-day active users, a rolling window rather than a calendar month.

“Rolling” means each day’s figure looks back over its own window. The 7-day active users figure for a Friday counts distinct engaged users from the seven days ending that Friday. Plot it over a quarter and you get a smoothed line of reach, not a spike on each busy day.

GA4 also calculates three ratios from these windows: DAU/MAU, DAU/WAU and WAU/MAU. Product teams call these stickiness. A high DAU/MAU means the same people keep coming back day after day, which matters for an app or a SaaS product and much less for a brochure site people visit once before enquiring.

How do you find these user metrics in your own GA4 property?

The fastest place to see every user metric side by side is a free form exploration. Standard reports show active users by default, and adding other user metrics means editing the report.

1. In GA4, open Explore in the left navigation and choose Free form.
2. In the Variables column, click the + beside Metrics. Search for and import Active users, Total users, New users, 1-day active users, 7-day active users and 28-day active users. Add DAU / MAU too if you want the stickiness ratio.
3. Click the + beside Dimensions and import Date.
4. Drag Date into Rows and the metrics into Values.
5. Set the date range at the top of the Variables column. Use a date range at least as long as the 28-day active users window, so that figure has a complete window to look back over.

For a quick check without building anything, open Reports > Reports snapshot. Its users chart shows the same active users count as the “Users” label everywhere else in standard reports.

Why can’t you add up daily active users?

GA4 de-duplicates users inside each window, so daily figures don’t sum to a weekly or monthly one. Someone who visits on five days in a week counts once in each of those five daily figures, but only once in the 7-day active users figure.

Add seven daily numbers together and that one person becomes five. The sum overstates real reach, and the gap widens with how loyal your audience is. We see this most in agency reports built in Looker Studio or a spreadsheet, where a “monthly users” row is really a sum of daily rows. Pull the 28-day active users metric, or the active users figure for the full date range, instead.

GA4 also estimates unique counts of users and sessions rather than counting every ID one by one, using an approximation method called HyperLogLog++ that Google describes in its Analytics sessions documentation. That estimation is why two reports covering the same range can sometimes differ by a small amount. Small differences between reports are expected; large ones point to a filter, a comparison or a different metric.

Why don’t GA4 user counts match other tools?

GA4 user counts rarely match Shopify, a CRM, a product analytics tool or old Universal Analytics, because each one defines a user differently and sees a different share of visitors. When we audit accounts, the first thing we check is which definition each number uses, before anyone assumes the tracking is broken.

These are the usual causes, in the order we check them:

• The “Users” label. GA4’s report figure is active users, which leaves out returning visitors who never engaged. That accounts for a small difference. Large gaps usually come from consent, identity or blocked tags, covered in the bullets below.
• Reporting identity. GA4 can identify people by user ID, by device ID, or with modelling added on top. Check it under Admin > Data display > Reporting identity. Changing between Blended, Observed and Device-based changes user counts in reports for past dates too, so note which one was set when comparing periods.
• Consent. Visitors who decline analytics cookies are not counted as ordinary users. Blended identity can model some of them if your property qualifies. Our guide to Consent Mode v2 covers what that does to your numbers.
• Devices, not people. Without a user ID, one person on a phone and a laptop is two users. Tools that key on a login, like a CRM or Shopify customer records, count that person once.
• Blocked tags. Ad blockers and browser privacy features stop the GA4 tag loading for some visitors. Shopify’s order records still include those purchases; GA4 doesn’t.

If the gap is about sales rather than people, our post on Shopify Analytics vs Google Analytics covers how the two count orders and sessions. If you’re unsure how users relate to the events and sessions underneath them, start with GA4 sessions and events explained.

Which user metric should you report to clients?

Report active users for the date range as your headline audience figure. It matches the “Users” number clients see when they open GA4 themselves, which heads off a round of “why doesn’t your report match mine?” emails.

Use total users only when the question is about reach, for example sizing an audience for remarketing. Use new users for acquisition questions, such as whether a campaign brought in people who hadn’t visited before. Keep DAU/MAU for apps and logged-in products, where repeat daily use is the point. On a lead generation site it mostly reports how rarely people need to come back, which isn’t a problem to solve.

Whichever you pick, name the metric in the report exactly as GA4 names it. A row labelled “Users” that is really total users is a reporting mismatch we find often.

How we check user counts for clients

We’ve set up hundreds of GA4 properties and Tag Manager containers for agency and in-house clients. When a client’s user counts disagree, we check the definitions before the tag. Often the fix is a label or a setting: a reporting identity switched without a note, or a dashboard summing daily active users.

When the numbers really are wrong, the cause sits lower down, in the tag or the consent setup. For a first look at what loads on your site, Sonar scans any URL for free, in one click and with no account. It reports the tags, pixels and consent setup it can prove from the outside. If you’d rather talk the problem through with a person, tell us what’s broken, or book a call.