Measurement

Retention

Retention is the continued appropriate use of a product, service, system, or relationship over time when repeated use is expected or valuable.

Concept facts

Retention is the continued appropriate use of a product, service, system, or relationship over time when repeated use is expected or valuable.

Also known as
User retention, service retention, continued use, repeat use.
Used in
Product analytics, service performance, UX measurement, subscription services, internal systems, digital transformation, and product health review.
Interpret with
Adoption, engagement, activation, outcome metric, user trust, service value, and drop-off rate.

Plain-language explanation

Retention measures whether users continue to use a service after initial adoption. In public services, the ideal outcome may be successful completion and no need to return.

Why it matters

Retention can reveal continued value or workflow fit, but it must be interpreted with the service model. High retention is not automatically good, and low retention is not automatically bad.

Use contexts

  • users are expected to return over time
  • staff repeatedly use a workflow tool
  • learners continue through a course
  • customers maintain use of financial or telco services
  • service owners monitor product health

Application guidance

Define whether repeated use is actually expected, measure retention over meaningful intervals, and separate healthy retention from friction-driven return.

Practical example

An edtech platform expects learners to return weekly for modules and assignments. Retention drops after the first assignment because learners do not understand feedback status or resubmission requirements. The UX consequence is reduced course completion, higher support queries, weaker learning outcomes, and misleading assumptions about motivation.

Interpretive boundaries

Retention is not always a valid success metric. It should not reward dependency, confusion, repeated checking, or inability to exit a service.

Applied at Userhub

Userhub uses retention analysis when continued use is meaningful for the product, service, or workflow. In UX Lab work, retention is interpreted with task success, service purpose, support burden, and user outcome.

See Userhub UX Lab for applied UX research and evaluation context.

Sources and references

Rodden, K., Hutchinson, H., & Fu, X. (2010). Measuring the user experience on a large scale: User-centered metrics for web applications. CHI ’10 Extended Abstracts on Human Factors in Computing Systems. https://doi.org/10.1145/1753326.1753687

Albert, B., & Tullis, T. (2022). Measuring the user experience: Collecting, analyzing, and presenting UX metrics (3rd ed.). Elsevier.

Government Digital Service. (n.d.). Measuring success. GOV.UK Service Manual. https://www.gov.uk/service-manual/measuring-success

Croll, A., & Yoskovitz, B. (2013). Lean analytics: Use data to build a better startup faster. O’Reilly Media.

Cite this entry

APA

Userhub. (2026). Retention. UX Reference. https://userhub.com.bd/reference/retention/