Closed Bug 1563309 Opened 5 years ago Closed 5 years ago

[Experiment] Pref-Flip: Fingerprinting Protections Retention Study Fx 68.0 Release

Categories

(Shield :: Shield Study, task, P3)

Desktop
Unspecified

Tracking

(firefox68+ fixed, firefox69+ fixed)

RESOLVED FIXED
Tracking Status
firefox68 + fixed
firefox69 + fixed

People

(Reporter: experimenter, Assigned: arthur)

References

()

Details

(Whiteboard: Ready for Sign-Off)

User Story

Experiment Type: Pref Flip Experiment

    What is the preference we will be changing

privacy.trackingprotection.fingerprinting.enabled

    What are the branches of the experiment and what values should
    each branch be set to?

- Treatment treatment 50%:

Value: true

Fingerprinting is blocked
        
- Treatment control 50%:

Value: false

Fingerprinting is not blocked
        

    What version and channel do you intend to ship to?

0.9% of Release Firefox 68.0

    Are there specific criteria for participants?

Prefs:
Experiments:

Any additional filters:
    Please exclude:
    * https://experimenter.services.mozilla.com/experiments/feature-revenue-impact-study-for-enhanced-tracking-protection/
    * https://experimenter.services.mozilla.com/experiments/cryptomining-protections-retention-study/
    * https://experimenter.services.mozilla.com/experiments/strict-list-cookie-restrictions-3/
Countries: 

Locales: 

    What is your intended go live date and how long will the experiment run?

Jul 16, 2019 - Sep 10, 2019 (56 days)

    What is the main effect you are looking for and what data will you use to
    make these decisions?

This is a very similar study to the basic list cookie restrictions experiments [1, 2] and the strict list cookie restrictions experiment [3] - the main difference is that this has less of a focus on search ads, because we do not expect them to be directly impacted. We re-use the power-analysis from [1] as a ball-park size for the population.

Check for churn, reduced usage over time, or a reduction in the number of search ad clicks over time.

Specifically, for various values of `n`, analyze per-user data for between `n` and `n+1` weeks after the user enrolled, and estimate the relative uplift (with uncertainties) in the % of users with >x active hours, uri count, search count, or search ad click count, for enough values of x to cover the vast majority of users.

The data will be taken from the following probes, none of which are custom to this experiment:
browser.engagement.uri_count
browser.engagement.active_ticks

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1506908
[2] https://experimenter.services.mozilla.com/experiments/mid-65-default-on-cookie-restrictions-for-existing-users/
[3] https://experimenter.services.mozilla.com/experiments/strict-list-cookie-restrictions-3/

    Who is the owner of the data analysis for this experiment?

flawrence

    Will this experiment require uplift?

False

    QA Status of your code:

QA requested
Signed off as GREEN - https://experimenter.services.mozilla.com/experiments/fingerprinting-protections-retention-study/#comment340

    Link to more information about this experiment:

https://experimenter.services.mozilla.com/experiments/fingerprinting-protections-retention-study/

Fingerprinting Protections Retention Study

We plan to study the effect of fingerprinting protections for 0.9% of users. Churn will be monitored during the study to inform a decision whether to move fingerprinting protections to Standard tracking Protection in Firefox 70.

Experimenter is the source of truth for details and delivery. Changes to Bugzilla are not reflected in Experimenter and will not change delivery configuration.

More information: https://experimenter.services.mozilla.com/experiments/fingerprinting-protections-retention-study/

[Tracking Requested - why for this release]:

Hardware: Unspecified → Desktop
User Story: (updated)
Summary: [Experiment]: Pref-Flip: Fingerprinting Protections Retention Study → [Experiment] Pref-Flip: Fingerprinting Protections Retention Study Fx 68.0 Release
User Story: (updated)
Assignee: nobody → arthur
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.