Skip to content
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.

For #26551 - Add telemetry for MR Onboarding welcome and sync dialogs. #26596

Merged
merged 2 commits into from
Aug 30, 2022

Conversation

Alexandru2909
Copy link
Contributor

@Alexandru2909 Alexandru2909 commented Aug 23, 2022

Added telemetry for MR onboarding welcome and sync dialogs.

Pull Request checklist

  • Tests: This PR includes thorough tests or an explanation of why it does not
  • Screenshots: This PR includes screenshots or GIFs of the changes made or an explanation of why it does not
  • Accessibility: The code in this PR follows accessibility best practices or does not include any user facing features. In addition, it includes a screenshot of a successful accessibility scan to ensure no new defects are added to the product.

QA

  • QA Needed

To download an APK when reviewing a PR (after all CI tasks finished running):

  1. Click on Checks at the top of the PR page.
  2. Click on the firefoxci-taskcluster group on the left to expand all tasks.
  3. Click on the build-debug task.
  4. Click on View task in Taskcluster in the new DETAILS section.
  5. The APK links should be on the right side of the screen, named for each CPU architecture.

GitHub Automation

Fixes #26551

@Alexandru2909
Copy link
Contributor Author

Alexandru2909 commented Aug 23, 2022

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?
  • How many users saw the MR welcome onboarding card?
  • How many users dismissed the MR welcome onboarding card?
  • How many users interacted with the `Get started` button from the welcome onboarding card?
  • How many users saw the MR sync onboarding card?
  • How many users dismissed the MR sync onboarding card?
  • How many users interacted with the `Sign in` button from the MR sync onboarding card?
  • How many users interacted with the `Skip` button from the MR sync onboarding card?
  1. Why does Mozilla need to answer these questions? Are there benefits for users? Do we need this information to address product or business requirements?
  • We need to count the MR onboarding impressions and interactions with the MR onboarding screens to understand how many users are reminded of the value Firefox is providing and how they decide to interact with the onboarding dialogs.
  1. What alternative methods did you consider to answer these questions? Why were they not sufficient?
  • No other alternatives.

  1. Can current instrumentation answer these questions?
  • No.

  1. List all proposed measurements and indicate the category of data collection for each measurement, using the Firefox data collection categories 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 #
Welcome card impression: The welcome onboarding card was displayed to the user. Category 2 - interaction data #26551
Welcome close clicked: The user clicked the X button from the welcome onboarding card. Category 2 - interaction data #26551
Welcome get started clicked: The user clicked the Get started button from the welcome onboarding card. Category 2 - interaction data #26551
Sync card impression: The sync sign in onboarding card was displayed to the user. Category 2 - interaction data #26551
Sync close clicked: The user clicked the X button from the sync sign in onboarding card. Category 2 - interaction data #26551
Sync sign in clicked: The user clicked the Sign in button from the sync sign in onboarding card. Category 2 - interaction data #26551
Sync skip clicked: The user clicked on the Skip button from the sign in onboarding card. Category 2 - interaction data #26551
  1. Please provide a link to the documentation for this data collection which describes the ultimate data set in a public, complete, and accurate way.
  1. How long will this data be collected? Choose one of the following:
  • Up until version 119, with the option to renew at that point.
  1. What populations will you measure?
  • All channels, all locales, all countries.

  1. If this data collection is default on, what is the opt-out mechanism for users?
  • Default Glean SDK opt-out mechanism.

  1. Please provide a general description of how you will analyze this data.
  • Glean.

  1. Where do you intend to share the results of your analysis?
  • 
Only on Glean and with mobile teams.

  1. Is there a third-party tool (i.e. not Telemetry) that you are proposing to use for this data collection?
  • No third-party tools.

@gabrielluong gabrielluong added the pr:work-in-progress PRs that are not ready to be reviewed yet and are actively being worked on label Aug 23, 2022
@gabrielluong gabrielluong self-requested a review August 23, 2022 17:00
@gabrielluong gabrielluong self-assigned this Aug 23, 2022
@mergify
Copy link
Contributor

mergify bot commented Aug 25, 2022

This pull request has conflicts when rebasing. Could you fix it @Alexandru2909? 🙏

