Closed Bug 1302246 Opened 9 years ago Closed 9 years ago

Version 2 - Create new page with OS-agnostic send to device widget

Categories

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

Product:
www.mozilla.org
Component:
Pages & Content
Version:
Production
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: erenaud, Assigned: jpetto)

References

(
URL
)

Details

(Whiteboard: [q4 sprint 1])

+++ This bug was initially created as a clone of Bug #1299336 +++ The Firefox durable team has asked us to add the "send to device" widget currently live on /firefox/android and /firefox/ios to the /firefox/mobile-download/ page to support a campaign to increase mobile downloads. Version 2 of this page must: - Include the additional localized links as detailed in the original, Version 1, bug - Be updated with the widget configured to use a custom basket message set - Go live in production on 9/19/2016
From bug 1299336 comment 41 [1], the Heartbeat promo has been delayed, which (probably?) means the original deadline for this bug of 9/19/2016 is no longer valid. mhan - Can you provide a new deadline for this page to be in use? If the new deadline is far in the future or TBD, I'd recommend de-activating the URL (but keeping the code in place) to avoid having an out-of-use orphaned page live on mozilla.org. Additionally, we should have a bit of a discussion regarding page functionality for users in locales that do not have a localized basket message. Is it okay/a good experience for them to receive an email in English? If not, what content should be shown in place of the widget? This may be a stress case, but should have an intentional and reasoned solution. Thanks! [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1299336#c41
Flags: needinfo?(mhan)
Eric, Im not sure what the options are here, can you schedule a quick 15-30 minute meeting next week to discuss?
Flags: needinfo?(mhan)
Whiteboard: [q3 sprint 5] → [q4 sprint 1]
Met w. jpetto and mhan today and determined the following - For version 2 we will: - Hide the widget and provide localized content for-non basket locales*. - Pick a string we already have for the generic message, display that message and the app store badges in place of the widget. *Basket emails are localized in: ES, FR, DE, PT-BR, RU, PL, ID
Ben - I can't recall status on work in basket for this v2 rollout. Can you please indicate what is/what needs to be done there?
Flags: needinfo?(bniolet)
The new target for launch here is FF 50 (currently scheduled for release on November 8th). Moz.org is taking this into our next sprint, Q4/S1 with expectation to complete within the sprint, then launch the changes on the date corresponding to FF50.
Assignee: nobody → jon
Should this new /whatsnew template be used for only 50.0 exactly, or used for any /whatsnew visitor on 50.0 and up? In the past, we've generally done the latter (target version and up), but if this is a campaign for a very specific moment in time, we can limit to only 50.0.
Flags: needinfo?(erenaud)
Hey Mike, See comment 6... I think the answer is 50.0 and up, but want to confirm with you.
Flags: needinfo?(mhan)
Jpetto - 50.0 and up! Thanks for checking.
Flags: needinfo?(mhan)
jpetto: yes, let's please go with the pre-localized string displaying that message (Download Firefox) and the app store badges in place of the widget.
Flags: needinfo?(erenaud)
A WIP version of the page is up on a demo. Here are some URLs to test: User is in en-* locale and gets widget with custom en-* headline: https://bedrock-demo-jpetto-fx50.us-west.moz.works/en-US/firefox/50.0/whatsnew/ User is in non-en-* basket-supported locale (de, es-ES, fr, id, pl, pt-BR, ru) and gets widget with fallback, pre-localized headline: https://bedrock-demo-jpetto-fx50.us-west.moz.works/fr/firefox/50.0/whatsnew/ User is not in a basket-supported locale and gets no widget with generic, pre-localized "Download Firefox" headline: https://bedrock-demo-jpetto-fx50.us-west.moz.works/it/firefox/50.0/whatsnew/
Eric and LCM team are coordinating on what needs to happen from a basket, email side. Clearing the NI for me. Re-ping if there's something I can add.
Flags: needinfo?(bniolet)
Thanks JPetto. The page looks good. Why did the URL change from the original (https://bedrock-demo-jpetto-mobiledl.us-west.moz.works/en-US/firefox/mobile-download/desktop/)
(In reply to mhan@mozilla.com from comment #12) > Thanks JPetto. The page looks good. Why did the URL change from the > original > (https://bedrock-demo-jpetto-mobiledl.us-west.moz.works/en-US/firefox/mobile- > download/desktop/) The new URL follows our standard convention for /whatsnew pages: /firefox/{version}/whatsnew/. This was created as a fork of the old page/URL, meaning we can re-activate that page with different copy if/when needed. If this page is targeted at upgrading users, I think the copy and URL should reflect that intent. I think it is possible to configure product to point to any URL when upgrading. Do you see an advantage to using the old, non-standard URL for this /whatsnew page?
Flags: needinfo?(mhan)
JPetto, This page isnt targeted at upgrading (the version) of Fx desktop users - we are only launching this page with beginning Fx50 because Fx50 will have a recommender to cross promote from desktop to mobile. This landing page shouldnt be tagged specifically to Fx50 because we will be using it as an evergreen page for any desktop to mobile cross promotions through the recommender.
Flags: needinfo?(mhan)
per mtg w. mhan, jbalaco, jbertsch, jpetto: confirming that both URLs will go live for FF50 as: /whatsnew and (the original) /mobile-download/desktop, the latter of which will be used going forward for multiple campaigns. The forthcoming copy intended for en-US will *not* be localizable as it will likely change.
Michele - when the new message IDs in Basket are available, please provide (or have the assigned person from your team do so) those in this bug, clearing the needinfo for you at that time. Many thanks.
Flags: needinfo?(mwarther)
The demo server now has both URLs active: # /firefox/mobile-download/desktop Custom en-* headline: https://bedrock-demo-jpetto-fx50.us-west.moz.works/en-US/firefox/mobile-download/desktop/ Localized fallback headline with send to device widget: https://bedrock-demo-jpetto-fx50.us-west.moz.works/fr/firefox/mobile-download/desktop/ Localized fallback headline without send to device widget: https://bedrock-demo-jpetto-fx50.us-west.moz.works/it/firefox/mobile-download/desktop/ # /firefox/50.0/whatsnew/ Custom en-* headline (still TBD): https://bedrock-demo-jpetto-fx50.us-west.moz.works/en-US/firefox/50.0/whatsnew/ Localized fallback headline with send to device widget: https://bedrock-demo-jpetto-fx50.us-west.moz.works/fr/firefox/50.0/whatsnew/ Localized fallback headline without send to device widget: https://bedrock-demo-jpetto-fx50.us-west.moz.works/it/firefox/50.0/whatsnew/
Ritu - the work in this bug includes the need to place custom content in (we'll take care of that) and to 'turn-on' /whatsnew in FF50. Can please let me know any requirements (file a separate bug?) to make that request and information you'll require? Thank you - Eric
Flags: needinfo?(rkothari)
Need to unblock you on the what anew copy. Please go with - ------------ ✔ Your Firefox is up to date. Now get on the go. Send Firefox to your phone and unleash your Internet.
Flags: needinfo?(jon)
The new copy for en-* /whatsnew users is now in. Revisit the URLs in comment 17 to view the update. To clarify, non en-* /whatsnew users who still receive the send to device widget (i.e. are in a locale supported by the basket messages) get a translated version of the following headline: "Send Firefox to your smartphone or tablet" This headline works okay, but doesn't have any /whatsnew-related information. Just want to ensure this is acceptable.
Flags: needinfo?(jon)
per conversation in irc, please add the pre-localized string "Thanks for choosing Firefox!" above the "Send Firefox to your smartphone or tablet", for the non en-* /whatsnew users who will see the send to device widget based on their locales (those supported by basket).
Flags: needinfo?(jon)
Flags: needinfo?(jon)
Hi Eric - I'm new to the LCM team, and am helping update the mobile download emails and create the new Basket ID for this effort. I was working with Jess Osorio on tracking links yesterday, and she mentioned that the download emails will also need to be localized for IT, CN, and JP - and that this will be used in Recommender instead of Heartbeat - which led to a a few questions/flags: 1. I'll need to investigate if basket can support delivering triggered messages to these currently not-supported locales. This investigation work can happen next sprint. 2. How is this being delivered in Recommender (i.e. are we using this new mobile page or do you know if there's a direct form in Recommender talking to Basket)? In reading through the Bug, it looks like we originally agreed to use the mobile download emails already in place for ES, FR, DE, PT, RU, PL and ID, so wanted to reach out for clarification. Thanks, Brynne
Hi Brynne, I can address some of these questions. 1. I'll need to investigate if basket can support delivering triggered messages to these currently not-supported locales. This investigation work can happen next sprint. > for the download email locales that are not support, we're okay defaulting to english email for now. 2. How is this being delivered in Recommender (i.e. are we using this new mobile page or do you know if there's a direct form in Recommender talking to Basket)? >The recommender is a door hanger in the desktop product. There will be a message prompt to download fx for mobile. When users click on it, they will be taken to the landing page with the send to device widget. When users put in their email address, they will get the standard download email that is triggered from the send to device page
Brynne - IT, CN and JP are not in scope for this user story/this sprint w. regard to Basket - only those locales originally cited, as those are the only ones supported in Basket. For common understanding: The logic in place for the /whatsnew and /mobile-download/desktop pages is to show the widget only to those locales supported in Basket. All other unsupported locales will see (pre-)localized copy and the two store badges, but no widget, as the previously agreed upon statement (requirement) was that sending an email in English to non-EN locales was an undesirable user experience. Defaulting to English email is therefore not a consideration, citing this requirement and, moreover, citing the fact that only en-US and the locales corresponding to the current basket email locales will see the widget. I don't know that Recommender and Basket will cross paths at all, from what MHan has stated? Mike - can you provide or point me to more information about Recommende, please?
Flags: needinfo?(mhan)
Flags: needinfo?(mhan)
Brynne, Eric is right that IT, CN and JP are not in scope for the basket work. We may however do some small tests on the recommender promotion side to see the results, but thats down the line and Im not expecting any additional basket work.
Eric and Mike - Thanks for the clarification and additional information, it's super helpful! I'll continue working on getting the mobile download emails and triggers ready for the agreed upon locales mentioned above. Brynne
Hi Brynne - When you have the new basket message IDs, please add those to this bug and assign a 'needinfo' to :jpetto
Flags: needinfo?(mwarther) → needinfo?(bhaack)
Hi Eric - The new Basket ID is: download-firefox-mobile-reco.
Flags: needinfo?(bhaack) → needinfo?(jon)
The triggers are activated, so please let me know once they're in a testing environment and we'll QA the different languages to make sure everything is working correctly before going live. Thanks, Brynne
The demo server has been updated with the new basket ID: https://bedrock-demo-jpetto-fx50.us-west.moz.works/en-US/firefox/mobile-download/desktop/ https://bedrock-demo-jpetto-fx50.us-west.moz.works/en-US/firefox/50.0/whatsnew/ I just submitted and got what appears to be the correct email response. Let us know how the testing turns out!
Flags: needinfo?(jon) → needinfo?(bhaack)
I tested all 8 locales in the two test environments listed above, and everything appears to be working correctly. From our end, everything looks good to go! Thanks, Brynne
Flags: needinfo?(bhaack)
The email and text also worked for me in US. Is there away to confirm the Adjust tracking is working correctly? Can you confirm which adjust links were used in this page?
(In reply to Eric Renaud from comment #18) > Ritu - the work in this bug includes the need to place custom content in > (we'll take care of that) and to 'turn-on' /whatsnew in FF50. > > Can please let me know any requirements (file a separate bug?) to make that > request and information you'll require? > > Thank you - Eric Hello Eric, this plan seems good to me. Will there be a patch uplift needed to mozilla-beta repo for this?
Flags: needinfo?(rkothari)
(In reply to mhan@mozilla.com from comment #32) > The email and text also worked for me in US. Is there away to confirm the > Adjust tracking is working correctly? Can you confirm which adjust links > were used in this page? I *think* you're asking about the adjust links used in the new email template, but to confirm, the adjust links used on the web page are as specified in bug 1299336 comment 3 [1]. Brynne would need to verify the URLs used in the new email template, as they appear to be re-written into click.e.mozilla.org URLs. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1299336#c3
(In reply to Ritu Kothari (:ritu) from comment #33) > Hello Eric, this plan seems good to me. Will there be a patch uplift needed > to mozilla-beta repo for this? Honestly don't know if it should hit beta first (or does it have to do so, according to release cycle 'rules'?). If it is uplifted and thereby made part of the release, would it then be functional for that and all the following 50 beta releases? Sorry, I have more questions than answers here . . .
Hey All - Below are the links being used in the emails: EN Android https://app.adjust.com/2uo1qc?campaign=desktop_xp&adgroup=send_to_device&creative=email_android_en iOS https://app.adjust.com/2uo1qc?campaign=desktop_xp&adgroup=send_to_device&creative=email_ios_en&fallback=https%3A%2F%2Fitunes.apple.com%2Fapp%2Fapple-store%2Fid989804926%3Fru%3D373246%26ct%3Dadjust_tracker%26mt%3D8 --- ES Android https://app.adjust.com/2uo1qc?campaign=desktop_xp&adgroup=send_to_device&creative=email_android_es iOS https://app.adjust.com/2uo1qc?campaign=desktop_xp&adgroup=send_to_device&creative=email_ios_es&fallback=https%3A%2F%2Fitunes.apple.com%2Fes%2Fapp%2Fapple-store%2Fid989804926%3Fru%3D373246%26ct%3Dadjust_tracker%26mt%3D8 --- DE Android https://app.adjust.com/2uo1qc?campaign=desktop_xp&adgroup=send_to_device&creative=email_android_de iOS https://app.adjust.com/2uo1qc?campaign=desktop_xp&adgroup=send_to_device&creative=email_ios_de&fallback=https%3A%2F%2Fitunes.apple.com%2Fde%2Fapp%2Fapple-store%2Fid989804926%3Fru%3D373246%26ct%3Dadjust_tracker%26mt%3D8 --- FR Android https://app.adjust.com/2uo1qc?campaign=desktop_xp&adgroup=send_to_device&creative=email_android_fr iOS https://app.adjust.com/2uo1qc?campaign=desktop_xp&adgroup=send_to_device&creative=email_ios_fr&fallback=https%3A%2F%2Fitunes.apple.com%2Ffr%2Fapp%2Fapple-store%2Fid989804926%3Fru%3D373246%26ct%3Dadjust_tracker%26mt%3D8 --- PT Android https://app.adjust.com/2uo1qc?campaign=desktop_xp&adgroup=send_to_device&creative=email_android_pt iOS https://app.adjust.com/2uo1qc?campaign=desktop_xp&adgroup=send_to_device&creative=email_ios_pt&fallback=https%3A%2F%2Fitunes.apple.com%2Fpt%2Fapp%2Fapple-store%2Fid989804926%3Fru%3D373246%26ct%3Dadjust_tracker%26mt%3D8 --- ID Android https://app.adjust.com/2uo1qc?campaign=desktop_xp&adgroup=send_to_device&creative=email_android_id iOS https://app.adjust.com/2uo1qc?campaign=desktop_xp&adgroup=send_to_device&creative=email_ios_id&fallback=https%3A%2F%2Fitunes.apple.com%2Fid%2Fapp%2Fapple-store%2Fid989804926%3Fru%3D373246%26ct%3Dadjust_tracker%26mt%3D8 --- RU Android https://app.adjust.com/2uo1qc?campaign=desktop_xp&adgroup=send_to_device&creative=email_android_ru iOS https://app.adjust.com/2uo1qc?campaign=desktop_xp&adgroup=send_to_device&creative=email_ios_ru&fallback=https%3A%2F%2Fitunes.apple.com%2Fru%2Fapp%2Fapple-store%2Fid989804926%3Fru%3D373246%26ct%3Dadjust_tracker%26mt%3D8 --- PL Android https://app.adjust.com/2uo1qc?campaign=desktop_xp&adgroup=send_to_device&creative=email_android_pl iOS https://app.adjust.com/2uo1qc?campaign=desktop_xp&adgroup=send_to_device&creative=email_ios_pl&fallback=https%3A%2F%2Fitunes.apple.com%2Fpl%2Fapp%2Fapple-store%2Fid989804926%3Fru%3D373246%26ct%3Dadjust_tracker%26mt%3D8 I've also checked the links in Adjust, and they appear to be tracking correctly. Please let me know if anything else is needed from my end. Thanks, Brynne
Mike & bhaack - In the interest of not writing duplicate code, I'd like to verify that the locales specified for this request are purposefully distinct from the general locales supported by the send to device widget: * specific for this page/request de, en-GB, en-US, en-ZA, es-ES, fr, id, pl, pt-BR, ru * general locales supported by send to device widget de, en-GB, en-US, en-ZA, es-AR, es-CL, es-ES, es-MX, fr, id, pl, pt-BR, ru Really the only difference is the inclusion of other es-* locales. We don't want to maintain two locale lists that are technically different by practically the same. If this campaign should specifically exclude es-AR, es-CL, and es-MX, then we can manage two lists of locales. If not, we'll stick to our pre-existing locale list. Thanks!
Flags: needinfo?(mhan)
Flags: needinfo?(bhaack)
jpetto, I have no issues adding the other es-* locales if the web page can support it and if brynne and the lifecycle marketing team can support the other languages. Whatever is easiest for the team.
Flags: needinfo?(mhan)
Yes, my only concern here is whether the es-* variations will indeed be directed via the basket id to the single es (es-ES) version email that will be sent from basket to the original requesters from each of es-* localized widget. If those locales aren't recognized and routed/sent as es-ES, we'll be provide a poor user experience.
(In reply to Eric Renaud from comment #39) > Yes, my only concern here is whether the es-* variations will indeed be > directed via the basket id to the single es (es-ES) version email that will > be sent from basket to the original requesters from each of es-* localized > widget. If those locales aren't recognized and routed/sent as es-ES, we'll > be provide a poor user experience. From IRC conversations yesterday, I am under the impression that basket only has one es translation per message that is sent to all es-* locales. Brynne - is that correct?
(In reply to Jon Petto [:jpetto] from comment #40) > (In reply to Eric Renaud from comment #39) > > Yes, my only concern here is whether the es-* variations will indeed be > > directed via the basket id to the single es (es-ES) version email that will > > be sent from basket to the original requesters from each of es-* localized > > widget. If those locales aren't recognized and routed/sent as es-ES, we'll > > be provide a poor user experience. > > From IRC conversations yesterday, I am under the impression that basket only > has one es translation per message that is sent to all es-* locales. Brynne > - is that correct? Correct - Basket doesn't currently support more than 2 character languages. If this is needed, we can explore what it would take, but it's out of scope for this project.
Flags: needinfo?(bhaack)
(In reply to bhaack from comment #41) > Correct - Basket doesn't currently support more than 2 character languages. > If this is needed, we can explore what it would take, but it's out of scope > for this project. Perfect. We'll move forward with the pre-existing locale list [1] for this set of basket messages. Thanks! [1] de, en-GB, en-US, en-ZA, es-AR, es-CL, es-ES, es-MX, fr, id, pl, pt-BR, ru
Hey Jon, The updated app store badge links for the "/desktop" page are ready one this page: https://docs.google.com/spreadsheets/d/151_fWwEPxmPN_AbHCp-sqAkshDCLaABRrVaowxoFS10/edit#gid=1107867494 *** See rows 2-46 *** The badges for the "/whatsnew" page are coming soon. They will also be on this same spreadsheet. Please let me know if you have any questions. Thank you, Jess O
Hey Jon, The updated app store badge links for the "/whatsnew" page are ready one this page: https://docs.google.com/spreadsheets/d/151_fWwEPxmPN_AbHCp-sqAkshDCLaABRrVaowxoFS10/edit#gid=1107867494 *** See rows 50-94 *** Please let me know if you have any questions. Thank you,
Flags: needinfo?(jon)
I've added the (very nicely organized) updated store badge URLs to the pull request. Now only waiting on new basket message IDs (and for the pushed back launch of Fx 50).
Flags: needinfo?(jon)
Message slug for the SMS "What's New?" page will be: whatsnewfifty SMS will be set up shortly.
Flags: needinfo?(jon)
SMS is working properly, based on a curl request I just sent. Let me know if you have any troubles.
Just tested the new SMS message and all worked as expected. Thanks Ben!
Flags: needinfo?(jon)
The basket ID for the Whats New campaign is: download-firefox-mobile-whatsnew Please let me know once the demo server has been updated with the new ID, and I'll run final QA.
Flags: needinfo?(jon)
The demo server [1][2] has been updated with the new SMS and email basket ids. Working as expected as far as I can tell! [1] https://bedrock-demo-jpetto-fx50.us-west.moz.works/en-US/firefox/mobile-download/desktop/ [2] https://bedrock-demo-jpetto-fx50.us-west.moz.works/en-US/firefox/50.0/whatsnew/
Flags: needinfo?(jon) → needinfo?(bhaack)
QA checked out on my end as well!
Flags: needinfo?(bhaack)
Commits pushed to master at https://github.com/mozilla/bedrock https://github.com/mozilla/bedrock/commit/12b567c83f7514fe57119bd34b4028c402a4400d [fix bug 1302246] Add URLs for mobile download desktop template: - /firefox/50.0/whatsnew/ - /firefox/mobile-download/desktop/ https://github.com/mozilla/bedrock/commit/4608ea89036092b809516f5be4a19259764b303b Merge pull request #4425 from jpetto/bug-1302246-fx50-whatsnew-mobile-download [fix bug 1302246] Add URLs for mobile download desktop template.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Please update copy in /whatsnew from comment 19 as (add in the 'it'): ✔ Your Firefox is up to date. Now get it on the go. Send Firefox to your phone and unleash your Internet.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Re-closing. Copy in comment 19 was/is correct
Status: REOPENED → RESOLVED
Closed: 9 years ago → 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.