Quick answer
Monthly active users (MAU) is the number of distinct users, accounts or devices that did at least one qualifying action in a 30-day window. What counts as active, who is counted and which window is used all change the number.
Formula: MAU = distinct user IDs with at least one qualifying event in the window
What counts as a monthly active user?
A monthly active user (MAU) is a distinct person, account or device that was active in a product at least once in a 30-day period. The number is only as meaningful as the word "active". Two teams can report very different MAU for the same product because one counts anyone who opened the app and the other counts only people who finished a key action.
Three decisions define every MAU figure:
- Who is counted. Logged-in people, devices, or anonymous browsers. Mapbox, for example, bills its mobile SDKs by MAU and says it counts "each application or device as a separate MAU", so one person with two phones is two users there.
- What counts as active. Any launch or page view (loose), or a specific event such as "created a project" or "sent a message" (strict).
- Which window. The last 30 days ending today (rolling), or the calendar month.
If a MAU number is quoted without those three answers, it cannot be compared with anything.
The formula and a deduplication example
MAU is a count of distinct IDs, not a sum of daily or weekly counts:
MAU = number of distinct user IDs with at least one qualifying event in the window
The deduplication is where people go wrong. Sample data: a product has the following weekly active users in four consecutive weeks.
| Week | Weekly active users |
|---|---|
| Week 1 | 5,000 |
| Week 2 | 4,800 |
| Week 3 | 4,600 |
| Week 4 | 4,500 |
| Sum of the four weeks | 18,900 |
| Distinct users in the 28 days (MAU) | 9,000 |
Adding the weeks gives 18,900, more than twice the real figure. The average user showed up in 18,900 ÷ 9,000 = 2.1 of the four weeks. The sum counts a loyal user four times; MAU counts them once. The same trap applies to adding daily active users (DAU).
Loose versus strict "active": one product, two MAUs
Sample data: a project-management tool over one 30-day window.
| Definition of "active" | MAU | Average DAU | DAU ÷ MAU |
|---|---|---|---|
| Loose: any session | 12,000 | 1,800 | 1,800 ÷ 12,000 = 15.0% |
| Strict: created or edited a task | 4,200 | 1,260 | 1,260 ÷ 4,200 = 30.0% |
The loose definition reports 2.9 times as many users (12,000 ÷ 4,200 = 2.86). The ratio of DAU to MAU, often called stickiness, also doubles under the strict definition, because loose "active" includes many people who open the product, find nothing to do and leave. Neither number is wrong. Decide which question you are asking: "how many people touch the product" (loose) or "how many get value from it" (strict). Then use the same definition in every report, and write it next to the chart.
Rolling window or calendar month?
A rolling MAU looks at the 30 days ending on a given day, so it can be computed for every day and drawn as a smooth line. A calendar-month MAU resets on the first and is easier to put in a board deck, but it compares unevenly: February has 28 days and December has 31.
The edge cases are easy to test. Take a user whose only visit was on December 1. The calendar-month MAU for December counts them. The rolling 30-day MAU on December 31 covers December 2 to December 31 and does not. Both are correct; they answer different questions. Pick one, note it, and do not mix them in one trend line.
MAU, WAU, DAU and what each is for
| Metric | Window | Use it to answer |
|---|---|---|
| DAU | One day | Is the product part of a daily routine? |
| WAU | 7 days | Is it a weekly habit (planning tools, reporting)? |
| MAU | 30 days | How big is the active base, including occasional users? |
| DAU ÷ MAU | Day vs 30 days | How often does a monthly user return? See DAU/MAU |
MAU suits products used a few times a month, such as expense tools, travel and tax software. For a messaging app, DAU is the better lead metric; for a monthly-billed B2B tool, a weekly measure may reflect real use more closely. MAU also hides churn: a flat MAU can be a stable base, or a new cohort replacing one that is leaving. For that, read retention, which asks whether the same people come back, and user engagement, which asks how much they do.
How to choose the "active" event
Use these rules, in order:
- If the product has one action that delivers its value (a message sent, a file synced, a trip booked), use that action. A page view is not value.
- If value arrives by reading or watching, use a qualifying view: a session of at least some minimum length, or a content item opened.
- If you must report a loose figure for an outside audience (an investor update, an app-store listing), report both: "12,000 monthly active users, of which 4,200 completed a task".
- If the definition does not hold for new releases (the key action did not exist last quarter), say so and report the old and new definitions side by side for one period.
A useful sanity check: pick 20 random "active" users and read what they actually did. If more than a few only opened the app and left, the definition is too loose to guide product decisions.
Also decide the unit once. Logged-in IDs are the most stable; device IDs overcount people with several devices; anonymous cookies reset when someone clears their browser.
Common mistakes with MAU
- Counting registered users. Sign-ups only ever go up; MAU can fall. A sign-up total is not a MAU.
- Letting bots in. Crawlers and scripts inflate any "any session" definition. Exclude them before you count.
- Mixing identities. If anonymous browsers and logged-in people are both counted by cookie, one person can be two MAU. State whether the unit is a device, a cookie or a person.
- Changing the definition mid-year. A new "active" rule creates a step in the chart that looks like growth or decline. Re-state history under the new rule, or annotate the date.
- Comparing MAU across companies. Public MAU numbers come from each firm's own definition. Use them as context, not as a benchmark you can recompute.
- Reading MAU alone. A rising MAU with falling DAU ÷ MAU means broader but shallower use.
Reading MAU in TapCub
Take the loose-versus-strict example above and check it for your own app.
- Open App analytics › Users. The active-users tab draws daily, weekly and monthly active users. In TapCub, "active" means a start or a screen view in the range; the monthly figure is the thirty days ending on the last day, with each person counted once.
- Compare it with the weekly line. If the weekly values add up to far more than the monthly one, you are seeing the same deduplication effect as in the table above.
- For a strict definition, define your own metric in All-platform analytics › Behavior › Metrics & SQL: a distinct-user count of the event that marks real use, for example "task created". Divide it by the loose monthly figure to get the share of active users who do the key action.
- Keep the definition you chose written next to the metric. TapCub does not decide for you what "active" means for your product.
The sample figures in this article are illustrative; TapCub will not produce them for you.
See also: How to Increase Monthly Active Users: Tactics by Lever.
Sources
- Mapbox Docs, Monthly active users (MAU) glossary.
- Wikipedia, Active users.
Was this explanation clear?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.

Data Analyst
Explores traffic sources, conversion funnels, and retention, using clear metric definitions and concrete examples to explain what the numbers mean.