Closed
Bug 1481305
Opened 8 years ago
Closed 7 years ago
[Shield] Pref Flip Study: Default Browser Study, release 61
Categories
(Shield :: Shield Study, enhancement)
Shield
Shield Study
Tracking
(firefox61+ verified)
RESOLVED
FIXED
People
(Reporter: tdowner, Assigned: tdowner)
Details
(Whiteboard: deployed 61-release)
Basic description of experiment: Promoting non-default browser users to set Firefox as default
What is the preference we will be changing? browser.shell.checkDefaultBrowser
What independent variable(s) (IVs) are you manipulating to affect measurements of your DV(s)? What different levels (values) can each IV assume?
Prompt: browser.shell.checkDefaultBrowser TRUE
Control: Leave browser.shell.checkDefaultBrowser at False
What percentage of users do you want in each branch?
50/50 each, 1% overall
What Channels and locales do you intend to ship to?
Firefox 61.0.2 Release, en-US,
What is your intended go live date and how long will the study run?
Aug 20th, 2018
Run for two weeks, monitoring overall usage
Are there specific criteria for participants?
Non-Default, en-US, Windows, Mac
What is the main effect you are looking for and what data will you use to make these decisions? If a user accepts the prompt to set Firefox as default, does retention or any of our usage metrics go up?
Who is the owner of the data analysis for this study? Ilana
Will this experiment require uplift? No, the reqired fix is already in 61.0.2
QA Status of your code: N/a
Do you plan on surveying users at the end of the study? No
Link to any relevant google docs / Drive files that describe the project. Links to prior art if it exists:
https://www.mozdatacollective.com/extcontent/index/index/element/1268/ Survey run on users asking their perceived defaultness
Updated•8 years ago
|
status-firefox61:
--- → affected
Comment 1•8 years ago
|
||
Comment 7•8 years ago
|
||
peer r+ however it is worth noting that an enterprise policy exists that can stop us from using the value of this preference. It's unlikely that many of our users have the policy applied but I'm not qualified to judge whether that will affect your numbers.
Flags: needinfo?(dtownsend)
Comment 9•8 years ago
|
||
Felipe can probably help understand that. Felipe, can we tell from telemetry if a user has a specific policy applied?
Flags: needinfo?(felipc)
Comment 10•8 years ago
|
||
We don't collect telemetry on policies at the moment, but I wouldn't worry about this policy for this study. Most users of policies are on the ESR branch, so as long as this doesn't target ESR 60.*, I think we're fine.
Does the pref flip system supports any feedback about the previous value of the pref, or whether it was locked or not? Checking if the pref is locked and excluding these users would be an alternative way to detect that, if it's possible to do so.
Flags: needinfo?(felipc)
Comment 11•8 years ago
|
||
Ryan, passing this on to you for 61.
I agree we aren't likely to have many enterprise policy users on 61 release.
Flags: needinfo?(lhenry) → needinfo?(ryanvm)
Updated•8 years ago
|
tracking-firefox61:
--- → ?
Updated•8 years ago
|
Summary: [Shield] Pref Flip Study: Default Browser Study → [Shield] Pref Flip Study: Default Browser Study, release 61, release 61
Updated•8 years ago
|
Summary: [Shield] Pref Flip Study: Default Browser Study, release 61, release 61 → [Shield] Pref Flip Study: Default Browser Study, release 61
Comment 12•8 years ago
|
||
We have finished testing the Default Browser Shield Study experiment.
QA’s recommendation: GREEN - SHIP IT
Reasoning:
- No issues have been found during testing.
Testing Summary:
- Full Functional test suite: TestRail.
Tested Platforms:
- Windows 10 x64
- Windows 7 x64
- Mac 10.13.3
Tested Firefox version:
- Firefox Release 61.0.2, en-US
- Firefox Beta 62.0b17, en-US
Comments:
- We have also tested the study on Firefox Beta 62.0b17, en-US, because of a comment that appeared in the PHD document and which stated that the run time of the study may need to be longer. We haven’t received a confirmation on this matter from developers due to PTO.
Our concern was that the study could end up being live on both Firefox Release 61 and 62 with no coverage on the Beta channel.
Regards,
Remus
Flags: needinfo?(remus.dranca)
(Set flags for all approvals mentioned in the bug).
- Published: https://delivery-console.prod.mozaws.net/recipe/555/
- Observed in field.: New experiment id observed: Default_Browser_Pref-Flip: {"type":"normandy-exp","branch":"Control"}.
Status: NEW → ASSIGNED
Flags: shield-science+
Flags: shield-relman+
Flags: shield-qa+
Flags: shield-peer+
Flags: shield-data-steward+
Whiteboard: deployed 61-release
| Assignee | ||
Comment 15•7 years ago
|
||
Disabled on Friday. Josh Gaunt is on the hook for analysis
| Assignee | ||
Comment 16•7 years ago
|
||
Fixed. Pursuing full roll-out in Bug 1507011
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•