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

[Telemetry] Send an event when users click on the "set as default browser" card in the settings page #18852

Closed
2 of 7 tasks
tdsmith opened this issue Apr 7, 2021 · 1 comment
Assignees
Labels
E3 Estimation Point: average, 2 - 3 days eng:qa:verified QA Verified Feature:Telemetry
Milestone

Comments

@tdsmith
Copy link
Contributor

tdsmith commented Apr 7, 2021

Description & Product Manager / Data Scientist User Story

In order to understand whether we can improve the effectiveness of each messaging surface we’re testing in the set-default experiment (#18796), we should understand how many people interact directly with our message.

As a data scientist, I want to know, using a Glean event, if a user interacted with the "set as default browser" card in the settings page, which we will test in the branch described by #18376.

What questions will you answer with this data?

  • How many people clicked on the message that we presented?
  • When they set to default and the system dialog shows up, how many users actually set us as default?
    • How many people simply close the dialog and do not follow through with setting to default?

Acceptance Criteria

  • ENG files a DS JIRA request outlining their methodology.
  • DS sign off on instrumentation methodology addressing product questions.
  • Event pings can be queried via re:dash
  • Event pings can be queried via amplitude
  • We are sending telemetry events for the actions listed in the requirements
  • We have documented the telemetry
  • We have asked a data steward to review the telemetry

┆Issue is synchronized with this Jira Task

@github-actions github-actions bot added the needs:triage Issue needs triage label Apr 7, 2021
@eliserichards eliserichards removed the needs:triage Issue needs triage label Apr 7, 2021
@amedyne amedyne added this to Ready for Engineering (min-5 ; max-22) in Android Engineering Team Kanban board via automation Apr 8, 2021
@mcarare mcarare self-assigned this Apr 12, 2021
@mcarare mcarare moved this from Ready for Engineering (min-5 ; max-22) to In Development (WIP limit - 15) in Android Engineering Team Kanban board Apr 12, 2021
@mcarare mcarare added the E3 Estimation Point: average, 2 - 3 days label Apr 12, 2021
mcarare added a commit to mcarare/fenix that referenced this issue Apr 15, 2021
@mcarare mcarare moved this from In Development (WIP limit - 15) to Review in progress (WIP limit - 11) in Android Engineering Team Kanban board Apr 15, 2021
mcarare added a commit to mcarare/fenix that referenced this issue Apr 15, 2021
mcarare added a commit to mcarare/fenix that referenced this issue Apr 16, 2021
@Amejia481 Amejia481 added the eng:qa:needed QA Needed label Apr 20, 2021
@mcarare mcarare moved this from Review in progress (WIP limit - 11) to Reviewer approved, ready for test (WIP limit - ?) in Android Engineering Team Kanban board Apr 22, 2021
@lobontiumira
Copy link

Verified as fixed on a debug Nightly build #2015805929, GV 89.0a1-20210418092832 with Google Pixel (Android 10):

  • ping: a546b63f-afea-4a6e-9088-e56404bd0009
  • the event is generated every time the user taps on the "Set as default browser" button from Settings - please see the attached photo
  • Glean dashboard
  • Logcat.txt
{
          "category": "set_default_setting_experiment",
          "name": "set_default_browser_clicked",
          "timestamp": 20399
        }

Android Engineering Team Kanban board automation moved this from Reviewer approved, ready for test (WIP limit - ?) to Done Apr 23, 2021
@lobontiumira lobontiumira added eng:qa:verified QA Verified and removed eng:qa:needed QA Needed labels Apr 23, 2021
@gabrielluong gabrielluong added this to the 89 milestone Apr 23, 2021
mergify bot pushed a commit that referenced this issue May 6, 2021
Amejia481 pushed a commit that referenced this issue May 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
E3 Estimation Point: average, 2 - 3 days eng:qa:verified QA Verified Feature:Telemetry
Projects
No open projects
Development

No branches or pull requests

6 participants