Skip to content
This repository has been archived by the owner on Jul 22, 2024. It is now read-only.

FxA telemetry #1610

Closed
11 of 12 tasks
jvonitter opened this issue Aug 20, 2019 · 8 comments · Fixed by #2327
Closed
11 of 12 tasks

FxA telemetry #1610

jvonitter opened this issue Aug 20, 2019 · 8 comments · Fixed by #2327
Assignees
Milestone

Comments

@jvonitter
Copy link
Contributor

jvonitter commented Aug 20, 2019

  • number of users who click the "sign in" button
  • number of users who successfully log-in to an account
  • number of users who sign out
  • sign outs not caused by user manually signing out?
  • number of users who turn syncing off (for each bookmarks and history)
  • number of users who send a tab from FxR (across all users, all sessions)
  • number of users who receive a tab from another device (across all users, all sessions)
  • of users who have sent a tab ever, average number of tabs sent per week
  • of users who have received a tab ever, average number of tabs received per week
  • if possible - tab source: mobile/desktop percentage

  • Do data review
  • Implement telemetry
@jvonitter jvonitter self-assigned this Aug 20, 2019
@jvonitter jvonitter added this to the v1.5 milestone Aug 20, 2019
@jvonitter jvonitter modified the milestones: #5 polish, #6 features Oct 2, 2019
@jvonitter jvonitter assigned keianhzo and unassigned jvonitter Oct 14, 2019
@bluemarvin bluemarvin modified the milestones: #6 features, #7 polish Oct 29, 2019
@larsbergstrom
Copy link

It would be really excellent to fit this in for the FxA / Send to Device launch, if possible. lmk if I can help expedite data or legal reviews (ET has recently grown the data stewardship team, too). cc @jvonitter

@jvonitter
Copy link
Contributor Author

cc @daoshengmu

@daoshengmu
Copy link
Contributor

All of them can implement by Glean. There is no blocker issue for them because their lifetime looks like can be daily and no time measurement.

@daoshengmu
Copy link
Contributor

One thing might be concerned is our FxR 6 release is blocked that makes a little risky for Glean because we haven't had a chance to check the Glean baseline metric with real users. Ideally, we need to make sure baseline data are match with our current DAU data first, then adding more telemetry on it.

@daoshengmu
Copy link
Contributor

In terms of bookmark/history, we can reuse the telemetry from
https://github.com/mozilla-mobile/android-components/blob/master/components/support/sync-telemetry/metrics.yaml.

Please take a look at org_mozilla_vrbrowser.bookmarks_sync, org_mozilla_vrbrowser.history_sync schema from our data source before we start.

This was referenced Nov 20, 2019
@davismtl
Copy link

@irrationalagent do they need to track send tab on their end or do we have this convered?

@larsbergstrom
Copy link

If it's already covered on your end (via the component), then presumably there would already be data if we look at the metrics and filter for the Firefox Reality product, due to all of our internal testing?

@irrationalagent
Copy link

I am not seeing anything that looks like telemetry in the send tab android component, so I'm guessing it will not be automatically sending any telemetry out of the box

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
8 participants