Why 15% DAU/MAU Can Be Misleading for Product Managers

September 12, 2026

Why 15% DAU/MAU Can Be Misleading for Product Managers

Why 15% DAU/MAU Can Be Misleading for Product Managers

Apptenium analytics hero about DAU MAU metrics

DAU/MAU ratio is daily active users divided by monthly active users, expressed as a percentage, and it tells you what share of your monthly base opens your product on a typical day. A higher ratio means more habitual, daily usage, which is what most teams call stickiness. A lower ratio isn’t automatically bad. It’s often normal for products people use weekly or seasonally rather than daily. Benchmarks vary widely by category, so your own historical baseline matters more than any published number.

TL;DR:

  • A high DAU/MAU ratio indicates habitual use, but products with weekly or seasonal usage patterns can have naturally lower ratios without reflecting poor performance.
  • Using a value-driven active event, like a core action rather than just an app open, makes the ratio more accurate in representing genuine engagement.
  • Benchmarks vary widely: social apps often exceed 40-50 percent, B2B SaaS around 31 percent, while low-frequency apps like finance or utility services tend to be lower.
  • The ratio can be misleading if driven by power users, forced engagement, or definition changes, so it must be interpreted alongside retention, revenue, and cohort analysis.
  • Accurate measurement hinges on consistent identity resolution and choosing rolling 30-day MAU, with alerts for sudden shifts that may indicate tracking issues.
Apptenium
See Your App Performance Clearly
Apptenium brings ASO, competitor intelligence, keyword tracking, and app performance data together in one platform.

Table of Contents

What Counts as DAU/MAU: Defining Active Users and Windows

The DAU/MAU ratio only means something if you’re precise about what “active” means. Daily active users (DAU) counts unique users who trigger a defined event in a single day. Monthly active users (MAU) counts unique users over a 30-day window. Divide DAU by MAU and multiply by 100, and you get a stickiness percentage that shows how habitual product usage really is.

Two decisions determine whether that number means anything:

  • Rolling vs. calendar windows: A rolling 30-day MAU (calculated fresh each day) smooths out artifacts like short months or weekend dips, while calendar-month MAU resets on the first of every month and can swing based on how many weekends fall inside it.
  • What counts as “active”: Some teams count any app open. Others require a core action like a purchase, a message sent, or a workout logged.

Tying “active” to a value action rather than a bare open is the single biggest lever you have for making this metric honest. An app open tells you someone launched the app. It doesn’t tell you they got anything out of it.

How to Calculate DAU/MAU: A Step-by-Step Example

Calculating the ratio itself takes seconds once you’ve picked your active event. Getting a useful number takes a little more discipline.

  1. Choose your active event. Pick something tied to value: a session over 30 seconds, a core feature use, a completed transaction.
  2. Compute DAU. Count unique users who triggered that event on a single day.
  3. Compute MAU. Count unique users who triggered it at least once in the trailing 30 days.
  4. Divide DAU by MAU and multiply by 100 for a percentage.
  5. Decide on daily-snapshot vs. averaged. A single day’s DAU divided by MAU can be noisy; averaging DAU across all 30 days in the window, then dividing by MAU, gives a steadier read.

Here’s a worked example: say your app logs 45,000 unique users on a given Tuesday, and 300,000 unique users touched a core event over the trailing 30 days. That’s 45,000 ÷ 300,000 = 15%. If you average DAU across the full month instead, say the daily average comes out to 42,000, you’d get 14%. Both are valid. Just be consistent about which one you’re tracking over time.

In a data warehouse, this usually looks like a COUNT(DISTINCT user_id) query filtered by event name and date range, run once for the single day and once for the trailing 30, then divided in your BI tool or a simple spreadsheet formula.

DAU MAU calculation workflow diagram

What Is a Good DAU/MAU Ratio? Benchmarks by Vertical

There’s no universal “good” number, and chasing one is how teams waste a quarter optimizing the wrong thing. Context from your specific category matters more than any headline figure.

  • Social and messaging apps tend to sit highest, with many exceeding 40 to 50 percent stickiness because the entire product is built around daily habit loops.
  • B2B SaaS products average closer to 31 percent, which reflects real usage patterns rather than underperformance. Most B2B tools are used on workdays, not weekends, and often only when there’s a task to complete.
  • Fintech and utility apps frequently land lower still, since checking a balance or filing an expense report isn’t a daily need for most people.
  • AI products often show lower raw DAU/MAU even when they’re delivering real value, because usage clusters around specific tasks rather than habitual daily check-ins.

Don’t borrow Meta or LinkedIn’s numbers as your target. Those figures come from a different product category, a different user relationship, and often a different era of the internet entirely.

Where DAU/MAU Falls Short: Pitfalls to Watch For

DAU/MAU is popular because it’s simple. That simplicity is also where it lies to you.

  • Power-user bias. A small group of highly engaged users can inflate your DAU while the median user barely returns, masking a retention problem underneath a flattering headline number.
  • Forced frequency. Aggressive notifications, streaks, and reminder emails can push the ratio up without adding real value, producing what amounts to vanity growth.
  • Necessity mismatch. Tax software, moving-planning tools, and other low-frequency-by-design products will always show a modest ratio no matter how well they perform their job.
  • Definition drift. If your data team changes what counts as “active” between quarters, your trend line becomes meaningless, and you’re comparing two different metrics wearing the same name.

