Program Management/Programs/Telemetry/Improve Opt-in: Difference between revisions
(Created page with "=Goal= The current Telemetry opt-in rate is roughly 2%. The rate needs to improve to 10%+ in order for the data to be meaningful. want to get 10% plus on release channel dev (ni...") |
|||
| (35 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
=Goal= | =Goal= | ||
It is thought that 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. The issue with Telemetry data lies in the sample population. Because Telemetry is opt-in, the sample population is not random and therefore needs to be very large (80-90%) to answer a broad range of questions. It may still be possible to answer specific questions with a smaller sample size (metrics can engage on an ongoing basis to assist with determination of whether a question can be answered). Alternatively, the existing sample population may contain enough variety to be representative. | |||
===Release and Beta channels=== | |||
Current: ~2%<br/> | |||
Goal: | |||
- | |||
===Nightly (M-C) and Aurora channels=== | |||
Current: ~2% <br/> | |||
Goal: ~100%<br/> | |||
<br/> | |||
Nightly and Aurora have small user bases. It is important to have as close to full adoption as possible in order to obtain meaningful data. Note that the users on these channels are assumed to be more technically savvy and interested in contributing to the improvement of Firefox. | |||
==Investigation== | |||
The metrics team (Chris Jung) will investigate to see if the current Telemetry data is representative based on the information that we have available from daily add-on pings. See {{bug|698848}}. | |||
=Tactics= | =Tactics= | ||
The following are some tactics that may be used to increase the opt-in rate for Telemetry. | The following are some tactics that may be used to increase the opt-in rate for Telemetry. | ||
==Change to opt-out policy== | ==Change to enabled by default (opt-out policy) on Aurora and Nightly== | ||
Will change to enabled by default (opt-out policy) on Aurora and Nightly channels. See {{bug|699806}} Enable Telemetry by default on Nightly and Aurora channels. | |||
<bugzilla> | |||
{ | |||
"id": "699806,702284,728340,728350,701182,723129,725407,725987,733522,735444,737596,701178,819732" | |||
} | |||
</bugzilla> | |||
==Fix current desktop opt-in ui== | |||
Issues with the current opt-in UI: | |||
* UI may disappear quickly | |||
* UI may be hidden in another tab | |||
These issues are related to the prompt mechanism (used for know your rights message) not being designed to be used heavily. | |||
<bugzilla> | |||
{ | |||
"id": "691951,697860,737600" | |||
} | |||
</bugzilla> | |||
==Improve Telemetry opt-in advertising== | |||
The current Telemetry notification has not provided the opt-in rates that we would like to see to gather meaningful information from the Firefox population. We should look for alternative ways to advertise Telemetry. We can look to use the Mozilla blog (others?) to promote Telemetry and request user help with improving the performance of Firefox. | |||
<bugzilla> | |||
{ | |||
"id": "692861,683340,731433" | |||
} | |||
</bugzilla> | |||
== | ==Enable Telemetry on mobile== | ||
Telemetry needs to be added to the mobile native UI. | |||
<bugzilla> | |||
{ | |||
"id": "696076,699513,702281" | |||
} | |||
</bugzilla> | |||
Latest revision as of 15:44, 10 December 2012
Goal
It is thought that 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. The issue with Telemetry data lies in the sample population. Because Telemetry is opt-in, the sample population is not random and therefore needs to be very large (80-90%) to answer a broad range of questions. It may still be possible to answer specific questions with a smaller sample size (metrics can engage on an ongoing basis to assist with determination of whether a question can be answered). Alternatively, the existing sample population may contain enough variety to be representative.
Release and Beta channels
Current: ~2%
Goal:
Nightly (M-C) and Aurora channels
Current: ~2%
Goal: ~100%
Nightly and Aurora have small user bases. It is important to have as close to full adoption as possible in order to obtain meaningful data. Note that the users on these channels are assumed to be more technically savvy and interested in contributing to the improvement of Firefox.
Investigation
The metrics team (Chris Jung) will investigate to see if the current Telemetry data is representative based on the information that we have available from daily add-on pings. See bug 698848.
Tactics
The following are some tactics that may be used to increase the opt-in rate for Telemetry.
Change to enabled by default (opt-out policy) on Aurora and Nightly
Will change to enabled by default (opt-out policy) on Aurora and Nightly channels. See bug 699806 Enable Telemetry by default on Nightly and Aurora channels.
Bugzilla query error
Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1
Fix current desktop opt-in ui
Issues with the current opt-in UI:
- UI may disappear quickly
- UI may be hidden in another tab
These issues are related to the prompt mechanism (used for know your rights message) not being designed to be used heavily.
Bugzilla query error
Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1
Improve Telemetry opt-in advertising
The current Telemetry notification has not provided the opt-in rates that we would like to see to gather meaningful information from the Firefox population. We should look for alternative ways to advertise Telemetry. We can look to use the Mozilla blog (others?) to promote Telemetry and request user help with improving the performance of Firefox.
Bugzilla query error
Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1
Enable Telemetry on mobile
Telemetry needs to be added to the mobile native UI.
Bugzilla query error
Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1