Firefox/Accounts/Progress Report/2017Q3: Difference between revisions

Jump to navigation Jump to search

Firefox/Accounts/Progress Report/2017Q3 (view source)

Revision as of 19:57, 14 September 2017

300 bytes removed ,  14 September 2017
completed through 2.1
(Updated 1.1 and 1.2)
(completed through 2.1)
Line 67: Line 67:
|
|
*Supports the onboarding team, marketing retention team and Mozilla.org team to improve user retention (through converting first run users to multi-device users).
*Supports the onboarding team, marketing retention team and Mozilla.org team to improve user retention (through converting first run users to multi-device users).
*Ask for email first: Instead of a user needing to know to "Sign In" or "Sign Up", they visit the "Connect to Firefox Accounts" (or similar) page, where they simply enter their email. We determine if an account exists and forward the user to the appropriate sign in or sign up screen.
*[https://sql.telemetry.mozilla.org/dashboard/fxa-q3-okr-1-3 Dashboards related to user retention]
*[https://sql.telemetry.mozilla.org/dashboard/fxa-q3-okr-1-3 Dashboards related to user retention]
*[https://github.com/mozilla/fxa-content-server/pull/5332 Issue 5332: ABC test for CAD phase 3 (deep link)]  
*[https://github.com/mozilla/fxa-content-server/pull/5332 Issue 5332: ABC test for CAD phase 3 (deep link)]  
*[https://github.com/mozilla/fxa-content-server/issues/5194 Issue 5194: Sign-up/in flow: Ask for email first]
|
|
*Now that we’re using strict multi-device, numbers are going down, leading us to have less confidence.
*Still not seeing any difference in outcomes between the different phases in our ABC test. Landed our iOS deeplink patch on Sept 7th so signinCodes consumption should have increased since that date. Form views on iOS should also have increased since that date thanks to deeplinks. Leif will compare form views per phase.
*Uptick in engage but no change in ?
*The bottom charts of our dashboard are not measuring phase 2 and 3 the same way. They show very different results because phase 3 uses the flow_id. There may be a bug with the flow_id so Leif will copy the phase 2 chart for phase 3. Will see what difference that makes.
*Graph not moving in the right direction
*Try to show CAD screen more often
|-
|-
|align="left"| 1.4 Fix newsletter subscription when email is confirmed on a 2nd device.
|align="left"| 1.4 Fix newsletter subscription when email is confirmed on a 2nd device.
Line 88: Line 84:
Fixes a problem with getting marketing newsletter opt-in data over to Salesforce.
Fixes a problem with getting marketing newsletter opt-in data over to Salesforce.
|
|
*Didn’t seem to be any big change in their metrics. Marketing is expected to look at them again.
*Not sure if the fix is working. Maybe the situation it fixed was small numbers and just not noticeable. We should be able to go through the flow ourselves and have Ben verify.  
*Number didn’t drop to 0 so we didn’t break it.
*Trending down even before our work landed. So not sure if the fix is working. Maybe the situation it fixed was small numbers and just not noticeable. We should be able to go through the flow ourselves and have Ben verify.  
|-
|-
|rowspan=2| 2. To have improved the quality of the Firefox Account experience on mobile.
|rowspan=2| 2. To have improved the quality of the Firefox Account experience on mobile.
Line 107: Line 101:
*[https://mozilla.invisionapp.com/share/76CPM7AC2#/screens/240561291_Desktop-_Connect_Another_Device Proposed mock up]
*[https://mozilla.invisionapp.com/share/76CPM7AC2#/screens/240561291_Desktop-_Connect_Another_Device Proposed mock up]
|
|
*No change. Waiting for a bunch of stuff to land. But happy with code and getting it through the review process with the iOS team.
*Next step is to design test to measure results.
|-
|-
| align="left"|2.2 Complete 80% of Q3 mobile bugs.
| align="left"|2.2 Complete 80% of Q3 mobile bugs.
Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1180483"

Navigation menu