Skip to content

Understand metrics and retention

Choose a metric that matches your product question. Counting actions, people, and visits produces different answers even when you select the same event.

MetricWhat it counts or calculates
Unique usersDistinct recorded identities with qualifying activity during the period.
Conversion ratePeople in the denominator who also perform the numerator event, divided by people with meaningful activity or the explicit denominator event. This is not an ordered funnel.
StickinessDaily active users divided by active users in a trailing 30-day period.
Session countDistinct visits with qualifying activity.
Session conversion rateSessions with the numerator event divided by meaningful sessions, or denominator-event sessions.
Observed session durationAverage time between the first and last recorded events in qualifying sessions. It is not a measurement of continuous attention.
Event occurrence countNumber of recorded custom-event occurrences.
Occurrences per unique user / per sessionCustom-event count divided by the people or sessions containing those events.

For example, five exports by one person can mean 5 occurrences, 1 unique user, and several or one session. Counts depend on what your app actually sends.

Movcues saved Demo activation overview dashboard with a signup count, onboarding funnel, and retention trend.
A saved custom dashboard combines three views of the synthetic product journey. Demo workspace; synthetic data only.

A retention card groups people by their first matching Start event in the selected period and checks for the Return event in later time buckets. You can choose a specific custom event or Any meaningful event.

  • Cohorts → Start-event date groups people by when they started.
  • Current Segment comparisons uses membership now, not membership at the time of the original event.
  • Cohort grid shows bucket-by-bucket results; Retention trend compares the return pattern.
  • Daily, weekly, or monthly granularity changes the bucket size. Analytics buckets use UTC. The starting bucket (D0/W0/M0) can include the initial action when it also matches the return-event choice.
  • Incomplete periods have not had enough observation time. Small cohorts can change sharply after a few visits.

Example: start with project_created and return with report_exported. This measures observed later use, rather than assuming any subsequent page visit represents value.

Movcues retention card configuration using signup_completed as the start event and feature_explored as the return event.
Choose a start and return event to define retention. The preview uses synthetic activity. Demo workspace; synthetic data only.

Anonymous browser identities and identified accounts are not interchangeable. Historical activity keeps the identity recorded with it; do not assume all pre-login activity is reassigned to an account. See Users.

Use the same filters and time buckets when comparing periods. A dashboard comparison is evidence of a difference, not proof of its cause.

Related: Configure cards · Funnels.