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 view the new tab screen #18854

Closed
7 tasks
tdsmith opened this issue Apr 7, 2021 · 2 comments
Closed
7 tasks

[Telemetry] Send an event when users view the new tab screen #18854

tdsmith opened this issue Apr 7, 2021 · 2 comments
Assignees
Labels
E2 Estimation Point: easy, half a day to 2 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 see our messages at all. This relates to the branch described in #18375.

As a data scientist, I want to know how often users view the new-tab UI. I would like to observe a Glean event each time users view the new-tab UI.

There is a new tab tapped event. If there's no other way that users experience new tab, this new telemetry isn't a high priority.

What questions will you answer with this data?

How many users will see, saw, or could have seen the message we will place on new tab?

Acceptance Criteria

  • ENG files a DS JIRA request outlining their methodology. Let's discuss in this ticket if you have any questions.
  • 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
@amedyne amedyne added this to Ready for Engineering (min-5 ; max-22) in Android Engineering Team Kanban board via automation Apr 8, 2021
@amedyne amedyne removed the needs:triage Issue needs triage label Apr 8, 2021
@Amejia481 Amejia481 added the E2 Estimation Point: easy, half a day to 2 days label Apr 13, 2021
@mcarare mcarare self-assigned this Apr 14, 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 14, 2021
@mcarare mcarare moved this from In Development (WIP limit - 15) to Dev Complete (WIP limit - 5) in Android Engineering Team Kanban board Apr 14, 2021
@mcarare mcarare moved this from Dev Complete (WIP limit - 5) to Review in progress (WIP limit - 11) in Android Engineering Team Kanban board Apr 14, 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 15, 2021
@lobontiumira
Copy link

Verified as fixed on the 4/19 Nightly build with Google Pixel (Android 10).
Ping: de13230d-0cbb-4393-b51d-8fa11679e435

{
          "category": "home_screen",
          "name": "home_screen_displayed",
          "timestamp": 3333
        }

Glean dashboard
logcat.txt

Android Engineering Team Kanban board automation moved this from Reviewer approved, ready for test (WIP limit - ?) to Done Apr 19, 2021
@lobontiumira lobontiumira added the eng:qa:verified QA Verified label Apr 19, 2021
@gabrielluong gabrielluong added this to the 89 milestone Apr 19, 2021
@eliserichards
Copy link
Contributor

PR: #19025

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
E2 Estimation Point: easy, half a day to 2 days eng:qa:verified QA Verified Feature:Telemetry
Projects
No open projects
Development

No branches or pull requests

7 participants