@Alexandru2909 Alexandru2909 added needs:data-review PR is awaiting a data review and removed pr:work-in-progress PRs that are not ready to be reviewed yet and are actively being worked on labels Aug 26, 2022
@Alexandru2909 Alexandru2909 marked this pull request as ready for review August 26, 2022 06:27
@Alexandru2909 Alexandru2909 requested review from a team as code owners August 26, 2022 06:27
@gabrielluong gabrielluong added the needs:review PRs that need to be reviewed label Aug 29, 2022
IconButton(
onClick = {
if (onboardingState == OnboardingState.Welcome) {
OnboardingMetrics.welcomeCloseClicked.record(NoExtras())
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm shocked that the Glean metrics don't break the Compose previews lol. I feel the metrics could live within HomeOnboardingDialogFragment though. @gabrielluong, do you have a strong opinion on this?

Copy link
Member

@gabrielluong gabrielluong Aug 29, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is fine for now. I would want to look at refactoring some of this and make use of an Interactor so that we can test this, but that can be a followup after this lands.

Copy link
Member

@gabrielluong gabrielluong left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code looks good to me, but we'll need a data review

@gabrielluong gabrielluong added pr:approved PR that has been approved and removed needs:review PRs that need to be reviewed labels Aug 29, 2022
@gabrielluong gabrielluong requested a review from travis79 August 29, 2022 20:36
@travis79
Copy link
Member

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?


* How many users saw the MR welcome onboarding card?

* How many users dismissed the MR welcome onboarding card?

* How many users interacted with the `Get started` button from the welcome onboarding card?

* How many users saw the MR sync onboarding card?

* How many users dismissed the MR sync onboarding card?

* How many users interacted with the `Sign in` button from the MR sync onboarding card?

* How many users interacted with the `Skip` button from the MR sync onboarding card?


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?


* We need to count the MR onboarding impressions and interactions with the MR onboarding screens to understand how many users are reminded of the value Firefox is providing and how they decide to interact with the onboarding dialogs.


3. What alternative methods did you consider to answer these questions? Why were they not sufficient?


* No other alternatives.


4. Can current instrumentation answer these questions?


* No.


5. List all proposed measurements and indicate the category of data 
   collection for each measurement, using the Firefox data collection 
   categories 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 #
Welcome card impression: The welcome onboarding card was displayed to the user. Category 2 - interaction data #26551
Welcome close clicked: The user clicked the X button from the welcome onboarding card. Category 2 - interaction data #26551
Welcome get started clicked: The user clicked the Get started button from the welcome onboarding card. Category 2 - interaction data #26551
Sync card impression: The sync sign in onboarding card was displayed to the user. Category 2 - interaction data #26551
Sync close clicked: The user clicked the X button from the sync sign in onboarding card. Category 2 - interaction data #26551
Sync sign in clicked: The user clicked the Sign in button from the sync sign in onboarding card. Category 2 - interaction data #26551
Sync skip clicked: The user clicked on the Skip button from the sign in onboarding card. Category 2 - interaction data #26551

6. Please provide a link to the documentation for this data collection 
   which describes the ultimate data set in a public, complete, and 
   accurate way.


* [dictionary.telemetry.mozilla.org/apps/fenix](https://dictionary.telemetry.mozilla.org/apps/fenix)


7. How long will this data be collected? Choose one of the following:


* Up until version 119, with the option to renew at that point.


8. What populations will you measure?


* All channels, all locales, all countries.


9. If this data collection is default on, what is the opt-out mechanism for users?


* Default Glean SDK opt-out mechanism.


10. Please provide a general description of how you will analyze this data.


* Glean.


11. Where do you intend to share the results of your analysis?


* Only on Glean and with mobile teams.


12. Is there a third-party tool (i.e. not Telemetry) that you are proposing to use for this data collection?


* No third-party tools.

Data Review

  1. 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 metrics.yaml file and the Glean Dictionary.

  1. Is there a control mechanism that allows the user to turn the data collection on and off?

Yes, through the "Send Usage Data" preference in the application settings.

  1. If the request is for permanent data collection, is there someone who will monitor the data over time?

N/A, collection to end by version 119

  1. Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under?

Category 2, Interaction data

  1. Is the data collection request for default-on or default-off?

Default-on

  1. 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

  1. Is the data collection covered by the existing Firefox privacy notice?

Yes

  1. Does the data collection use a third-party collection tool?

No

Result

data-review+

Copy link
Member

@travis79 travis79 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

data-review+

@travis79 travis79 removed the needs:data-review PR is awaiting a data review label Aug 29, 2022
@Alexandru2909 Alexandru2909 added the pr:needs-landing PRs that are ready to land [Will be merged by Mergify] label Aug 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
pr:approved PR that has been approved pr:needs-landing PRs that are ready to land [Will be merged by Mergify]
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add Telemetry for MR Home Onboarding Dialog for upgrading users
4 participants