1946609 - Record exposure event for new treatment of showing the user when sync is disabled

Status: RESOLVED FIXED

(Firefox :: Sync, task)

Description

[Sammy Khamis [:skhamis]]

We'll be launching an experiment for updating the treatment of telling the user is signed in but sync is disabled. It was initially determined that we did not need to record the exposure and that existing telemetry should be sufficient but we won't be able to appropriately see who was actually exposed to the new/old treatment without it https://docs.google.com/document/d/1ehPjvSjLUtlcRQmFaxcPlmX1dtyhAUEcLAj2AAi3udo/edit?tab=t.0.

Comment 1

[Sammy Khamis [:skhamis]]

Attachment: Bug 1946609 - Record exposure event for new treatment of sync being disabled r=LougeniaBailey

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/86b4f0784cb4
Record exposure event for new treatment of sync being disabled r=LougeniaBailey

Comment 3

[amarc]

https://hg.mozilla.org/mozilla-central/rev/86b4f0784cb4

Comment 4

[Sammy Khamis [:skhamis]]

Attachment: Bug 1946609 - Record exposure event for new treatment of sync being disabled r=LougeniaBailey

Original Revision: https://phabricator.services.mozilla.com/D237148

Comment 5

[Phabricator Automation]

beta Uplift Approval Request

• User impact if declined: Will not be able to determine optimal sync flow
• Code covered by automated testing: yes
• Fix verified in Nightly: yes
• Needs manual QE test: no
• Steps to reproduce for manual QE testing: 1. about:config set nimbus.debug to true, 2. sign in to FxA but disable sync, 3. open app menu, 4. go to about:telemetry 5. in Events see expose event for ew-sync-setup-flow
• Risk associated with taking this patch: Low
• Explanation of risk level: Adding exposure event for opening the app menu, low amount of code
• String changes made/needed: N/A
• Is Android affected?: no

Comment 6

[Pulsebot]

https://hg.mozilla.org/releases/mozilla-beta/rev/599f5200f541

Comment 7

[Sammy Khamis [:skhamis]]

Attachment: Bug 1946609 - Record exposure event for new treatment of sync being disabled r=LougeniaBailey

Original Revision: https://phabricator.services.mozilla.com/D237148

Comment 8

[Phabricator Automation]

release Uplift Approval Request

• User impact if declined: Will not be able to determine optimal sync flow
• Code covered by automated testing: yes
• Fix verified in Nightly: yes
• Needs manual QE test: no
• Steps to reproduce for manual QE testing: 1. about:config set nimbus.debug to true, 2. sign in to FxA but disable sync, 3. open app menu, 4. go to about:telemetry 5. in Events see expose event for ew-sync-setup-flow
• Risk associated with taking this patch: Low
• Explanation of risk level: Adding exposure event for opening the app menu, low amount of code
• String changes made/needed: N/A
• Is Android affected?: no

Comment 9

[Jessilyn Davis]

[Tracking Requested - why for this release]:

Release uplift comment above. This is tangentially related to the Relay experiment that's going live in 135.

Comment 10

[Pulsebot]

https://hg.mozilla.org/releases/mozilla-release/rev/ab83cf3938ed