Instrumentation specification
https://docs.google.com/spreadsheets/d/1Ywz2_KlhtjZrqcH5I_ZHiJ7owMD2JtTCgF_u-8xelpY/edit?gid=0#gid=0
Acceptance criteria
- Experiment is implemented in code
- Users in Control (control) and Control 2 (control-2) groups get status quo (default) experience
- Experiment tracking key and variation keys are aligned with the values in the linked instrumentation spec
- Instrumentation spec is implemented and tested
- experiment_exposure events sent when experiment subject visits their Collections (since that's where we will have the upcoming A/B test of signals)
- All events in the spec are marked Yes (done)
- All specified events fire in relevant scenarios and user interactions
- All events data appears to be accurate and includes all the specified interaction data
- Experiment is configured in GrowthBook: https://growthbook.wikimedia.org/experiment/exp_anu814nmufxo852#overview
- Details match those in T439045: Experiment: DE1.2.2 Motivational moments A/A test
- Tracking key and variation keys are aligned with the values in the linked instrumentation spec
- Experiment is scheduled to go live on planned start date
- Create a Phab task to clean up experiment code after the experiment is over: T439048: [DE1.2.2] Clean up A/A test code