All questions are mandatory. You must receive review from a data steward peer on your responses to these questions before shipping new data collection.
-
What questions will you answer with this data?
-
Why does Mozilla need to answer these questions? Are there benefits for users? Do we need this information to address product or business requirements? Some example responses:
-
Establish baselines or measure changes in product or platform quality or performance.
-
Provide information essential for advancing a business objective such as supporting OKRs.
-
Determine whether a product or platform change has an effect on user or browser behavior.
-
What alternative methods did you consider to answer these questions? Why were they not sufficient?
-
Can current instrumentation answer these questions?
-
List all proposed measurements and indicate the category of data collection for each measurement, using the Firefox data collection categories 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 # |
- How long will this data be collected? Choose one of the following:
-
This is scoped to a time-limited experiment/project until date MM-DD-YYYY.
-
I want this data to be collected for 6 months initially (potentially renewable).
-
I want to permanently monitor this data. (put someone’s name here)
- What populations will you measure?
-
Which release channels?
-
Which countries?
-
Which locales?
-
Any other filters? Please describe in detail below.
-
If this data collection is default on, what is the opt-out mechanism for users?
-
Please provide a general description of how you will analyze this data.
-
Where do you intend to share the results of your analysis?
-
Is there a third-party tool (i.e. not Telemetry) that you are proposing to use for this data collection? If so:
- Are you using that on the Mozilla backend? Or going directly to the third-party?