Free calculator
"Active members" can rise while your program is quietly getting less valuable. Loyalty Retained Yield (LRY) is the ratio that catches it — enter this period and last period to see whether your actives are really pulling ahead, or whether the gain is coming from database dilution.
Pull these from whatever cohort reporting you already have — no exact precision needed to see the direction.
LRY = 1 means active members generate revenue in exact proportion to their share of the database — being "active" carries zero revenue premium. In practice this is usually a sign the active window itself is too loose to mean much, since a recently-transacting customer should almost never be worth exactly the same as the database average, which includes long-dormant members.
LRY > 1 is the expected, healthy direction — actives punching above their weight. The higher above 1, the more concentrated your value is in that core. But very high LRY (5x, 10x+) is worth a second look too — it can mean the active window is too strict, crediting only a tiny elite core and undercounting everyone else who's genuinely valuable.
LRY < 1 means your defined "active" segment is worth less per capita than the database average — your "inactive" bucket is outperforming your "active" one. The most common and most actionable explanation is a miscalibrated active window: it's letting in low-value one-time visitors while genuinely high-value customers fall outside it and get mislabeled inactive. But it's worth ruling out before assuming it — some business models (subscription/dues-based programs, or categories built on infrequent big-ticket purchases) can produce LRY near or below 1 without anything being broken; it just means recency of activity isn't a good proxy for value in that category. Either way, LRY below 1 is the number that tells you to go check the definition, not skip straight to a fix.
| Component | Prior | Current | Change |
|---|
LRY = active-revenue share ÷ active-database share — how much more an active member is worth than the database average. The interpretive bands used for the scorecard cards above are illustrative starting points for a conversation, not formal industry benchmarks.
Always read LRY alongside its two components, the same way comparable sales are read alongside traffic and average check — a shift in the ratio caused by redefinition rather than behavior should be visible, not hidden inside a single number.
Turning a metric like this into a repeatable, board-ready measurement framework — and then rebuilding the program mechanics to actually move it — is exactly what nventiv's n-dicators and n-gagement Schemas are built for, together.
Book a discovery call