DAU/MAU: Measuring True Engagement
DAU/MAU shows how often monthly active users return daily. Define active use consistently and interpret the ratio in context.
Prerequisites
- • Understanding of basic user metrics
What DAU/MAU Means
A gym can have 10,000 members while only 500 work out on a typical day. The membership count alone does not show the pattern of use.
- MAU (Monthly Active Users): total who used the product in the last 30 days
- DAU (Daily Active Users): unique users on a given day, averaged over 28 days
- DAU/MAU: the percent of monthly users who come back daily
DAU/MAU = (Average Daily Active Users / Monthly Active Users) × 100
Monthly user count does not show how often those users return. DAU/MAU adds that frequency context.
Define "Active" Before You Measure
This is the single biggest mistake teams make. "Active" cannot mean "opened the app." That counts confused users who left frustrated.
Active means: completed a value-delivering action.
Examples:
- Slack: sent or read a message
- Instagram: scrolled feed for 30+ seconds, or posted
- E-commerce: viewed three products, or made a purchase
- B2B SaaS: completed a core workflow, or generated a report
- Gaming: completed a level, or played 5+ minutes
Use the same definition for both DAU and MAU. Use 28-day averages for DAU to smooth out weekend volatility. Exclude internal team members and test accounts.
Try It
Sample read: MAU 10,000, average DAU 2,000. Ratio = 20%. Under a consistent 30-day definition, that corresponds to about six active user-days per monthly active user. Interpret the result against the product's expected usage frequency and comparable cohorts.
Interpreting DAU/MAU
There is no universal DAU/MAU benchmark. A messaging product, a weekly reporting tool, and tax software have different expected use patterns. Compare cohorts with the same active-user definition, measurement window, platform mix, and job to be done.
For products intended for weekly rather than daily use, use a weekly-active-to-monthly-active measure as well. The question is whether users return at the frequency needed to get value, not whether every product produces a daily habit.
What Actually Moves the Ratio
Three patterns from products that lifted DAU/MAU meaningfully.
Recurring Fresh Value
Spotify's Discover Weekly and Daily Mix illustrate a product pattern: regularly refreshed, personalized content can give users a reason to return. The effect on engagement depends on the audience and implementation.
The pattern is to provide recurring value that fits the product's intended use frequency.
Habit Loops
Duolingo built around streaks. The streak counter, the "your streak is at risk" notification, streak freezes for forgiveness. None of it is novel game design. The combination is the product.
The pattern consists of a cue, a routine, and a reward. The cue is time-based or behavior-based. The routine is a simple, low-friction action. The reward is variable and satisfying, such as progress, social validation, or discovery.
Network Effects
For collaborative products, engagement can depend on whether a team establishes a shared workflow. Measure both account-level and user-level activity before deciding which activation event matters.
For collaborative products, design onboarding around the shared workflow that users need to establish.
Five Measurement Mistakes
1. Counting "opened the app" as active. Inflates DAU. Hides the truth. Users who open and leave are not engaged. They're frustrated.
2. Comparing across categories. Your B2B billing tool will never hit Instagram's DAU/MAU. Compare against your category.
3. Spamming notifications. Spam can boost DAU short-term but tanks retention long-term. Notifications without value are user-loss campaigns disguised as engagement growth.
4. Tracking blended ratio only. Power users can hide in the average. Segment by acquisition channel, plan tier, and cohort, then study the segments with stronger repeat use.
5. Optimizing the wrong thing. Low DAU/MAU can reflect onboarding, product fit, intended usage frequency, or time to value. Investigate those causes before choosing an intervention.
Segment Your Users
Don't treat all users the same. Break them into engagement bands:
| Band | DAU/MAU | What to do |
|---|---|---|
| High-frequency users | Defined from your own cohorts | Study their use cases and needs. |
| Regular users | Defined from your own cohorts | Identify opportunities to reduce friction. |
| Occasional users | Defined from your own cohorts | Examine whether the product needs more recurring value. |
| Low-frequency users | Defined from your own cohorts | Investigate fit, onboarding, and intended usage frequency. |
Move users up one band at a time. Casual to core is more achievable than at-risk to power.
L7/L30 for Non-Daily Products
Some products are weekly by nature. Weekly reports. Sprint reviews. Meal planning.
L7/L30 = (weekly active users) / (monthly active users) × 100. Use this alongside DAU/MAU when daily use is unrealistic, and compare the trend within a consistent cohort.
If your product is genuinely weekly, do not chase a high DAU/MAU. Chase a high L7/L30.
Feature-Level DAU/MAU
Calculate DAU/MAU for each major feature, not just the product overall. A high-ratio feature may be an important repeat-use behavior; review it alongside retention and user outcomes.
Example for a project management tool:
- Task creation: 45% DAU/MAU
- Reports: 15% DAU/MAU
- Team chat: 60% DAU/MAU
The team chat feature is doing the heavy lifting. Invest there. Reports might be high-value occasionally but does not drive daily return.
AI Prompts for Engagement Work
Use Claude, ChatGPT, or Gemini. Ground every claim in your data with a citation rule.
Cohort and segment analysis
Usage data: [paste] Calculate DAU/MAU overall and by cohort. Identify the top 10% by engagement. Find patterns separating daily users from occasional users. Suggest three feature ideas to lift the ratio for the casual band. Cite the rows you used. If you cannot find evidence, say so.
Benchmark interpretation
Our DAU/MAU is [X]%. We are a [B2B / B2C] [category] product. Compare our result with our own historical cohorts and any external dataset whose definition and population match. Suggest the most likely cause of any gap to top quartile.
Notification audit
Notification log: [paste] Find which notifications drive return visits vs which drive uninstalls. Recommend three to keep, three to kill. Cite the data points you used.
A 30-Day Plan to Lift the Ratio
Week 1. Define "active" properly. Pull baseline DAU and MAU using a 28-day average. Document the calculation so the team uses the same one going forward.
Week 2. Segment by acquisition channel and by tenure. Find the band differences. Note which segments are at 60%+. These are your power users.
Week 3. Pick one habit feature to ship. Default options: a streak mechanic, a fresh-daily-content surface, or a time-triggered notification with a real value payload. Ship behind a feature flag to 50% of new users.
Week 4. Compare test and control using a pre-defined success criterion, then assess the result alongside retention and unintended effects before deciding whether to expand the change.
Use the 30 days to establish consistent measurement, segment results, and test one evidence-based engagement hypothesis.
What This Connects To
DAU/MAU is one of three engagement signals. Pair it with:
- Retention Analytics for cohort decay over time
- Conversion Rate for funnel-level engagement
- MRR/ARR for how engagement rolls up to revenue
Use DAU/MAU with retention and product outcomes to understand whether engagement is durable and valuable.