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

Telemetry App Entry Point #968

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

Telemetry App Entry Point #968

bbinto opened this issue Mar 12, 2019 · 0 comments

Comments

@bbinto
Copy link
Contributor

bbinto commented Mar 12, 2019

Overview

  • Probe to understand how and from where users are opening Fenix

User Story

  • As a product owner, I want to know how and from where users are coming into Fenix so I can optimize their experience based on the entry point

What questions will you answer with this data?

  • How do users enter the app, e.g. PWA, custom tabs, other intent routes

Why does Mozilla need to answer these questions? Are there benefits for users? Do we need this information to address product or business requirements?

  • It will helps us identify how and when people users browsers, understand their workflows and tasks

What probes

Acceptance Criteria (Added by PM)

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

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