1438633 - [Retention] FxAccount CTA in /whatsnew 59

Status: RESOLVED FIXED

(www.mozilla.org :: Pages & Content, enhancement)

Comment 1

[Eric Renaud [:erenaud]]

Requirements:

Firefox 59.0

- The page will use the same content as in the current /firstrun with the single field email CTA for Firefox Accounts.

- The page should be made available to all locales with same localized content in /firstrun

Firefox 59.0.x (the 'dot' releases)

- TBD based an immediate security update, the content in the /whatsnew page will revert to the usual mobile download CTA for the first dot release, shown until decisions are made for the Fx 60 release.

Comment 2

[Eric Renaud [:erenaud]]

Alex noted (I agree) the strange experience on /firstrun for users that are logged into their Firefox account.

Per discussion in Slack, the current idea is to avoid this by providing the current mobile CTA version content used in /whatsnew as it already exists in prod and is already localized.

One question arises from this, with regard to 'smushing' the current .lang files for /firstrun and /whatsnew into a single one for the single template that will be created.  Flod & Peiying can you please comment about the feasibility of doing so?

Comment 3

[Francesco Lodolo [:flod]]

(In reply to Eric Renaud from comment #2)
> One question arises from this, with regard to 'smushing' the current .lang
> files for /firstrun and /whatsnew into a single one for the single template
> that will be created.  Flod & Peiying can you please comment about the
> feasibility of doing so?

It's almost impossible to give you a precise answer without seeing the actual templates.

Right now:
* /firstrun uses content from the firefox/new .lang file
* the generic /whatsnew uses its own .lang file, plus a second .lang file for the Send To widget

It's possible to load a different .lang file in a template, but it needs to be done carefully, since importing a .lang file also imports the activation status.

It's also possible to copy strings from one or more .lang files into a new one, that works around the activation issue. 

One concern is about timing of these changes: releng wants the list of locales cut really earlier than release, so we add risk (more locales not showing the whatsnew page because incomplete).

Comment 4

[Eric Renaud [:erenaud]]

The copying of strings appears to be the best option as we have no intent of modifying strings, using only those that have already been localized.

I'm wondering what the possibilities are here with regard to locales showing which content.  Right now we have a large set that are shown the /whatsnew page with the mobile CTA content. 

Alex - given the scheme here is to show 'all' locales (all those that have localize /firstrun) the FxAccount CTA on 59.0, then show them the same mobile CTA content in the dot releases they're seeing now, could we set the mobile CTA content as default for any locales that do not update in time to be shown the Fx Account CTA?

Comment 5

[Alex Gibson [:agibson]]

(In reply to Eric Renaud from comment #4)
> Alex - given the scheme here is to show 'all' locales (all those that have
> localize /firstrun) the FxAccount CTA on 59.0, then show them the same
> mobile CTA content in the dot releases they're seeing now, could we set the
> mobile CTA content as default for any locales that do not update in time to
> be shown the Fx Account CTA?

I was under the impression that all locales had /firstrun translated? Maybe Flod can verify here. If they don't, then this request is getting really complicated :/

To help give a little background as to this request:

1.) We need to show a new /whatsnew page for people updating from < 59.0.
2.) This new page would show the Firefox Accounts form as seen on /firstrun, for users who are not already signed into Sync.
3.) For users who are already signed in, we need to show them an alternative CTA (this is where the request gets messy).
4.) The ideal secondary CTA for signed-in users would be the send-to-device form (falling back to QR code), as seen on the standard /whatsnew page. In order to do this, we would need to load both the firstrun.lang and whatsnew.lang file in a single template. We understand this may or may not be feasible, depending on what locales have each lang file activated.
5.) If 4. is not feasible, we need to rethink and come up with some other, more simplified alternative CTA for signed-in users.

Comment 6

[Francesco Lodolo [:flod]]

