Retention measurement

From MozillaWiki
Jump to: navigation, search
Please use "Edit with form" above to edit this page.


Retention measurement
Stage Shelved
Status `
Release target `
Health OK
Status note Internal tracking


Product manager Asa Dotzler
Directly Responsible Individual Saptarshi Guha
Lead engineer `
Security lead `
Privacy lead `
Localization lead `
Accessibility lead `
QA lead `
UX lead `
Product marketing lead `
Operations lead `
Additional members Blake Cutler, Chris Jung, Dave Townsend

Open issues/risks


Stage 1: Definition

1. Feature overview

This feature adds the profile creation date to the Blocklist ping. We will use this data point to estimate aggregate retention across Firefox versions, OS, locale, and geography.

We want to know the date when a user first tries Firefox; we think that the profile creation date is a good proxy for this. We are open to suggestions of better or easier to implement proxies.

For the first 63 days, the exact profile creation date is reported back. After 63 days, the data sent is a default value e.g. 0.

2. Users & use cases

Users: consumers of product dashboards (e.g. nightly reports and rapid release reports). With this new measurement, we can track retention across versions e.g. 50% of new users who downloaded FF 8 still use it after 10 days vs 47% of new users who downloaded FF7. The trends give us an measure of the adoption and retention rates across versions, locales and OS.

3. Dependencies


4. Requirements




Stage 2: Design

5. Functional specification


6. User experience design


Stage 3: Planning

7. Implementation plan


8. Reviews

Security review


Privacy review


Localization review




Quality Assurance review


Operations review


Stage 4: Development

9. Implementation


Stage 5: Release

10. Landing criteria


Feature details

Priority `
Rank 999
Theme / Goal User Retention
Roadmap Firefox Desktop
Secondary roadmap Firefox Mobile
Feature list Desktop
Project `
Engineering team `

Team status notes

  status notes
Products ` `
Engineering ` `
Security ` `
Privacy ` `
Localization ` `
Accessibility ` `
Quality assurance ` `
User experience ` `
Product marketing ` `
Operations ` `

Switching back to P2 -- only Asa should be changing that value. This has been retired. We are moving this information to the Metrics Data Collection Ping.