Telemetry 3dot menu

[bbinto]

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