Monthly Active Users (MAU) is the number of distinct users who perform a defined meaningful activity in a product during a given month. SaaS teams use MAU to understand how many people are engaging with a service over time, but the metric is only useful when the company clearly defines what counts as active.
Logging in does not always mean a user received value. Depending on the product, meaningful activity might include creating a project, sending a report, completing a workflow, or using a core feature. A clear definition helps teams measure engagement consistently and avoid overstating product usage.
How to Measure MAU
Choose a calendar month or a rolling 30-day window, then count distinct users who completed the qualifying activity during that period. Use a consistent identity method so the same person is not counted multiple times simply because they used different devices or sessions.
MAU = Number of distinct users who complete at least one defined qualifying activity during the month
Example: If 8,400 unique users complete a qualifying action during April, April MAU is 8,400.
MAU is a count, not a percentage. To compare engagement with another user metric, teams may calculate a ratio such as DAU/MAU, but that ratio answers a different question.
What Counts as an Active User?
Define activity around the product’s purpose. For a project management tool, creating or updating a task may be meaningful. For a reporting platform, generating or viewing a report may qualify. For a developer tool, a successful deployment or meaningful API operation might be a better signal than a login alone.
Document important rules, including how to treat internal employees, test accounts, bots, duplicate accounts, suspended users, and users who only visit a marketing site. If the product has different user roles, consider whether each role needs a separate engagement measure.
Why MAU Matters for SaaS
- Shows reach within the product. MAU helps teams see how many distinct users engage during a month.
- Reveals engagement trends. Changes over time can point to stronger usage, weaker engagement, seasonal patterns, or changes in the user base.
- Supports product decisions. Teams can compare MAU with feature usage and user feedback to understand which experiences attract users.
- Provides context for growth. MAU can be reviewed alongside sign-ups, activation, retention, paid conversion, and customer growth.
- Helps assess product reach. For products with multiple seats per customer, MAU can show how broadly the product is used across the customer base.
MAU vs. DAU vs. WAU
| Metric | Definition | Useful for |
|---|---|---|
| Daily Active Users (DAU) | Distinct users who complete a qualifying activity in a day. | Products where daily engagement matters, such as collaboration or communication tools. |
| Weekly Active Users (WAU) | Distinct users who complete a qualifying activity in a week. | Products used regularly but not necessarily every day. |
| Monthly Active Users (MAU) | Distinct users who complete a qualifying activity in a month. | Monthly reach and broader engagement trends. |
| Paying customers | Customers or accounts that pay under the company’s definition. | Commercial performance and customer-base tracking. |
These metrics are not interchangeable. One paying customer may have many active users, while a free product may have active users who are not paying customers. Always state whether the unit is a person, account, seat, or organization.
DAU/MAU and Engagement
The DAU/MAU ratio compares daily active users with monthly active users. It can help describe how frequently monthly users return on a typical day, but it should not be treated as a universal score of product quality.
DAU/MAU (%) = Daily Active Users ÷ Monthly Active Users × 100
Example: If a product has 1,200 DAU and 8,000 MAU for a consistently defined period, the ratio is 1,200 ÷ 8,000 × 100 = 15%.
Interpret the ratio in context. A product used for daily work may naturally have a different usage pattern from a tool used for monthly reporting. Also make sure the daily and monthly figures use compatible definitions and dates.
How to Improve MAU Meaningfully
- Improve first-use activation. Help new users reach the product’s core value with clear onboarding and a short path to their first useful outcome.
- Make recurring value clear. Identify the jobs users need to complete regularly and make those workflows easy to find.
- Fix friction. Review confusing navigation, slow workflows, unreliable features, and unnecessary setup steps.
- Use relevant reminders carefully. Notifications and email can help users return when they offer real value, but excessive messaging can reduce trust.
- Improve feature discovery. Guide users toward capabilities that match their needs instead of promoting every feature at once.
- Learn from inactive users. Ask why users stopped engaging and look for common obstacles or unmet needs.
- Segment the results. Compare new and returning users, customer plans, roles, acquisition sources, and cohorts where appropriate.
- Pair usage with outcomes. Check whether higher activity connects to task success, retention, customer value, or other product goals.
Common MAU Measurement Mistakes
- Counting logins as meaningful activity without considering the product’s purpose.
- Counting sessions instead of distinct users.
- Mixing user counts and account counts in the same report.
- Changing the definition of active without documenting the change.
- Including internal test accounts, bots, or duplicate identities in production metrics.
- Comparing MAU across products with different usage patterns or definitions.
- Assuming a higher MAU always means better retention, satisfaction, or revenue.
- Reporting MAU without explaining the time window or identity rules.
Frequently Asked Questions
Is MAU the same as monthly paying users?
No. MAU counts distinct users who meet the activity definition, whether or not they pay. Monthly paying users counts users who pay under a specific billing definition. A SaaS business should track both when they answer different questions.
Should a login count as activity?
Only if login itself is a meaningful indicator for the product and the team documents that choice. For many products, a core action gives a more useful picture of engagement than simply opening the app.
What is a good MAU number?
There is no universal target. The right number depends on the size of the addressable audience, product category, business model, and how the product is intended to be used. Trends and outcomes often matter more than a generic benchmark.
Can MAU go down while a business grows?
Yes. A business may increase revenue through pricing, expansion, or higher-value customers even if fewer users are active in a given month. Investigate the change alongside retention, customer count, revenue, and the product’s intended usage pattern.
How often should MAU be reviewed?
Many teams review it monthly and monitor shorter-period trends when useful. Keep the definition stable and annotate major tracking or product changes so the trend remains interpretable.