What is user engagement?
User engagement is how often people come back to a product and how much of it they use when they do.
It works as a proxy. Nobody wants engagement for its own sake. Teams want retention and revenue, and engagement is the signal that usually moves first. That makes it useful for spotting change early, and a weak goal on its own, because people can be busy in a product without getting anything done.
How do you measure user engagement?
You measure user engagement with a small set of behavioural metrics: active users, stickiness, retention, session frequency, feature adoption and depth of use.
- Active users (DAU, WAU, MAU): unique people who did something meaningful in a day, week or month. Pick the interval that matches how often the product is meant to be used. See DAU, WAU and MAU.
- Stickiness: DAU divided by MAU, the share of monthly users who show up on a typical day.
- Retention rate: the percentage of a sign-up cohort still active after a set period, for example day 30 or week 8.
- Session frequency: how often the same person returns, which tells you more than a high total count.
- Feature adoption: the share of active users who use a specific feature at least once in the period.
- Depth of use: core actions per session, such as reports created or tickets closed. Time spent is a weaker stand-in for this.
Stickiness is calculated as (DAU / MAU) x 100. A product with 2,000 daily and 10,000 monthly active users has a stickiness of 20%.
Google's HEART framework, published by Kerry Rodden and colleagues in 2010, puts engagement next to Happiness, Adoption, Retention and Task success, which keeps engagement from being read on its own.
What is a KPI for engagement?
A KPI for engagement is the one metric you commit to that shows whether people keep doing the thing your product exists for. Common choices are stickiness, 30-day retention and weekly core actions per active account.
The core action depends on the product. For a reporting tool it might be reports shared with a colleague. A design tool might count files edited by more than one person. Choose it from what customers pay for, then set the interval. A tool people open once a month will look like it's failing on a daily metric.
Pair the KPI with a counter-metric so it can't be gamed. If sessions per week go up while finished tasks go down, people are probably coming back because they couldn't finish the first time.
What do engagement metrics miss?
Engagement metrics miss the reason behind a change. They show what happened in usage and can't explain why.
A drop of 8% in weekly active users arrives with no explanation attached. Time on a page is ambiguous too. Nine minutes on a settings form could mean someone is thorough or someone is lost. Averages hide the shape underneath, so a stable DAU can be a loyal core plus steady churn that only a cohort view would reveal.
Getting the reason means asking the people involved, ideally on the screen where their behaviour changed and while the moment is still fresh.
How do you improve user engagement?
You improve user engagement by making the core task easier and giving people a reason to return that fits their actual work.
- Shorten the path to the first useful result. The first few sessions decide whether a habit forms, so cut onboarding steps that lead nowhere.
- Remove steps that depend on someone else. Waiting for an admin or a colleague breaks the habit before it starts.
- Tie the product to a schedule the user already has, such as a weekly report, a sprint review or a month-end close.
- Announce changes where they happen. A message on the screen that changed reaches active users at the moment it's relevant.
- Ask, then show what you did with the answer. People keep using a product that visibly responds to them. That cycle is the customer feedback loop.
User engagement for enterprise product teams
In a large product organisation, a dashboard shows engagement on a module fell, and five teams each have a different theory about why.
Segment before you explain. Admins in an enterprise account may log in monthly by design, and averaging them with daily users hides what both groups are doing. Then attach evidence to the number: which accounts changed behaviour, what those users said in surveys, tickets and calls, and how many of them said it. An explanation built that way survives a roadmap review, and the decision that follows can be traced back to it months later.
How Usersnap explains changes in user engagement
Usersnap puts the reason next to the metric by asking users inside the product and grouping what they say.
- In-app surveys: micro-surveys with NPS, CSAT or CES raters can be shown on specific pages or to specific user groups, and, on plans that include it, triggered by an event in your app, such as finishing a step.
- Announcements and changelog: Announcements tell users about a change inside the product, with targeting rules, a schedule and statistics for each one. Past announcements can be collected into a changelog.
- Topic and sentiment: Sentiment Sensor tags each response by topic and sentiment as it arrives, so you can see shifts across topics and over time.
- Asking your AI assistant: the MCP connector lets ChatGPT, Claude or Cursor query your live workspace with your own permissions, for example "what are users saying about the new reporting screen?"
Sentiment Sensor is included on Professional plans and above, and available as an add-on on Starter and Growth.
User engagement FAQ
What is a good user engagement rate?
There's no universal benchmark, because a good rate depends on how often the product is meant to be used. Compare against your own earlier cohorts and against products people use on a similar schedule.
What counts as user engagement in Google Analytics?
In Google Analytics 4, an engaged session is one that lasts longer than 10 seconds, includes a key event, or has at least two page or screen views. Engagement rate is engaged sessions divided by all sessions.
What is the difference between user engagement and product adoption?
Product adoption is whether someone starts relying on a product or feature. Engagement describes what happens after that, and how consistently it continues.
What is the difference between user engagement and customer engagement?
User engagement measures behaviour inside the product. Customer engagement is wider and covers every interaction with the company, including support, success calls, community and email.
Related terms
See how product teams find the reason behind a change in engagement.
.svg)
