Program Management/Programs/Telemetry/Improve Opt-in: Difference between revisions
Line 3: | Line 3: | ||
===Release channel=== | ===Release channel=== | ||
Current: ~2% | Current: ~2%<br/> | ||
Goal: 10%+ | Goal: 10%+ | ||
Revision as of 17:30, 11 October 2011
Goal
The current Telemetry opt-in rates do not provide enough data to be useful. In general, Telemetry is only useful if users are providing feedback.
Release channel
Current: ~2%
Goal: 10%+
Nightly (dev) channel
Current: Goal: 50%+
Tactics
The following are some tactics that may be used to increase the opt-in rate for Telemetry.
Change to opt-out policy
metrics pursuing opt-out policy - follow up with them to see how they're progressing Daniel for follow-up next week will require security review
Change opt-in ui
the opt-in may be hidden in another tab or disappear quickly, not designed to be used heavily discuss ux goal
Replace opt-in UI https://bugzilla.mozilla.org/show_bug.cgi?id=692861
Current UI gets dismissed too easily https://bugzilla.mozilla.org/show_bug.cgi?id=691951
More aggressive opt-in https://bugzilla.mozilla.org/show_bug.cgi?id=683340
follow up with ux frontend metrics
dev (nightly) channel want to get 50% plus with more aggressive opt-in (which is incomplete need ux to design) chrome puts checkbox on the download page, Rob pushing back as firefox is multiseat and chrome is single user, doesn't address current users
Increase publicity
Mozilla blog