Program Management/Programs/Telemetry/Improve Opt-in: Difference between revisions

Program Management/Programs/Telemetry/Improve Opt-in (view source)

786 bytes added , 1 November 2011

Confirmed users

2,473

edits

@@ Line 1: / Line 1: @@
 =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.
+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.
+==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}}.
+Lawrence will investigate changing Telemetry to an opt-out option.
 ===Release channel===
 Current: ~2%<br/>
-Goal: 10%+
+Goal:
 ===Nightly (dev) channel===
 Current: ~2% <br/>
-Goal: 50%+
+Goal:
 =Tactics=