Active users over 1, 7, and 28 days
Active users is the count of distinct users with an engagement signal in a window. The window is the whole story: 1-day, 7-day, and 28-day active users (DAU/WAU/MAU) count different things, and GA4 reports rolling versions of each. They overlap rather than add up, and the DAU/MAU ratio is read as a 'stickiness' signal — but all of it inherits the identifier limits of any user count.
What this means
An active user is a distinct user who triggered an engagement signal within a defined time window. The window defines the metric: daily active users (DAU) over one day, weekly (WAU) over seven, monthly (MAU) over twenty-eight. GA4 reports 1-day, 7-day, and 28-day active users as rolling windows ending on each day in the range.
Overlap and stickiness
These windows overlap — a user active today is also counted in the 7-day and 28-day windows — so they must never be summed. The ratio between them is informative: DAU divided by MAU is a common 'stickiness' measure of how much of the monthly audience shows up on a typical day. Because every variant counts identifiers, all the new-vs-returning caveats (cookie loss, multiple devices) apply equally.
- 1-day, 7-day, 28-day windows count different spans
- Windows overlap — do not add them together
- DAU/MAU is a stickiness ratio, not a sum
How it appears in analytics and logs
Active-user counts say how many distinct users engaged within a window. A daily and monthly figure are not comparable in size by design, and both reflect identifiers rather than people.
Diagnostic use case
Choose the active-user window that matches your usage cadence, and use DAU/MAU as a stickiness ratio rather than comparing windows directly.
What WebmasterID can help detect
WebmasterID counts active users from first-party engagement without cross-site tracking, so windowed audience figures carry no third-party-cookie dependency.
Common mistakes
- Adding DAU, WAU, and MAU together.
- Comparing the raw size of different windows as if equivalent.
- Forgetting active users count identifiers, not people.
Privacy and accuracy notes
Active-user counts use first-party identifiers and engagement signals, not personal profiles. Coarse identity reduces precision but protects privacy.
Related pages
- Users: counting people vs identifiers
The users metric estimates how many distinct visitors a site had, but it actually counts distinct identifiers, not individuals. GA4 reports several user metrics — Total users, Active users (its headline), and New users — that mean different things. Because a person on three devices is three identifiers, and a cleared cookie is a new one, the count diverges from the real number of people.
- New vs returning visitors
New vs returning classifies a visitor by whether the analytics tool recognizes them from a prior visit, usually via a client identifier. The split is fragile: cleared cookies, multiple devices, private browsing, and privacy-driven storage limits all make returning visitors look new. So the 'new' share is systematically overstated, and the dimension says more about identifier persistence than loyalty.
- Engagement rate and engaged sessions
Engagement rate is the percentage of sessions that were 'engaged'. In GA4 an engaged session is one that lasted longer than a threshold (10 seconds by default), had a key event/conversion, or had at least two pageviews. Engagement rate is the inverse of GA4 bounce rate, and its threshold is configurable — so the number depends on a setting most people never check.
- Website observability
Windowed active-user trends, first-party.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.