The metric “can be deceptive,” as Gainsight’s guide on DAU/MAU puts it, and it works best when read alongside retention and revenue signals rather than in isolation. Andrew Chen has made a similar point about the ratio’s limits as an engagement measure, noting that context from your specific product category matters more than the number itself.

Reading the Ratio Correctly: Cohorts, Value Actions, and Supporting Metrics

A single DAU/MAU number tells you almost nothing on its own. It becomes useful once you break it apart by cohort and pair it with metrics that explain why it moved.

  • Retention cohort analysis. Track D0, D7, and D30 retention by acquisition cohort to see whether new users are sticking around long enough to become the daily habit that drives your ratio up.
  • Segment by acquisition channel. Users from a paid campaign often behave differently than organic sign-ups, and blending them hides which channel is actually building habitual usage.
  • Measure DAU of the core action, not raw opens. If you run a publishing app, count daily unique publishers, not daily unique launches. This aligns the metric with what you actually monetize.
  • Cross-check against revenue per user, session depth, and churn. A rising ratio paired with falling revenue per user is a warning sign, not a win.

Pro Tip: Build one dashboard that shows DAU/MAU next to your D7 retention curve and revenue per active user. If the ratio climbs while the other two flatten or drop, you’re likely looking at forced engagement, not real product improvement.

Improving Stickiness: Tactics Worth Testing

Raising DAU/MAU sustainably means getting more users to a real value moment more often, not just getting them to open the app more.

  1. Shrink time-to-value in onboarding. If a user’s first meaningful action takes five steps, cut it to two. Faster activation correlates directly with whether someone becomes a repeat user at all.
  2. Surface the core action, not secondary features. Redesign the home screen or dashboard around the one action that predicts retention, and de-emphasize everything else competing for that first tap.
  3. Test targeted notifications and email nudges, not blanket ones. A reminder tied to an unfinished task performs differently than a generic “come back” push, and you should A/B test both before rolling either out broadly.
  4. Set a guardrail metric before you launch any experiment. If a change lifts DAU but retention cohorts or revenue per user drop in the following weeks, that’s forced frequency, not stickiness, and you should roll it back.

Pro Tip: Run activation and notification experiments as small, reversible tests, and measure the downstream cohort effect two to four weeks out, not just the same-week DAU bump. A tool like AmmarAI’s marketing platform can help teams plan and test messaging variants faster without adding headcount to the process.

Getting the Measurement Right: Identity, Windows, and Monitoring

Bad identity resolution is the most common way teams end up with a DAU/MAU number they can’t trust.

  • Deduplicate across devices and sessions. Use a canonical user ID or deterministic identity stitching rather than counting device IDs, or the same person on phone and desktop inflates your count.

  • Prefer rolling 30-day MAU over calendar-month MAU for day-to-day monitoring since it’s less sensitive to calendar artifacts like short months or weekend-heavy weeks.

  • Pull from a consistent source. Whether that’s Firebase, Google Analytics, or your own event warehouse, keep the active-event definition identical across tools to avoid silently comparing two different metrics.

  • Set alert thresholds for sudden shifts, a ratio move of several points week over week usually means a tracking break, not a real user-behavior change, and deserves a data check before a product reaction.

A Product Manager’s Take on Chasing the Ratio

Most teams treat DAU/MAU as a scoreboard number to move, and that’s the wrong instinct. Treat it instead as a symptom. Define your core action around real value first, set your own baseline instead of an industry benchmark, then validate any movement against cohort retention before celebrating. Keep experiments small and reversible. A ratio that climbs for the wrong reason is worse than one that stays flat for the right one.

— Mike

Track DAU/MAU Alongside Your ASO Performance With Apptenium

A robust ASO platform can give your team one place to watch the full picture, not just the ratio in isolation. By connecting to Firebase, Google Analytics, and your ad networks, a tool may pull event-based activity, cohort behavior, and revenue signals into a single view, so you can define your own core action and see how it moves alongside downloads, keyword rankings, and search visibility.

Apptenium

That matters because a stickiness number without install and ranking context tells half the story. If your DAU/MAU is climbing but organic installs are flat, Apptenium’s AI-powered listing recommendations can show whether the gap sits in acquisition, not retention. Teams already using the platform to monitor performance metrics can see how visibility improvements show up in real user behavior over time, the kind of before-and-after story you’ll find in Apptenium’s customer results. If you’re ready to see how your own app’s stickiness stacks up against its store performance, check out Apptenium’s ASO plans and start with a free scan.

Sources

FAQ

What Is a Good DAU/MAU Ratio?

There’s no single good number. Social apps often exceed 40 to 50 percent, B2B SaaS products average closer to 31 percent, and low-frequency products can be healthy well below that. Compare against your own historical baseline, not a competitor’s category.

What Is the Difference Between DAU and MAU?

DAU counts unique users active in a single day; MAU counts unique users active over a trailing 30 days. Dividing DAU by MAU gives you the stickiness ratio.

What Does DAU/MAU Mean?

DAU/MAU means the percentage of your monthly user base that engages with your product on a given day, a core measure of product stickiness.

How Is DAU Calculated?

DAU is calculated by counting unique users who trigger a defined active event, an app open, a core action, or a conversion, within a single calendar day, using a deduplicated user identifier.

← Back to Guides · Home