Instrumentation specification
https://docs.google.com/spreadsheets/d/1UfnYdAspvhkQLzh2iRYX7ystnKXI1loYlVsNcisWALc/edit?gid=0#gid=0
Acceptance criteria
- Experiment is implemented in code
- Users in Control (control) group get status quo (default) experience
- Users in treatment variation group(s) get appropriate changes in 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 user experience diverges between variations (see guide)
- 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
- [If applicable] Instrumentation checks user eligibility in experiment epic (see parent task)
- Experiment is configured in GrowthBook: https://growthbook.wikimedia.org/experiment/exp_1bfnmuhfwjes#overview
- Details match those in measurement plan https://docs.google.com/document/d/1BR99hgPiCL3rNGMU8to15WUsu25WkX0S0lfQdORGkzA/edit?tab=t.0
- Tracking key and variation keys are aligned with the values in the linked instrumentation spec
- Variations have images added to show the change(s) being tested
- Create a Phab task to clean up experiment code after the experiment is over: [Task]