
What is product stickiness? DAU/MAU ratio explained
Most SaaS teams track signups and churn. Product stickiness is the metric that sits between those two numbers and tells you whether people actually come back.
Definition
Product stickiness is the degree to which users return to a product repeatedly because they find it valuable. The standard measurement is the DAU/MAU ratio: daily active users divided by monthly active users, expressed as a percentage. A product with 2,500 DAU and 10,000 MAU has a 25% stickiness rate. As of April 2026, the median SaaS stickiness rate is 9.3%, and the average sits around 13% (Userpilot). Anything above 20% is considered good across industries; 50% or higher is elite territory that only a handful of products like messaging apps and social networks reach (Geckoboard).
The concept isn't new. Sequoia Capital has long used DAU/MAU as a core metric for evaluating consumer and SaaS investments, noting that "the standard DAU/MAU ratio is 10-20% with only a handful of companies over 50%" (Geckoboard).
How product stickiness works
Product stickiness is calculated by dividing daily active users by monthly active users, but the formula only works if you define "active" correctly. Page views and logins don't count. An active user is someone who performed a meaningful action that corresponds to your product's core value, like creating a document, sending a message, or completing a workflow. Get that definition wrong and the metric tells you nothing.
Here's the formula:
Stickiness Rate = (DAU / MAU) × 100One wrinkle that trips up B2B teams: calendar-day DAU/MAU punishes products that aren't used on weekends. A project management tool with perfect weekday engagement still maxes out around 71% (5/7 days). Gainsight recommends a workday-adjusted calculation for B2B SaaS, which typically pushes the real benchmark from the misleading 13% average to roughly 40% (Gainsight).
DAU/MAU also has a blind spot. David Sacks points out that "because DAU/MAU is inherently lagging due to its dependence on the MAU figure, any movement won't be noticeable immediately and may not be suitable for measuring the impact of product initiatives in the short term" (Sacks, Substack). If you shipped a feature yesterday and want to know if it moved the needle, DAU/MAU won't tell you for weeks.
For shorter feedback loops, try the Lness distribution instead. It measures how many days a user was active within a period: L4+/7 means four or more days in a week, L19+/28 means 19 or more in a month. More granular than a single ratio. Amplitude and Userpilot both recommend tracking Lness alongside DAU/MAU (Userpilot).
Product stickiness examples
Product stickiness benchmarks vary dramatically by category because different products have fundamentally different usage frequencies. A social media app used five times a day and a payroll tool used once a month aren't comparable on DAU/MAU alone, so context matters more than the raw number. Here are benchmarks as of 2026:
| Category | DAU/MAU range | Why |
|---|---|---|
| Social media and messaging | 50-80% | Network effects create daily habits |
| Productivity tools | 40-60% | Work requires daily use |
| B2B SaaS (workday-adjusted) | ~40% | Weekday-only usage, adjusted denominator |
| Gaming | 30-40% | Session-based engagement |
| B2C consumer apps | 20-50% | Wide range based on frequency expectations |
| B2B SaaS (calendar-day) | 10-20% | Weekend drag lowers the raw number |
| E-commerce | ~9.8% | Users buy occasionally, not daily |
Sources: Geckoboard, Userpilot, Statsig
Comparing your DAU/MAU to a product in a different category is meaningless. A 15% stickiness rate is poor for a messaging app and excellent for an e-commerce platform.
Why product stickiness matters for SaaS
Stickiness is a leading indicator of retention. Users who engage daily are far less likely to churn, and that compounds: companies with the highest net revenue retention posted median growth 83% higher than the population median in Benchmarkit's 2025 SaaS report.
But stickiness doesn't happen by accident. Three patterns drive it:
Onboarding speed. Users who activate within three days are 90% more likely to keep using a product (Userpilot). Speed to the "aha moment" is everything. WeMoney saw a 20% retention boost after integrating goal-setting directly into their onboarding flow (Amplitude).
Habit loops. Slack, Notion, Linear — products that embed into daily workflows build behavioral patterns that are genuinely hard to break. The Twilio State of Customer Engagement Report found 57% of consumers spend more with brands that personalize their experience (Amplitude). Onboarding that adapts to a user's role creates those early loops.
Feedback mechanisms. Collecting in-app feedback (NPS, CSAT) at the right moments identifies friction before it becomes churn. Timing is everything here. Survey a user mid-task and they'll dismiss it. Wait until they've completed a milestone and you'll get signal worth acting on.
Product stickiness in Tour Kit
Tour Kit addresses all three stickiness drivers through its package architecture: tours accelerate activation, adoption tracking identifies which features drive daily return visits, and milestone-triggered surveys capture feedback without annoying users mid-task. The @tour-kit/adoption package gives you the raw data to calculate feature-level stickiness, while @tour-kit/surveys deploys NPS or CSAT at the right moments.
None of this replaces building a product worth returning to. Tours and surveys are the instrumentation that tells you what's working and what's not. Stickiness comes from the product itself.
For implementation details on wiring tour completion into your DAU/MAU tracking pipeline, see DAU/MAU ratio and onboarding: how tours improve stickiness. For every onboarding KPI with formulas, see the onboarding metrics explained pillar page.
FAQ
What is a good product stickiness rate?
Product stickiness above 20% DAU/MAU is considered good across most industries. For B2B SaaS products measured on calendar days, 10-20% is average and anything above 25% is excellent. Social media and messaging apps routinely hit 50-80%, but comparing across categories is misleading because usage frequency expectations differ fundamentally.
How do you calculate product stickiness?
Product stickiness is calculated as (DAU / MAU) x 100. Divide daily active users by monthly active users and express it as a percentage. For B2B products, adjust the denominator for workdays only to avoid the weekend penalty that makes calendar-day ratios look artificially low.
What is the difference between stickiness and retention?
Product stickiness (DAU/MAU) measures how frequently active users return within a month. Retention measures whether users come back at all after a specific period. A product can have high retention but low stickiness if users stay active for 90 days yet only log in twice a month. Stickiness reveals engagement depth; retention reveals longevity.
Does onboarding affect product stickiness?
Onboarding directly affects product stickiness. Users who activate within three days are 90% more likely to keep using a product, and interactive tours reduce time-to-value by guiding users to meaningful actions faster. WeMoney saw a 20% retention boost from goal-setting in onboarding.
Related articles

What is a hotspot? In-app guidance element explained
Learn what a hotspot is in onboarding UX. Covers definition, accessibility, code examples, and when to use hotspots vs tooltips in your React app.
Read article
What is a product tour? (definition, types, and examples)
Learn what a product tour is, how it works technically, and when to use each type. Covers tooltips, hotspots, modals, and walkthroughs with code examples.
Read article
What is a slideout? In-app messaging element explained
Learn what a slideout is, how it differs from modals and drawers, and when to use slideout panels for in-app messaging and onboarding.
Read article
What is a tooltip? (and when to use tooltips in product tours)
A developer's definition of tooltips covering ARIA patterns, WCAG 1.4.13, the four tooltip types, and how tooltips work inside product tours.
Read article