Definition
Monthly active users is a user-level engagement metric. It counts distinct users who performed at least one action defined as “active” within the reporting month—for example, opening an app, logging in, viewing content, or completing a meaningful product event. The exact activity rule should match the product and be documented.
Because each qualifying user is counted once in the period, MAU is different from sessions, visits, or total events. A person who returns several times in the month contributes one MAU, while multiple devices, browsers, consent choices, or identity rules can cause one person to be counted as more than one user.
MAU is usually reported for a calendar month, but some teams use a rolling 30-day window. Those approaches are not interchangeable: a calendar-month number aligns to monthly reporting, while a rolling window smooths the boundary between months. Comparisons are meaningful only when the time window, activity definition, and identity method stay consistent.
What does that mean
As an analogy, imagine a guest list for a month. Each person who does the agreed activity gets one place on the list, even if they visit many times; the list is only useful if everyone agrees what counts as “showing up.”
Why this matters.
MAU turns many individual interactions into a simple signal of how broadly and regularly a product is being used. Product teams can use changes in MAU to assess adoption, while marketing and data teams can compare audiences and campaigns—but the metric should be read alongside retention, frequency, conversion, and business outcomes.
Use cases
Track product adoption and engagement
Product and Data teams often need to know whether a product is reaching more users after a launch, redesign, or feature release. MAU provides a consistent count of distinct active users that can be trended over time and compared by platform, plan, geography, or other approved audience definitions.
When MAU rises, teams can investigate which experiences or channels contributed to the change; when it stalls or falls, they can examine the journeys and actions associated with active and inactive groups. The benefit is a clearer view of adoption than raw event or session totals alone, helping teams prioritize product improvements and validate whether changes broaden usage.
Understand retention and churn signals
Product and Marketing teams may see a stable acquisition rate but a weakening base of returning users. MAU helps establish the size of the active audience, but it does not explain why people return or stop returning.
Teams can pair monthly counts with cohort and segment analysis to compare repeat behavior, identify actions associated with continued use, and distinguish a genuine loss of engagement from changes in acquisition mix or measurement. This supports more targeted re-engagement and product fixes instead of treating every inactive user the same.
Measure mobile app growth
Product and Marketing teams need to know whether app improvements, onboarding changes, or re-engagement campaigns are creating repeat usage. MAU can be tracked by operating system, app version, subscription tier, or acquisition source, then read alongside activation, subscriptions, retention, and feature adoption.
This makes it easier to connect changes in the active audience with the experiences that preceded them. The expected benefit is a more complete view of app growth: not just how many people installed or opened the app, but whether meaningful usage is expanding over time.
See it in practice
After using Product Analytics to inform changes to its native mobile app strategy, Leonardo.Ai reported a +39% increase in iOS monthly active users and a +35% lift in iOS subscriptions within 90 days.
How Contentsquare helps.
Product Analytics automatically captures user journeys across web and mobile so teams can analyze adoption, retention, and feature usage without relying only on manually defined events.
Mobile Apps provides app-focused views of engagement, retention, feature usage, and re-engagement so teams can interpret MAU in a mobile context.
User Segmentation lets teams compare active audiences by behavior and characteristics, helping reveal which cohorts are growing, returning, or dropping off.
Advanced Journey Analytics connects cross-session behavior with retention so teams can investigate the experiences and actions associated with users coming back.
FAQs on monthly active users
A basic calculation is: MAU equals the number of distinct users who performed the agreed active-user action at least once during the reporting month. The calculation is a count, not a sum of visits or events.
The result depends on the activity rule, reporting window, and identity method. Document those choices so the number can be reproduced and compared over time.