Open
Bug 1434445
Opened 6 years ago
Updated 2 years ago
MMA: User attribute - Total number of devices registered under Fx Account
Categories
(Firefox for iOS :: General, enhancement, P4)
Tracking
()
NEW
Tracking | Status | |
---|---|---|
fxios | + | --- |
People
(Reporter: jcollings, Unassigned)
Details
Attachments
(1 file)
To improve our contextual hints for FxA, we need to get a little bit granular with understanding where are users are in the FxA sign up/in flow. Ask 1: We would like to track total # of devices registered under a user's FxA This would allow us to send specific messages to users with only 1 device in this flow to sync their account with other devices. Ask 2: We would also need to drop an event that indicates that they've actually synced or added another device - so we can measure the success of this campaign.
Updated•6 years ago
|
Updated•6 years ago
|
Assignee: nobody → fpatel
Priority: P2 → P1
Comment 1•6 years ago
|
||
Attachment #8949178 -
Flags: review?(jhugman)
Comment 2•6 years ago
|
||
Comment on attachment 8949178 [details] [review] Pull Request The code looks good to me. This looks like it needs to go for Data Review. https://github.com/mozilla/data-review/blob/master/request.md
Attachment #8949178 -
Flags: review?(jhugman) → review+
Reporter | ||
Comment 3•6 years ago
|
||
Thanks James, let me know if I need to tag Chenxia in this bug. Here are the responses: What questions will you answer with this data? This data will allow us to know which users have not synced their devices and send tailored messages to these users to encourage them to do so. 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 know that users who have a FxAccount and sync across multiple devices retain longer on the browser. And the user will benefit the full Sync services (passwords, bookmarks, Send Tab) only if they sync across multiple devices. What alternative methods did you consider to answer these questions? Why were they not sufficient? The alternative method is to not have this as an user attribute but without it, it would be difficult for us to understand if users are synced or not, therefore the ability to send tailored messages to encourage them to move to the next step in the Sync flow. Can current instrumentation answer these questions? Having this as an user attribute will help answer our question List all proposed measurements and indicate the category of data collection for each measurement, using the Firefox data collection categories on the found on the Mozilla wiki. Measurement Description Data Collection Category Tracking Bug # Track total # of devices registered under a user's FxA This would allow us to send specific messages to users with only 1 device in this flow to sync their account with other devices. I think this is a Category 2. 2) We would also need to drop an event that indicates that they've actually synced or added another device - so we can measure the success of this campaign. Also category 2. I want this data to be collected for 6 months initially (potentially renewable). What populations will you measure? Firefox iOS release / FxA users Which release channels? Current release channel and future release channels Which countries? The countries/locales that Leanplum is currently connected to: en_US, en_GB, en_CA, en_AU, en_HK, en_SG de_DE fr_FR zh_TW it_IT id_ID pt_BR es_ES es_MX pl_PL ru_RU If this data collection is default on, what is the opt-out mechanism for users? Telemetry opt-out Please provide a general description of how you will analyze this data. Take FxA users who have only 1 device and see if they have taken an action from our message to sync to 1 or more devices Where do you intend to share the results of your analysis? Leanplum Quarterly Reviews
Comment 4•6 years ago
|
||
This info is also already in the Sync Ping. For reference https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/telemetry/data/sync-ping.html#syncs-devices
Updated•6 years ago
|
Assignee: fpatel → nobody
Updated•5 years ago
|
Priority: P1 → P4
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•