-
Notifications
You must be signed in to change notification settings - Fork 208
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Epic] Boomerang #1758
Comments
|
|
Here is a dashboard to track performance with registrations: Why did the experiment only start on Friday the 13th? |
There was a fix for amplitude metrics that went out that day 👻 |
Numbers are still showing a 22% increase in registrations. There is a slight decrease in retention. @vbudhram is looking to turn this up to 100% as of next week since this seems like a win. We will continue to keep an eye on retention/ |
WOOOOW! Fantastic work @vbudhram, @ryanfeeley, and everyone else who pushed on this! |
Tagged for train 146. Should go out today. Going to 50% for sign-ins. |
For the registration experiment, we need to log results here: |
Since the release, we seem to be losing a lot of multi-device users. What could we do to recover this lost knowing that we prefer this flow for many reasons? https://analytics.amplitude.com/mozilla-corp/dashboard/q2nfqqt |
Not rolled out at 100% ??? |
#2847 has been fixed and is in train-148 |
This bug with analysis might be showing that the mobile drop has nothing to do with codes since it also impacted CAD on logins which had no codes in train 146. |
|
We should have an analysis to discuss next week. |
Logged results for registration and conversion to mobile in the feature doc. Will add results for login after I review Kimmy's analysis. |
Moved card to remove A/B logic. |
All issues for the Skyline boomerang work would be opened under this epic for tracking purposes.
PRD:
https://docs.google.com/document/d/1fqyXTcAfJ8HPaCsEtML_bfIItlYYtG5yk32ZRaOXorY/edit#
┆Issue is synchronized with this Jira Epic
┆Issue Number: FXA-196
The text was updated successfully, but these errors were encountered: