# 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.

Canonical URL: https://manalens.dev/features/retention

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](https://manalens.dev/docs/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.

## Explore next

- [User profiles](https://manalens.dev/features/user-profiles)
- [Identity guide](https://manalens.dev/blog/website-visitor-to-steam-wishlist)
- [How collection works](https://manalens.dev/docs/privacy)

Implementation reviewed 2026-11-18.
