Product Engagement Metrics: DAU/MAU, Stickiness, and Feature Adoption — How to Actually Read Them

Engagement metrics answer the question that sits between signup and revenue: is anyone actually living in this product? DAU/MAU, stickiness, and feature adoption are the standard instruments — and each one is routinely misread, usually because teams copy a benchmark without asking whether it fits their product's natural rhythm.

Here's how to define, compute, and interpret each one honestly.

First, define "active" like you mean it

Every engagement metric inherits its meaning from your definition of an active user. "Opened the app" or "logged in" is the default in most tools — and it's engagement theater. A user who logs in, stares at a dashboard for four seconds, and leaves is not engaged; they're lost.

Define active as performing a core value action: created a document, ran a report, sent a message, completed a workflow. The test: would you be comfortable telling a customer "you used the product 12 times this month" based on this definition, to their face?

Expect your numbers to drop when you switch definitions — illustratively, a team moving from "logged in" to "completed a core action" might watch MAU fall 40%. Nothing changed except honesty. All figures below assume the honest definition.

DAU, WAU, MAU: pick the window that matches reality

DAU, WAU, and MAU count unique active users in a day, week, or month. The mistake is treating DAU as the serious one and the others as consolation prizes. In truth, every product has a natural frequency:

• Communication and collaboration tools: daily. DAU is the honest measure.
• Project, analytics, and workflow tools: a few times weekly. WAU is the metric; DAU will look "bad" forever and that's fine.
• Invoicing, payroll, reporting tools: monthly rhythm. MAU (and completion of the monthly job) is the truth. A payroll tool with "low DAU" is called a payroll tool.

Judging a weekly-natural product by DAU leads directly to engagement spam — notifications engineered to inflate daily opens while teaching users to ignore you.

Stickiness (DAU/MAU): what it actually measures

DAU/MAU divides average daily actives by monthly actives, yielding the fraction of your monthly users who show up on a typical day — a proxy for how many days per month your users need you. A DAU/MAU of 25% roughly means the average monthly user is active 7–8 days a month.

Illustrative reference points, to be taken as orientation rather than targets:

Three reading rules:

1. Compare against your own past, not other products. The cross-product comparison is dominated by category rhythm, not quality.
2. Watch the components. DAU/MAU rises when DAU grows — or when MAU shrinks. A stickiness "improvement" during a signup slump is your casual users disappearing, not your product getting stickier.
3. For weekly-rhythm products, track WAU/MAU instead. It answers the same question at the frequency that matters: what share of monthly users show up in a given week?

Feature adoption: the layer under the topline

Topline engagement tells you that users come back; feature adoption tells you what for — which is where roadmap decisions live. Measure three things per feature:

• Adoption rate: share of active users who used the feature in the period (be strict about the denominator — "% of users who could use it," e.g. plan-eligible users, not all signups).
• Depth / repeat usage: share of adopters who used it 3+ times. First use is curiosity; third use is a habit forming.
• Retention correlation: do adopters of this feature retain better than comparable non-adopters?

That last one is the strategic gold, with the standard caveat: correlation isn't causation — power users adopt everything. The pragmatic protocol: find features whose adopters retain dramatically better (illustratively, users of a scheduling feature retaining at 65% vs. 35% at month 3), form the hypothesis that the feature drives commitment, then test it by nudging a subset of new users toward it and comparing downstream retention against the un-nudged.

A useful map is the adoption matrix: plot features by adoption rate × retention correlation.

• High adoption, high correlation → your core. Protect and polish.
• Low adoption, high correlation → your onboarding's biggest missed opportunity. Promote.
• High adoption, low correlation → table stakes. Maintain, don't over-invest.
• Low adoption, low correlation → deprecation candidates. Every feature you keep costs UI space and maintenance.

Setting targets and alerts that respect variance

Engagement metrics wobble; the art is separating wobble from signal.

• Set targets on 4-week rolling averages, not single weeks. A weekly WAU number swings with holidays, launches, and luck; the rolling view shows the trend a target can honestly bind to.
• Alert on sustained deviation. "Stickiness below its 8-week average for 3 consecutive weeks" is an alert worth waking up for; "DAU down 6% yesterday" is a notification that trains you to ignore notifications.
• Segment your engagement targets. A blended WAU target hides the split that matters: engagement of this quarter's cohorts versus the legacy base. New-cohort engagement responds to your current product decisions; blended engagement responds to your history.
• Pair every growth target with an engagement floor. "Grow MAU 15% this quarter while keeping new-cohort WAU/MAU above 30%" (illustrative) prevents the classic failure of buying growth that evaporates. The floor turns engagement from a report into a constraint — which is what makes teams take it seriously.

Reading engagement as a system

The metrics interlock into a diagnostic:

• MAU up, stickiness down → acquisition is outrunning activation; new users sample and drift.
• Stickiness up, MAU flat → the core deepens but growth stalled; a retention win and an acquisition warning.
• Both flat, feature adoption shifting → users are migrating within the product; the roadmap should follow them.
• Engagement strong, revenue flat → a monetization gap, not a product one; pricing and packaging deserve the quarter.

And the pairing that keeps everyone honest: engagement metrics with cohort retention curves. Engagement is the leading indicator; retention flattening above a healthy floor is the confirmation. If engagement rises but cohort curves don't budge, you've probably gamified opens rather than delivered value.

Pair the numbers with qualitative signal

Engagement metrics tell you what changed, rarely why. The efficient pairings: when a feature shows high adoption but low depth (everyone tries it once), watch a handful of session replays of first uses — the abandonment reason is usually visible within ten minutes. When a previously sticky cohort's usage declines, a two-question survey to the slipping users ("what were you trying to do? what got in the way?") outperforms weeks of dashboard archaeology. And when stickiness rises, interview a few of the newly habitual users to learn which workflow hooked them — that's the story your onboarding should tell next. Quantitative finds the smoke; qualitative finds the fire.

The bottom line

Define active as a value action, judge frequency against your product's natural rhythm, read stickiness with its components, and treat feature adoption as retention hypotheses to test rather than trivia. Engagement metrics won't tell you what to build — but read this way, they'll reliably tell you where to look.

Growth Pilot puts engagement, cohort retention, and revenue in one AAARRR cockpit — with A/B testing built in for the moment your feature-adoption hypothesis needs an honest verdict.