Repository navigation
Bug 2081305 - Add studies and rollouts opt out events - #7656
Conversation
7bbf760 to
e8a95c9
Compare
Request for data collection review formAll questions are mandatory. You must receive review from a data steward peer on your responses to these questions before shipping new data collection.
What are the studies and rollouts opt-out rates for our users in mobile Firefox?
This will give us information into reachability of our clients in terms of incident response rollouts and experimental feature delivery.
No other options exist.
It is technically possible to cobble together a query that selects all enrollment status telemetry from users and filters to any that submit "RolloutsOptOut" or "StudiesOptOut" as the reason, but we don't get a clear picture of when it happens and this telemetry will be cheaper to query.
Note that the data steward reviewing your request will characterize your data collection based on the highest (and most sensitive) category.
This collection is documented in the Glean Dictionary at https://dictionary.telemetry.mozilla.org/
N/A
Opt-out telemetry.
We will use this to develop a dashboard across desktop and mobile about experiment and rollout opt-out rates.
Internally via stmo
No
N/A |
e8a95c9 to
37077ed
Compare
travis79
left a comment
travis79
left a comment
There was a problem hiding this comment.
Request for data collection review form
All questions are mandatory. You must receive review from a data steward peer on your responses to these questions before shipping new data collection.
1. What questions will you answer with this data?What are the studies and rollouts opt-out rates for our users in mobile Firefox?
2. Why does Mozilla need to answer these questions? Are there benefits for users? Do we need this information to address product or business requirements?This will give us information into reachability of our clients in terms of incident response rollouts and experimental feature delivery.
3. What alternative methods did you consider to answer these questions? Why were they not sufficient?No other options exist.
4. Can current instrumentation answer these questions?It is technically possible to cobble together a query that selects all enrollment status telemetry from users and filters to any that submit "RolloutsOptOut" or "StudiesOptOut" as the reason, but we don't get a clear picture of when it happens and this telemetry will be cheaper to query.
5. List all proposed measurements and indicate the category of data collection for each measurement, using the [Firefox data collection categories](https://wiki.mozilla.org/Data_Collection) found on the Mozilla wiki.Note that the data steward reviewing your request will characterize your data collection based on the highest (and most sensitive) category.
Measurement Description Data Collection Category Tracking Bug #
Studies opt-out event Category II: Interaction https://bugzilla.mozilla.org/show_bug.cgi?id=2081305
Rollouts opt-out event Category II: Interaction https://bugzilla.mozilla.org/show_bug.cgi?id=20813056. Please provide a link to the documentation for this data collection which describes the ultimate data set in a public, complete, and accurate way.This collection is documented in the Glean Dictionary at https://dictionary.telemetry.mozilla.org/
7. How long will this data be collected? Choose one of the following: * I want to permanently monitor this data. (Beth Rennie) 8. What populations will you measure? * Which release channels? all * Which countries? all * Which locales? all * Any other filters? Please describe in detail below.N/A
9. If this data collection is default on, what is the opt-out mechanism for users?Opt-out telemetry.
10. Please provide a general description of how you will analyze this data.We will use this to develop a dashboard across desktop and mobile about experiment and rollout opt-out rates.
11. Where do you intend to share the results of your analysis?Internally via stmo
12. Is there a third-party tool (i.e. not Glean or Telemetry) that you are proposing to use for this data collection? If so:No
* Are you using that on the Mozilla backend? Or going directly to the third-party?N/A
Data Review Form (to be filled by Data Stewards)
- Is there or will there be documentation that describes the schema for the ultimate data set in a public, complete, and accurate way?
Yes, through the Glean Dictionary
- Is there a control mechanism that allows the user to turn the data collection on and off?
Yes, through the application data preferences
- If the request is for permanent data collection, is there someone who will monitor the data over time?
Yes beth backed by the Nimbus team will monitor this data.
- Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under?
Category 2, User Interaction
- Is the data collection request for default-on or default-off?
default on
- Does the instrumentation include the addition of any new identifiers (whether anonymous or otherwise; e.g., username, random IDs, etc. See the appendix for more details)?
No
- Is the data collection covered by the existing Firefox privacy notice?
Yes
- Does the data collection use a third-party collection tool?
No
Result
data-review+
|
r+ on the patch contents too |
37077ed to
9405851
Compare
We now submit an event when disabling experiment or rollout participation. Additionally, requesting experiment and rollout participation will now no longer throw at the application layer on Android and will instead default to true, which aligns Android with iOS. Enabling experiment or rollout participation while already enabled is now a no-op and will no longer perform a Nimbus update.
9405851 to
45f7deb
Compare
2 participants
Pull Request checklist
[ci full]to the PR title.