Day and week retention for returning players
Measure day and week returns (D1, D7, D30) by first observed page or game event, using explicit user IDs and persistent anonymous IDs.
How to install ↗Start with observed account activity
The cohort date is the first observed page or product event. Choose weekly cohorts (weeks 0 to 12) or daily cohorts (days 0 to 30, including D1, D7, and D30). An optional breakdown splits cohorts by an event property such as plan. This is recurring retention, not rolling retention or an activation-event cohort.
Use a durable identity
Each user is an explicit user ID, else a user linked unambiguously to the anonymous ID, else the persistent anonymous ID. Events sent before consent carry no ID and are excluded.
Incomplete weeks are blank
The report marks weeks that have not completed as immature. A blank future cell is not zero retention. Use the project date picker to select cohort entry dates and the observation end date.
Frequently asked questions
Is there a retention report?
Yes. Users links to a day and week retention matrix. Configurable activation events and advanced retention variants remain planned.
Can anonymous visitors be part of retention?
Yes. The first-party anonymous ID persists across days, so anonymous returning visitors count. Explicit user IDs join activity across devices.
Start with a clear measurement model.
Install the SDK, then explore traffic and product activity with the same definitions.