1779514 - Add Privacy segmentation screen for existing users MR onboarding

Status: VERIFIED FIXED

(Firefox :: Messaging System, task, P1)

Description

[Punam Dahiya [:pdahiya]]

Scope of this bug is to add Privacy segmentation screen for existing users MR onboarding

Comment 1

[Punam Dahiya [:pdahiya]]

NI @vtay to help provide image to be used on Pin Private browsing promo. Thanks

Comment 2

[Vtay]

(In reply to Punam Dahiya [:pdahiya] from comment #1)

NI @vtay to help provide image to be used on Pin Private browsing promo. Thanks

Here is the link to the asset: https://drive.google.com/drive/folders/1slOsmfvctpY8f1GhZe-ATK73VVKKLbcp?usp=sharing
Thank you @acargo!

Comment 3

[Negin]

Attachment: Bug 1779514 - Add asset needed for about:privatebrowsing pin promo

Comment 4

[Negin]

Please disregard the context above ^ because of an incorrect commit, the original ticket is now being swapped to define Add Privacy segmentation screen for existing users MR onboarding. The following context is the correct one:

Scope of this bug is to add Privacy segmentation screen for existing users MR onboarding

User Story
As a product manager, I would like to prompt existing users to choose the level of communication about the rollout of the features that use their browsing data for optimal experience, so that users trust Firefox.

Figma File
Please note the copy here is not finalized, but the informational architecture is ready to go.

Acceptance Criteria

1. Users are presented with the text prompt explaining the choice and two options to pick from.
2. Based on user choice, a pref value is set:
   More communication - > set browser.privacySegmentation.enabled pref to false.
   Less communication -> set browser.privacySegmentation.enabled pref to true.
   There is no bypass CTA available on the screen, and users have to choose one of the options to move to the next step.

Comment 5

[Punam Dahiya [:pdahiya]]

Privacy Segmentation is still in review with product with decision on moving parts by August 4th. Thanks

Comment 6

[Ania]

Hi Negin,

We have the final copy for this screen, and we were able to avoid the two primary CTAs UI we originally planned for this screen.

I wanted to ask if this late change doesn't create a problem and we can still do it?

Our final CTA and pref values:
Firefox recommendations - > set browser.privacySegmentation.enabled pref to false.
Detailed information -> set browser.privacySegmentation.enabled pref to true.

Comment 7

[Jason Prickett]

ni: @asafko, Upon the user clicking one of these buttons, should they also be taken to the next screen in addition to the pref being set?

Comment 8

[Ania]

Yes, that's correct, my apologies for not specifying that button clicks set the pref value AND move the user to the next screen.
Thank you!

Comment 9

[Ed Lee :Mardak]

Strings getting added in bug 1781378 and probably using the new/renamed CTAParagraph from bug 1782812

Comment 10

[Jason Prickett]

Attachment: Bug 1779514 - Add privacy segmentation screen for existing users in MR Onboarding r=mardak,pdahiya

Comment 11

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/219d7f64a58f
Add privacy segmentation screen for existing users in MR Onboarding r=pdahiya

Comment 12

[Norisz Fay [:noriszfay]]

https://hg.mozilla.org/mozilla-central/rev/219d7f64a58f

Comment 13

[Marius Coman [:mcoman], Ecosystem QA]

I have verified this task and I can confirm the following:

• The "Privacy segmentation" modal is successfully displayed during the Onboarding flow for existing users.
• All the strings "Privacy segmentation" modal respect the Figma specifications.
• The "browser.privacySegmentation.enabled" pref is set to "true" if the "Use Firefox Recommendations" primary button is clicked.
• The "browser.privacySegmentation.enabled" pref is set to "false" if the "Show detailed information" secondary button is clicked.
• The "IMPRESSION" and "CLICK" (both primary and secondary button events) telemetry pings are successfully displayed in the "Browser Console".
• The background image does not respect the Figma, however, I will verify this again after Bug 1776689 lands.

Verified using the latest Firefox Nightly (106.0a1 Build ID - 20220830092750) installed on Windows 10 x64, macOS 11.6.5, and Linux Mint 20.2 x64.