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

Telemetry 3dot menu #1024

Closed
bbinto opened this issue Mar 14, 2019 · 0 comments
Closed

Telemetry 3dot menu #1024

bbinto opened this issue Mar 14, 2019 · 0 comments

Comments

@bbinto
Copy link
Contributor

bbinto commented Mar 14, 2019

Learn about interaction of menu

Description & Product Manager / Data Scienties User Story

  • As a product owner, I want to know how users leverage the menu and for what so we can make sure we provide the best and quickest way for users to perform their task they expect the menu to entail

What questions will you answer with this data?

  • What are the most common uses cases for users to open the menu?
  • How often is "Request Desktop Site"?
  • All events in the menu should be tracked, e.g. click on

[ ] Settings
[ ] Your library
[ ] Help
[ ] Desktop Site toggle on/off
[ ] Find in Page
[ ] New Tab
[ ] Private Tab
[ ] Share
[ ] Report Site Issue
[ ] Back/Forward button
[ ] Reload Button

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 understand how users are navigating through the browser, including also these events into Amplitude let's us create funnels and improve user flow

Dependencies (Added by PM and Eng)

  • Glean SDK

Acceptance Criteria (Added by PM)

  • Event pings can be queried via re:dash AND 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

@bbinto bbinto added this to the Milestone 3 Backlog milestone Mar 14, 2019
@bbinto bbinto added Epic and removed needs:product labels Mar 14, 2019
@boek boek self-assigned this Mar 25, 2019
boek added a commit to boek/fenix that referenced this issue Mar 27, 2019
boek added a commit to boek/fenix that referenced this issue Mar 27, 2019
boek added a commit to boek/fenix that referenced this issue Mar 27, 2019
boek added a commit to boek/fenix that referenced this issue Mar 27, 2019
@bifleming bifleming added this to Blocked in Fenix Sprint Kanban Mar 27, 2019
@bifleming bifleming moved this from Blocked to Ready for Dev in Fenix Sprint Kanban Mar 27, 2019
@boek boek moved this from Ready for Dev to In Progress in Fenix Sprint Kanban Mar 27, 2019
@boek boek moved this from In Progress to In Review in Fenix Sprint Kanban Mar 27, 2019
@vesta0 vesta0 added P1 Current sprint and removed P1 Current sprint labels Apr 1, 2019
boek added a commit to boek/fenix that referenced this issue Apr 1, 2019
boek added a commit to boek/fenix that referenced this issue Apr 3, 2019
boek added a commit to boek/fenix that referenced this issue Apr 3, 2019
@boek boek closed this as completed in 4b4d172 Apr 3, 2019
@ghost ghost removed the P1 Current sprint label Apr 3, 2019
@data-sync-user data-sync-user changed the title Telemetry 3dot menu FNX2-15819 ⁃ Telemetry 3dot menu Jul 30, 2020
@data-sync-user data-sync-user changed the title FNX2-15819 ⁃ Telemetry 3dot menu FNX-4731 ⁃ Telemetry 3dot menu Aug 10, 2020
@data-sync-user data-sync-user changed the title FNX-4731 ⁃ Telemetry 3dot menu FNX3-13754 ⁃ Telemetry 3dot menu Aug 10, 2020
@data-sync-user data-sync-user changed the title FNX3-13754 ⁃ Telemetry 3dot menu FNX-4731 ⁃ Telemetry 3dot menu Aug 11, 2020
@data-sync-user data-sync-user changed the title FNX-4731 ⁃ Telemetry 3dot menu FNX2-15819 ⁃ Telemetry 3dot menu Aug 11, 2020
@data-sync-user data-sync-user changed the title FNX2-15819 ⁃ Telemetry 3dot menu Telemetry 3dot menu May 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants