Retention measurement

Please use "Edit with form" above to edit this page.

Status

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

{{#set:Feature name=Retention measurement

|Feature stage=Shelved |Feature status=` |Feature version=` |Feature health=OK |Feature status note=Internal tracking }}

Team

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

{{#set:Feature product manager=Asa Dotzler

|Feature feature manager=Saptarshi Guha |Feature lead engineer=` |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=` |Feature ux lead=` |Feature product marketing lead=` |Feature operations lead=` |Feature 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

`

Non-goals

`

Stage 2: Design

5. Functional specification

`

6. User experience design

NA

Stage 3: Planning

7. Implementation plan

`

8. Reviews

Security review

`

Privacy review

`

Localization review

`

Accessibility

`

Quality Assurance review

`

Operations review

`

Stage 4: Development

9. Implementation

`

Stage 5: Release

10. Landing criteria

` {{#set:Feature open issues and risks=` |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. |Feature users and 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. |Feature dependencies=` |Feature requirements=` |Feature non-goals=` |Feature functional spec=` |Feature ux design=NA |Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=` |Feature landing criteria=` }}

Feature details

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

{{#set:Feature priority=`

|Feature rank=999 |Feature theme=User Retention |Feature roadmap=Firefox Desktop |Feature secondary roadmap=Firefox Mobile |Feature list=Desktop |Feature project=` |Feature engineering team=` }}

Team status notes

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

{{#set:Feature products status=`

|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=` |Feature security health=` |Feature security notes=` |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=` |Feature qa notes=` |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}

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.