WebmasterID logoWebmasterID
Analytics metrics

Day-N retention (D1/D7/D30)

Day-N retention measures the percentage of a user cohort that returns on a specific day after first use — D1, D7, and D30 being the common checkpoints. It is a core mobile and product retention curve. The subtlety is that 'returned on day N' has three competing definitions — classic (exactly day N), range (by day N), and rolling — which produce different numbers from the same data, so the definition must always be stated.

Partially verified

What this means

Day-N retention = (users from a cohort who were active on day N) ÷ (cohort size) × 100, where day 0 is first use. D1, D7, and D30 are conventional checkpoints that together sketch a retention curve. Mobile and product analytics rely on it to judge whether new users form a habit: a steep early drop with a flattening tail is the typical shape.

Three definitions that disagree

The same cohort yields different retention numbers depending on the definition. 'Classic' (or day-N) retention counts users active exactly on day N. 'Range' (or N-day) retention counts users active at any point up to day N. 'Rolling' (or unbounded) retention counts users active on day N or later. Classic is the strictest and lowest; range and rolling are more forgiving and higher. Tools default to different ones, so a D7 figure from one product is not comparable to another's unless the definition matches. Always state which definition and what 'active' means.

This page is educational and not financial advice.

How it appears in analytics and logs

Higher day-N retention means more of the cohort came back at that checkpoint — a habit-formation and value signal. Because the three definitions disagree, a 'D7 retention' number is only interpretable once you know which one produced it.

Diagnostic use case

Track how well a product holds a cohort over time using fixed checkpoints (D1/D7/D30), to compare onboarding and habit formation across cohorts.

What WebmasterID can help detect

WebmasterID records first-party cohort and return events, so retention curves can be built from defined activity events without cross-site or cross-app tracking.

Common mistakes

Privacy and accuracy notes

Day-N retention aggregates cohort return counts and needs no third-party identifiers. This page is educational and not financial advice.

Related pages

Sources and verification notes

Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.