Retention Cohorts

Compare cohort retention over time and reveal how activation behavior, plan, and acquisition source change long-term use. The screen connects Cohorts and Retention so product analysts can find the “New cohort” action while checking d7 retention and d30 retention.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Activated in 1 day · 52% and Invited team · 47%, rather than an empty visual shell.

Retention Cohorts
Use this template in Figr

Template facts

Screen

Analytics

Primary action

New cohort

Pattern

Analytics

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Product analysts need a clear “New cohort” action without losing sight of d7 retention, d30 retention and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: New cohort is clearly available where the task happens.
  • Main view: Cohorts keeps the starting point obvious.
  • Connected view: Retention supplies nearby context.
  • Metric: D7 retention is visible with a meaningful value.
  • Another signal: D30 retention helps people judge what to do next.
  • Representative record: Activated in 1 day · 52% makes the example specific.
  • Second record: Invited team · 47% shows the pattern works beyond one item.

States worth designing

  • No data for the chosen period; show what people can do instead of leaving a blank panel.
  • Loading cohorts without changing the layout unexpectedly.
  • Partial or delayed metrics; explain the problem and preserve work.
  • Permission denied for retention; clarify who can continue.
  • Success after choosing New cohort; confirm the result and the next step.
  • Network or data refresh failure; offer a retry without losing context.

Where this screen sits in the flow

Cohorts → Retention → New cohort → Review outcome

Patterns used

Analytics, Cohorts, Retention, Segments, accessible states, contextual actions

Why these choices work

Make time ranges, filters and metric units clear. Show the data behind each trend so readers can test what changed.

In this design, people should be able to compare Activated in 1 day · 52% with Invited team · 47%. Make d7 retention clear, then use d30 retention to explain whether the next step needs attention.

Before handing this to a designer or engineer, check keyboard focus, error copy, permissions and what happens after they choose the “New cohort” action. The happy path alone is not enough.

Related UI examples: Funnel Analysis, Experimentation, Event Analytics.

Start from this in Figr

Design a retention cohorts screen for our existing software product. Use our real design-system tokens, components and product language. Show Cohorts and Retention, include believable records such as Activated in 1 day · 52%, and make new cohort easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr