Retention
Retention groups activity into cohorts so you can see whether users return over time.
Before you start
Collect recurring activity with a stable user/device identity. Newly created apps or very recent cohorts may not have enough history.
Step by step
- Open the intended app's Retention page.
- Read the labels around Retention Heatmap, including each cohort period and return interval.
- Compare the first eligible interval for cohorts with sufficient history.
- Move across a row to see how that cohort changes over later intervals.
- Compare cohorts only when they have had time to reach the same interval.
- Use Analytics and your release history to investigate a change. A chart alone cannot prove a release caused the change.
Confirm it worked
Older cohorts have eligible return periods and new cohorts are interpreted as incomplete where appropriate. Check the SDK's identity and event flow if return activity is unexpectedly absent.
Troubleshooting
Do not interpret a future or unavailable interval as zero retention. Identity changes, reinstall behavior and sparse traffic can alter the apparent return pattern. Keep time windows and cohort definitions consistent when reporting results.