Engagement rate: what it is and how to measure it in SaaS

The engagement rate measures how intensely the base uses the product: how many users actually perform the action that represents value, over the total number of users, within a period. It is not a vanity metric about logins, but a picture of who truly gets value from what you ship.

The part that trips people up is that there is no single formula. Each product defines the key action that counts as engagement: sending a message, publishing a report, closing a deal inside the system, inviting a teammate. What matters is choosing the behavior that correlates with customers staying and growing, then measuring the share of the base that repeats it.

The general shape is simple: active users who perform the key action, divided by the total number of users, over the chosen period. What changes from one SaaS to another is the definition of active and of key action, and that is where the real work lives.

• Engagement rate = (users who do the key action ÷ total users) over the period.
• Define the value action before you calculate; without it, the number means nothing.
• Pick a window (day, week, month) that matches the product natural usage frequency.

A common approach is to anchor the key action to the North Star Metric, the metric that captures the value delivered to the customer. That way engagement rate stops being a loose number and starts measuring how many users reach the moment the product keeps its promise.

One of the best-known ways to measure engagement is the DAU / MAU ratio, daily active users divided by monthly active users. It answers a direct question: on how many days of the month does the typical user come back to the product.

A DAU/MAU of 50% suggests the average user opens the product about fifteen days a month, a sign of a strong habit; below 10% or 20%, usage tends to be occasional. Keep in mind the bar depends on the product type: a daily-use tool and software touched once a quarter cannot be judged against the same line.

Engagement has two dimensions worth separating. Breadth asks how many users in the base are active; depth asks how intensely each one uses it, how many key actions per session, how many features adopted, how much value over time.

A broad but shallow base (lots of people who show up and do little) is fragile. A smaller but deeper base is usually healthier, because it concentrates power users who extract a lot of value and pull expansion. Measuring breadth alone hides this contrast; looking at both dimensions together shows where the product really lands.

The reason engagement rate matters so much is that it is a leading indicator. Users who engage often and deeply tend to renew and buy more; users who fade from the product tend to cancel weeks or months later. Engagement moves before revenue, which is why it works as an early warning.

In practice, a drop in engagement inside an account is one of the most reliable signs of churn to come, with enough lead time for the team to act before the cancellation. On the other side, highly engaged accounts are the natural ground for upsell and cross-sell. Benchmark reports such as those from Benchmarkit show how retention and expansion sustain SaaS growth, and both begin with engagement.

Do not ask this metric for a universal good-or-bad number. Unlike financial metrics, engagement only makes sense against your own baseline and product type. The value is in the trend (rising or falling) and in comparing segments, plans and cohorts, not in copying a percentage from outside.

• Define the key action and keep the definition stable so you can compare over time.
• Segment: engagement by plan, by entry cohort and by customer profile reveals more than the overall average.
• Combine breadth and depth, and cross-check against retention to confirm the chosen action really predicts staying.

Done this way, engagement rate becomes the product health dashboard: it shows early where value is being delivered, where it is leaking, and where to invest to turn usage into recurring revenue.