Only the "control" branch does not modify the default state of Tracking Protection throughout the study. The default state is TP ON for private windows only.
However, just to be safe, we can make a blanket rule: just reset built-in TP to ON for private windows only at the end of the study. The only exception is when the study ends because the user proactively changed the state of tracking protection (e.g. through about:preferences) as the reason the study is ending.
In all other cases, the survey at the end of the study will notify users that TP is currently turned off (except for private windows).
Important: The built-in TP UI should also be turned OFF at the beginning of the study. The pref for that is "privacy.trackingprotection.ui.enabled", and turned back ON at the end of the study.
Only the "control" branch does not modify the default state of Tracking Protection throughout the study. The default state is TP ON for private windows only.
However, just to be safe, we can make a blanket rule: just reset built-in TP to
ON for private windows onlyat the end of the study. The only exception is when the study ends because the user proactively changed the state of tracking protection (e.g. throughabout:preferences) as the reason the study is ending.In all other cases, the survey at the end of the study will notify users that TP is currently turned off (except for private windows).
Important: The built-in TP UI should also be turned OFF at the beginning of the study. The pref for that is
"privacy.trackingprotection.ui.enabled", and turned back ON at the end of the study.