Reference the original work in #6629
| Estimates | |
| ------------- | ------------- |
| TL | 1 hour |
| PM | 1/2 day |
| ENG | 1 day |
| SEO | |
| ANA | ? |
| DES | |
| COPY | |
Description: Notch up the global CTA to a 90% experiment and localize it in DE/FR. (Original description: Implement a test showing a Fx Account CTA in the Global Navigation to users visiting mozilla.org w. a Firefox browser instead of the current 'Download Firefox' CTA.)
I believe the ask here is to expand this experiment to 2 further locales (de and fr), as opposed to open this up for l10n? Generally we will open things up only once an experiment proves successful.
Also, I seem to remember an ask in Slack of opening this up to FF > 57 visitors which isn't yet detailed here. Is that still a requirement? (and also why 57, considering those users are pretty out of date?)
I think the reasoning may (may) be that users with older versions may (may) not be able to update further, but can sign up for an account regardless of their version and our overarching goal is to promote Accounts. @hoosteeno - is that accurate - we're looking promote accounts to all Fx users?
I believe the ask here is to expand this experiment to 2 further locales (de and fr), as opposed to open this up for l10n? Generally we will open things up only once an experiment proves successful.
I clarified above. I asked the FxA team to provide localized strings.
Also, I seem to remember an ask in Slack of opening this up to FF > 57 visitors which isn't yet detailed here. Is that still a requirement? (and also why 57, considering those users are pretty out of date?)
Getting people on Quantum puts them on solid footing for a whole host of things we care about that relate to user satisfaction and a deepening relationship -- accounts features like send tabs, UI improvements, better performance, pocket integration, and of course any security fixes in the interval. But going forward from Quantum, we should not assume that the website is the best place to convince people to update Firefox. In fact, product features should do this work. We can do more impactful things with the high-value web real estate we've previously allocated to promoting upgrades.
Thanks for the context re: 57. I think for an experiment this is fine, and I totally agree that trying hard to get people to update is a difficult task in context of the website and the UX problems it presents.
Should this become a long term feature, perhaps we could consider not using a hard coded version number though. Instead we could perhaps say, if the user is <= x major versions out of date, show FxA, else: show the download button.
Blocking this issue on strings.
Are the l10n strings preventing us from exposing this to 90% of the audience in EN?
Are the l10n strings preventing us from exposing this to 90% of the audience in EN?
Good suggestion 馃憤 If we're blocked on copy, let's split this out into two pieces of work.
@amychurchwell - ready for your code review, please.
Can someone please send me the strings for this page so that we can localize it? Thanks!
Hi! The strings have been added here: https://docs.google.com/document/d/1qeGA50axmClm03KEC7opuF0DOgExyCj03rFd0l57rco/edit
@ejregithub @LaurenNiolet
@alexgibson - here's are the localized strings:
EN | DE | FR
-- | -- | --
Get a Firefox Account | Firefox-Konto erstellen | Cr茅ez un compte Firefox
Check out the Benefits | Das sind deine Vorteile | D茅couvrez les avantages
I've opened a PR to expand this experiment for de and fr above.
Questions for @hoosteeno and/or @sghoseWI:
en-US?90% is good in de/fr.
Amplitude can segment by lang and locale so we shouldn't need to send that info.
Ok, this is now ready to go
Experimental cohort sample results look good so far! https://analytics.amplitude.com/mozilla-corp/chart/rghy2p9/edit/3wa0gki
Most helpful comment
90% is good in de/fr.
Amplitude can segment by lang and locale so we shouldn't need to send that info.