Fatskills
Practice. Master. Repeat.
Study Guide: Principles of Product Management: User Engagement Metrics (DAU/WAU/MAU, Stickiness, Session Length, Frequency)
Source: https://www.fatskills.com/product-management/chapter/product-management-user-engagement-metrics-dauwaumau-stickiness-session-length-frequency

Principles of Product Management: User Engagement Metrics (DAU/WAU/MAU, Stickiness, Session Length, Frequency)

By Fatskills Exam Guides Team — the exam nerds behind 28,500+ quizzes and 2.1M practice questions across 500+ global exams.

⏱️ ~7 min read

User Engagement Metrics (DAU/WAU/MAU, Stickiness, Session Length, Frequency)


User Engagement Metrics (DAU/WAU/MAU, Stickiness, Session Length, Frequency) – Study Guide

What This Is

User engagement metrics measure how actively and meaningfully users interact with your product. They’re leading indicators of retention, monetization, and long-term success—critical for PMs to diagnose health, prioritize features, and justify roadmap decisions. Example: When Instagram launched Reels, they tracked DAU/MAU stickiness (daily active users as a % of monthly actives) to validate whether short-form video was driving habitual use, not just one-time views. A stickiness ratio >20% signaled product-market fit for the new format.


Key Terms & Frameworks

  • DAU (Daily Active Users): Unique users who engage with your product in a 24-hour period. Example: A meditation app counts a user as "active" if they complete at least one session.
  • WAU/MAU (Weekly/Monthly Active Users): Unique users active in a 7-day or 30-day window. Use case: WAU is useful for products with weekly habits (e.g., grocery delivery), while MAU suits less frequent use cases (e.g., tax software).
  • Stickiness (DAU/MAU or WAU/MAU): Formula: Stickiness = (DAU / MAU) × 100%. Measures how often users return. Benchmark: >20% is strong (e.g., social media), <10% suggests low habit formation.
  • Session Length: Average time a user spends in a single session. Context matters: Long sessions can signal engagement (e.g., Netflix) or friction (e.g., a confusing checkout flow).
  • Session Frequency: Average number of sessions per user in a given period (e.g., 3 sessions/week). Example: Duolingo tracks this to ensure users practice daily.
  • Retention Rate (Day 1, Day 7, Day 30): % of users who return after N days. Formula: Retention = (Returning Users on Day N / Users on Day 0) × 100%. Key insight: Day 1 retention >40% is a strong signal for habit-forming products.
  • Engagement Funnel (AARRR): Acquisition-Activation-Retention-Revenue-Referral. Focus: Engagement metrics live in the Retention stage.
  • North Star Metric (NSM): A single metric that best captures the core value your product delivers. Example: Airbnb’s NSM is "nights booked," while Slack’s is "messages sent in paid teams."
  • Engagement Heatmap: Visualizes where users drop off in a flow (e.g., onboarding, checkout). Tool: Hotjar or Amplitude.
  • Cohort Analysis: Groups users by sign-up period to compare behavior over time. Example: Compare Day 7 retention for users who signed up in January vs. February.
  • Time to First Value (TTFV): How quickly a user gets value from your product. Example: Calm’s TTFV is the time from app open to completing the first 3-minute meditation.
  • Engagement vs. Vanity Metrics: Engagement metrics (e.g., session length) tie to user value; vanity metrics (e.g., total downloads) don’t correlate with success.

Step-by-Step / Process Flow

How to diagnose and improve engagement as a PM:

  1. Define Your North Star Metric (NSM)
  2. Ask: "What’s the one action that best represents a user getting value from our product?"
  3. Example: For a fitness app, it might be "workouts completed per week," not "app opens."
  4. Action: Align your team around this metric (e.g., "Increase weekly workouts from 2 to 3").

  5. Instrument Your Funnel

  6. Map the user journey (e.g., onboarding-first session-repeat use).
  7. Tools: Amplitude, Mixpanel, or Google Analytics to track events (e.g., "workout_started," "workout_completed").
  8. Pro tip: Tag events with user properties (e.g., "new_user," "power_user") to segment later.

  9. Analyze Engagement Metrics

  10. Pull DAU/MAU stickiness, session frequency, and retention curves for your target segment.
  11. Red flags:
    • Stickiness <10%-Users aren’t forming habits.
    • Session length dropping-Possible friction or lack of value.
  12. Example: If session frequency is low, dig into why (e.g., notifications not working, content not personalized).

  13. Run Cohort Analysis

  14. Compare retention for different user groups (e.g., by acquisition channel, feature usage).
  15. Example: Users from Instagram ads have 30% Day 7 retention vs. 15% from Google Ads-double down on Instagram.
  16. Action: Identify "whale" cohorts (high retention) and replicate their behavior for others.

  17. Prioritize Experiments

  18. Use ICE (Impact, Confidence, Ease) to prioritize fixes:
    • Impact: Will this move the NSM? (e.g., "Reduce onboarding steps from 5 to 3").
    • Confidence: Do we have data/user feedback to support this? (e.g., 80% of users drop off at Step 3).
    • Ease: How hard is it to implement? (e.g., "Low effort: just remove a form field").
  19. Example: If session length is short, test:

    • A "continue where you left off" feature (for habitual users).
    • A progress bar (for new users).
  20. Iterate and Measure

  21. Launch A/B tests (e.g., "New onboarding flow vs. control").
  22. Track leading indicators (e.g., "time to first workout") before lagging indicators (e.g., "Day 30 retention").
  23. Pro tip: Use statistical significance (p < 0.05) to avoid false positives.

Common Mistakes

  • Mistake: Tracking DAU/MAU without segmenting by user type.
  • Correction: Segment by behavior (e.g., "power users" vs. "lurkers") or demographics. Why? A single DAU/MAU number hides critical differences (e.g., new users vs. churned users).

  • Mistake: Assuming longer session length = better engagement.

  • Correction: Context matters. Why? Long sessions in a productivity app might mean users are stuck; short sessions in a meditation app might mean they’re getting value quickly.

  • Mistake: Ignoring retention curves in favor of DAU/MAU.

  • Correction: Always pull Day 1, Day 7, and Day 30 retention. Why? DAU/MAU can be inflated by one-time users; retention shows true habit formation.

  • Mistake: Not tying engagement metrics to business outcomes.

  • Correction: Link engagement to LTV (Lifetime Value) or churn rate. Why? Stakeholders care about revenue, not just "active users."

  • Mistake: Over-optimizing for engagement at the expense of user experience.

  • Correction: Balance engagement with NPS (Net Promoter Score) or CSAT (Customer Satisfaction). Why? Dark patterns (e.g., infinite scroll) can boost DAU but hurt long-term trust.

PM Interview / Practical Insights

  1. Tricky Distinction: DAU vs. MAU vs. Stickiness
  2. Interviewer trap: "Why not just track DAU?"
  3. Answer: DAU alone doesn’t show habit formation. A product with 1M DAU and 10M MAU (10% stickiness) is less healthy than one with 500K DAU and 2M MAU (25% stickiness). Stickiness reveals whether users are coming back regularly.

  4. Leading vs. Lagging Indicators

  5. Interviewer question: "How do you know if a feature is working before retention improves?"
  6. Answer: Track leading indicators (e.g., "time to first value," "feature adoption rate") to predict future retention. Example: If users who complete onboarding in <2 minutes have 2x higher Day 7 retention, optimize for faster onboarding.

  7. Engagement vs. Retention

  8. Interviewer trap: "A feature increases session length but hurts retention. Is that good?"
  9. Answer: No—retention is the ultimate goal. Why? Long sessions without repeat use suggest users are stuck, not engaged. Example: A confusing tutorial might increase session length but frustrate users into churning.

  10. Stakeholder Pushback

  11. Scenario: "The CEO wants to increase DAU by 20% next quarter. How do you respond?"
  12. Answer: Ask: "What’s the underlying goal—habit formation, revenue, or something else?" Then propose a North Star Metric (e.g., "Let’s focus on increasing weekly active users who complete a workout, not just app opens").

Quick Check Questions

  1. Scenario: Your team wants to add a "daily streak" feature to a language-learning app. It increases DAU by 15% but drops NPS by 10 points. How do you decide?
  2. Answer: Don’t launch it. Why? NPS is a leading indicator of churn; a 10-point drop suggests users are frustrated, which will hurt long-term retention. Instead, test a less intrusive version (e.g., weekly streaks).

  3. Scenario: A social app’s DAU is growing, but session length is decreasing. What’s the most likely cause?

  4. Answer: Users are getting value faster (good) or the product is becoming less engaging (bad). Why? Dig into qualitative feedback (e.g., surveys, user interviews) to distinguish between the two. Example: If users say, "I can find what I need in 30 seconds now," it’s a win. If they say, "The feed is boring," it’s a problem.

  5. Scenario: Your e-commerce app’s stickiness is 12%. What’s the first thing you’d investigate?

  6. Answer: Retention curves and user segments. Why? 12% stickiness is low; check if certain cohorts (e.g., new vs. returning users) have higher retention, and identify drop-off points (e.g., post-purchase flow).

Last-Minute Cram Sheet

  1. Stickiness = DAU / MAU × 100%->20% is strong.
  2. Retention rate = (Returning Users on Day N / Users on Day 0) × 100%.
  3. Session frequency = Avg. sessions per user per period (e.g., 3/week).
  4. North Star Metric (NSM) = The one action that best captures user value.
  5. Cohort analysis = Compare behavior of users who signed up at the same time.
  6. Leading indicators (e.g., TTFV) predict future retention; lagging indicators (e.g., DAU) show past behavior.
  7. Long session length-good engagement (could mean friction).
  8. DAU alone doesn’t show habit formation—always check stickiness.
  9. ICE Score = Impact × Confidence × Ease (prioritize experiments).
  10. Balance engagement with NPS/CSAT—don’t optimize for metrics at the expense of user happiness.