-
Notifications
You must be signed in to change notification settings - Fork 218
Telemetry
This will allow us to understand which features are being used and how are they used. Based on the data, we will have a better scope of shipping the right features to users and obtain actionable insights for the product. We will understand if any changes to the product (e.g. GeckoView, other features) will increase/decrease the Monthly Active Users and Daily Active Users.
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?
- 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.
3. What alternative methods did you consider to answer these questions? Why were they not sufficient?
We have access to the number of sessions, but we need to understand engagement on a more micro level.
No.
5. List all proposed measurements and indicate the category of data collection for each measurement, using the Firefox data collection categories on the Mozilla Wiki.
Measurement Description | Data Collection Category | Tracking Bug # |
---|---|---|
DAU/WAU/MAU (Engagement Results) | Category 2 Interaction data | #85 |
Session length distribution | Category 2 Interaction data | #85 |
Engagement ratio | Category 2 Interaction data | #85 |
Number of users | Category 2 Interaction data | #85 |
New user retention | Category 2 Interaction data | #85 |
DAUs by locale | Category 2 Interaction data | #85 |
Distribution of Devices Over Time | Category 1 Technical data | #85 |
Action Counts | Category 2 Interaction data | #85 #395 |
Search Engine Counts | Category 2 Interaction data | #395 |
Search Counts | Category 2 Interaction data | #395 |
Event | Category | Method | Object | Value |
---|---|---|---|---|
Start session (App is in the foreground) | Action | Foreground | App | N/A |
Stop session (App is in the background) | Action | Background | App | N/A |
Event | Category | Method | Object | Value |
---|---|---|---|---|
URL entered | Action | type_url | search_bar | N/A |
Search entered | Action | type_query | search_bar | bundled engine name |
Voice query | Action | voice_query | voice_input | bundled engine name |
I want to permanently monitor this data. (@larsberg)
All users opting in to telemetry
These VR app stores: Oculus, Google Play, and Viveport.
Worldwide
Worldwide
Users can go into the Developer Settings panel to toggle off.
Look at the features used over time to see if it increases with improvements to the app.
Internal use only.