(In reply to Alex Gibson [:agibson] from comment #5)
> I was under the impression that all locales had /firstrun translated?

Not really
https://l10n.mozilla-community.org/langchecker/?locale=all&website=0&file=firefox/new/quantum.lang

Also, we need to give releng the list of locales, with tags involved it's hard to tell what each locale will see.

Comment 7

[Alex Gibson [:agibson]]

Eric, it sounds like this request is going to get too clumbersome to deal with accurately. I'd suggest we rethink on the scope of this request and simplify an alternative CTa for users who are already signed in.

Comment 8

[Alex Gibson [:agibson]]

Here's a possible solution that reuses strings in firstrun.lang, but it depends if enough locales have the tag translated:

Alternative CTA for signed in users:

Headline: "Take Firefox with You"
Subhead: "Get your bookmarks, history, passwords and other settings on all your devices."
CTA: "Sync up with Firefox on mobile:" -> QR code / app store badges.

Flod can confirm here, but looking at coverage of the existing strings - this might be achievable?

https://l10n.mozilla-community.org/langchecker/?website=www.mozilla.org&file=firefox/new/quantum.lang&action=translate

Comment 9

[Francesco Lodolo [:flod]]

We have about 40 translations for the first two strings., but at this point it becomes more a question for Peiying (I see there's still a NI open).

Comment 10

[Alex Gibson [:agibson]]

(In reply to Francesco Lodolo [:flod] (offsite until Feb 25, slow replies) from comment #9)
> We have about 40 translations for the first two strings.

Even if 40 isn't enough, perhaps we can find an alternative here in the same lang file.

Comment 11

[Alex Gibson [:agibson]]

A WIP version of what I propose we do is now up on demo:

https://www-demo3.allizom.org/en-US/firefox/59.0/whatsnew/

Now that I've had the time to think through what we're doing here, I'm of the opinon that we should only really show this /whatsnew page to the ~40 locales who have these latest strings translated. The fallback strings (e.g. "Already using Firefox?" for the main title) don't really make sense in context of a /whatsnew page. Doing this also greatly simplifies all the fallback conditional strings, which would be messy.

To test the page functionality, you'll need to set up a test profile [1] and also enable uitour for the demo server [2].

Eric, can you please confirm if these ~40 locales are enough and we can move forward with this plan?

[1] http://bedrock.readthedocs.io/en/latest/firefox-accounts.html#demo-server-testing
[2] http://bedrock.readthedocs.io/en/latest/uitour.html

Comment 12

[GitHub Bugzilla PR Linker]

Attachment: Link to GitHub pull-request: https://github.com/mozilla/bedrock/pull/5472

Comment 13

[Eric Renaud [:erenaud]]

Alex - 

If this data is as it appears, I share your opinion.
"Complete locales: 41 (37%) - 95.07% of our l10n user base"
(Plus I see no other viable recourse achievable in time for the required date).

Could you please take screenshots of each state and attach them here?

Comment 14

[Eric Renaud [:erenaud]]

Flod or Peiying - would you please verify this as the list of locales we should pass over to releng, identified from this page (plus I've included en-US)

https://l10n.mozilla-community.org/langchecker/?locale=all&website=0&file=firefox/new/quantum.lang

an, bg, bs, cak, cs, cy, da, de, dsb, eo, en-US, es-AR, es-CL, es-ES, es-MX, fi, fr, fy-NL, gu-IN, hsb, hu, hy-AM, it, ja, ka, ms, nb-NO, nl, nn-NO, pl, pt-BR, pt-PT, ru, sk, sl, sq, sv-SE, tr, uk, zh-CN, zh-TW

Comment 15

[Peiying Mo [:CocoMo]]

Complete locales: 41 (37%) - 95.07% of our l10n user base
Activated locales: 60 (54%) - 101.41% of our l10n user base 

The 2nd line tells us 60 locales were activated at one point, but have not caught up with the latest (tagged) changes. I don't know if this helps with the decision making.

Comment 16

[Peiying Mo [:CocoMo]]

add to the list: et, fa
remove from the list: gu-IN

Comment 17

[Francesco Lodolo [:flod]]

As explained in the pull request, the current approach isn't really going to work.

While releng will use a list to enable the whatsnew page, the current PR reuses firefox/new/quantum.lang, so there are scenarios where the file is activated, but lacks the strings you want to use.

It's also using a string that is not available in that file ("Your Firefox is up to date."). 

What we need is to build a separate lang file with those string, and then figure out which locales can be enabled.

Comment 18

[Francesco Lodolo [:flod]]

(In reply to Francesco Lodolo [:flod] from comment #17)
> What we need is to build a separate lang file with those string, and then
> figure out which locales can be enabled.

At the moment, this list would be:

Complete locales (43):
an, bg, bs, cak, cs, cy, da, de, dsb, eo, es-AR, es-CL, es-ES, es-MX, et, fa, fi, fr, fy-NL, gu-IN, hsb, hu, hy-AM, it, ja, ja-JP-mac, ka, ms, nb-NO, nl, nn-NO, pl, pt-BR, pt-PT, ru, sk, sl, sq, sv-SE, tr, uk, zh-CN, zh-TW

I'll need to know when the deadline to provide the list is.

Comment 19

[Alex Gibson [:agibson]]

(In reply to Eric Renaud from comment #13)
> Alex - 
> 
> If this data is as it appears, I share your opinion.
> "Complete locales: 41 (37%) - 95.07% of our l10n user base"
> (Plus I see no other viable recourse achievable in time for the required
> date).
> 
> Could you please take screenshots of each state and attach them here?

Screenshot not-signed-in: https://screenshots.firefox.com/0DGevfwAvELfLjxW/www-demo3.allizom.org
Screenshot signed-in: https://screenshots.firefox.com/18LmhHXwyVB0zM7n/www-demo3.allizom.org

Vince, above are screenshots of the proposed design for this page. Please give feedback if any. Thanks

Comment 20

[Alex Gibson [:agibson]]

Eric, please confirm the approach (plus screenshots) here with the requesting team. If all is good, we can move forward and manually build a new lang file for this page, targeting the ~41 locales to show the /whatsnew page to.

Comment 21

[Eric Renaud [:erenaud]]

David & Michele - can you please review these screenshots for approval?

Content shown to users not-signed-in to Fx Account: https://screenshots.firefox.com/0DGevfwAvELfLjxW/www-demo3.allizom.org

Content shown to users signed-in to Fx Account: https://screenshots.firefox.com/18LmhHXwyVB0zM7n/www-demo3.allizom.org

I'll sum up the comments above to state that in order for this to work/launch on time, we're 'stuck' with the content shown to users signed-in to Fx Account, as in we can't really change it based on available strings. That being said, let's not forget the goal here, which is to get users to Sign Up.

Comment 22

[David Tenser [:djst]]

I understand the constraints of reusing existing strings and if there's anything here that would need my approval, it would be the merging of the copy for users already logged in. It looks OK to me and this is a worthy change to hopefully increase FxA signups. Go!

Comment 23

[Francesco Lodolo [:flod]]

(In reply to Francesco Lodolo [:flod] from comment #18)
> (In reply to Francesco Lodolo [:flod] from comment #17)
> > What we need is to build a separate lang file with those string, and then
> > figure out which locales can be enabled.
> 
> At the moment, this list would be:
> 
> Complete locales (43):
> an, bg, bs, cak, cs, cy, da, de, dsb, eo, es-AR, es-CL, es-ES, es-MX, et,
> fa, fi, fr, fy-NL, gu-IN, hsb, hu, hy-AM, it, ja, ja-JP-mac, ka, ms, nb-NO,
> nl, nn-NO, pl, pt-BR, pt-PT, ru, sk, sl, sq, sv-SE, tr, uk, zh-CN, zh-TW

I pushed the page out
https://l10n.mozilla-community.org/langchecker/?locale=all&website=0&file=firefox/whatsnew_59.lang

On a side note, if we want to update the WNP content in the future, we should put aside enough time in the schedule to properly set things up without rushing it last minute.

Comment 24

[Vince Joy]

Alex, looks fine to me.

thanks!

Comment 25

[Alex Gibson [:agibson]]

(In reply to Francesco Lodolo [:flod] from comment #23)
> On a side note, if we want to update the WNP content in the future, we
> should put aside enough time in the schedule to properly set things up
> without rushing it last minute.

Agreed, there should not be an assumption here that we can quickly and easily repurpose an existing page for a different audience at short notice. In future, it woould be good to involve both developers and our l10n team earlier in the planning stage here.

Comment 26

[Alex Gibson [:agibson]]

OK, demo is updated:

https://www-demo3.allizom.org/en-US/firefox/59.0/whatsnew/

- Signed in users see a QRCode to download Firefox on mobile.
- Signed-out users see the Firefox Accounts iframe.

Note: To test the page functionality, you'll need to set up a test profile [1] and also enable uitour for the demo server [2]

Peter, can we please make sure this experience is tracked appropriately in GA? Happy to run through this with you if it helps.

I'm also needsinfo'ing Ryan Kelly for visibility here. The iframe params are identical to /firstrun, but I changed the following:

- utm_source=whatsnew
- entrypoint=whatsnew

Happy to use any alternatives you would prefer here?

[1] http://bedrock.readthedocs.io/en/latest/firefox-accounts.html#demo-server-testing
[2] http://bedrock.readthedocs.io/en/latest/uitour.html

Comment 27

[pgerman]

I believe that is correct. The utm parameters in the FxA iframe are sent into amplitude which I'm not responsible for maintaining. 

ni'ing - Alex Davis for guidance.

Comment 28

[Ryan Kelly [:rfkelly]]

> I'm also needsinfo'ing Ryan Kelly for visibility here. 

Thank you :-)

I appreciate the visibility, but I'll defer to :adavis for any comments on the metrics params etc.

Comment 29

[pgerman]

Also, for the QR code, this link will require an Adjust QR code.

Comment 30

[Alex Gibson [:agibson]]

This page has now fininshed in code review. We're now just waiting on current needsinfo's before pushing this live.

Comment 31

[Alex Davis [:adavis]]

UTM Source looks good to me.
rfkelly: I know that the entrypoint impacts the flow (e.g. may or may not see SMS after) I just remember STomlinson telling me about how it had to be a few different options. Is what they are proposing correct?


From past tests, we've proven that while we want to encourage people to use SMS, it's important to put the app store badges below the form so people know what they are sending themselves AND so they know that they have an alternative way of installing our app.

This is especially true for markets that we don't support SMS. People don't want to have to put their email in to know where they can find our mobile browser.

You can see this in the conclusion here:
https://mana.mozilla.org/wiki/display/FIREFOX/Send+to+Device+vs+Google+Play+Button

Comment 32

[Eric Renaud [:erenaud]]

Alex (Gibson) - Michele gave approval in Slack just now.  We're good to go from that (required approvals) perspective.

I reached out in email to Cherry and Devyani requesting the QR code w. Adjust link.

We do have the current version of it to use, it is functional, should we not received the update in time for launch.

Comment 33

[Ryan Kelly [:rfkelly]]

> rfkelly: I know that the entrypoint impacts the flow (e.g. may or may not see SMS after)
> I just remember STomlinson telling me about how it had to be a few different options.

Hrm, I'm not aware of any instances where the value of `entrypoint` affects the flow, we usually base flow decision on the `context` value.  Vlad, does this ring any bells for you?

> Is what they are proposing correct?

The value seems OK to me, inasmuch as it'll pass validation and be correctly propagated around.  We should add it to the list of known values in https://github.com/mozilla/fxa-content-server/blob/master/docs/client-metrics.md for completeness, which I'm happy to do after Vlad sanity-checks the question above.

Comment 34

[Vlad Filippov (:vladikoff)]

(In reply to Ryan Kelly [:rfkelly] from comment #33)
> > rfkelly: I know that the entrypoint impacts the flow (e.g. may or may not see SMS after)
> > I just remember STomlinson telling me about how it had to be a few different options.
> 
> Hrm, I'm not aware of any instances where the value of `entrypoint` affects
> the flow, we usually base flow decision on the `context` value.  Vlad, does
> this ring any bells for you?
> 
> > Is what they are proposing correct?
> 
> The value seems OK to me, inasmuch as it'll pass validation and be correctly
> propagated around.  We should add it to the list of known values in
> https://github.com/mozilla/fxa-content-server/blob/master/docs/client-
> metrics.md for completeness, which I'm happy to do after Vlad sanity-checks
> the question above.

Yea that is correct. Keep in mind the validation for that param is

`const ENTRYPOINT_PATTERN = /^[\w.-]+$/;` 

Gien `whatsnew` it should be fine.

Comment 35

[Vlad Filippov (:vladikoff)]

Gien -> Given

Comment 36

[Alex Gibson [:agibson]]

As per Comment 32, I'm clearing the needsinfo for Michelle, who approved this page via Slack.

Looks like we're just waiting on Cherry and Devyani to respond before we can push this live.

Comment 37

[Devyani]

Attachment: QR Code and Tracking link

Hi there,

Please see attched the QR code and here is the Adjust link as well:

https://app.adjust.com/2uo1qc?campaign=whats_new&adgroup=QR Code&creative=59_Experiment

Comment 38

[Alex Gibson [:agibson]]

(In reply to Devyani from comment #37)
> Created attachment 8956276 [details]
> QR Code and Tracking link
> 
> Hi there,
> 
> Please see attched the QR code and here is the Adjust link as well:
> 
> https://app.adjust.com/2uo1qc?campaign=whats_new&adgroup=QR
> Code&creative=59_Experiment

This image is too small and will be blurred when stretched. Please supply a QRCode with the same dimensions as the one seen in the /whatsnew page (350x350px).

Comment 39

[Devyani]

(In reply to Alex Gibson [:agibson] from comment #38)
> (In reply to Devyani from comment #37)
> > Created attachment 8956276 [details]
> > QR Code and Tracking link
> > 
> > Hi there,
> > 
> > Please see attched the QR code and here is the Adjust link as well:
> > 
> > https://app.adjust.com/2uo1qc?campaign=whats_new&adgroup=QR
> > Code&creative=59_Experiment
> 
> This image is too small and will be blurred when stretched. Please supply a
> QRCode with the same dimensions as the one seen in the /whatsnew page
> (350x350px).

Cherry, can you translate the below Adjust link in the High res QR code? see above.
 https://app.adjust.com/2uo1qc?campaign=whats_new&adgroup=QR Code&creative=59_Experiment

Comment 40

[Devyani]

Attachment: 59 Experiment high res.png

Please see high res attached. Let me know if this doesnt work.

Comment 41

[Alex Gibson [:agibson]]

(In reply to Devyani from comment #40)
> Created attachment 8956545 [details]
> 59 Experiment high res.png
> 
> Please see high res attached. Let me know if this doesnt work.

This will work fine, thank you

Comment 42

[[github robot]]

Commit pushed to master at https://github.com/mozilla/bedrock

https://github.com/mozilla/bedrock/commit/98d14b1756981f7932d84a110184d4874a3f75e2
[fix bug 1438633] Add /whatsnew page for Firefox 59 with FxA CTA

Comment 43

[Liz Henry (:lizzard) (relman/hg->git project)]

Is this actually fixed for 59?

Comment 44

[Alex Gibson [:agibson]]

(In reply to Liz Henry (:lizzard) (needinfo? me) from comment #43)
> Is this actually fixed for 59?

Yes: https://www.mozilla.org/en-US/firefox/59.0/whatsnew/