MRU

What MRU Means in Billing and Retention Terms

Monthly Retained User is a retention-based usage unit, not a simple signup count. In the context of identity billing, it measures returning users in the month, so the metric reflects actual retained engagement rather than one-off registrations.

Why the Denominator Matters

MRU only works when the counting rule is clear. If one product bills on retained users and another bills on all signups, the numbers are not directly comparable, because the denominator changes what the price signal actually represents.

This is why teams should treat MRU as a commercial measurement convention as much as a user metric. It helps separate active, recurring value from inflated acquisition totals, which is especially important when finance, product, and procurement teams are comparing options.

How MRU Differs From MAU and Signup-Based Models

MRU is closely related to MAU, but it is narrower in what it counts. MAU often captures anyone active within a month, while MRU focuses on users who return after signup, which can exclude first-time registrations that never become recurring usage.

That distinction changes how vendors present value. A service can look cheaper or more expensive depending on whether it prices by active monthly users, retained monthly users, or raw account creation, so the metric definition must be read before comparing offers.

What Practitioners Should Verify Before Using MRU

Before adopting MRU in a contract, dashboard, or benchmark, teams should confirm how "retained" is defined, which events qualify a user as returning, and whether the count is tied to identity, account, device, or session. Small wording differences can materially change the result.

In practice, MRU is most useful when the organisation wants a billing or product metric that rewards repeat usage rather than transient signups. It is less useful if the vendor does not publish a stable counting rule or if the metric is being used interchangeably with broader monthly activity measures.