This ticket involves the work of implementing the instrumentation required to track how people are engaging with the Paste Check UX.
The instrumentation required to do the above was //largely// added as part of the Multi-Check feature implementation (T352092).
As such, this ticket largely holds the work of verifying the ` ===Requirements` have been implemented as expected.
=== Requirements
| feature | action | meaning
|---|---|---
|editCheck-paste|action-keep| User clicks 'Yes, keep it' button on Paste Check|
|editCheck-paste|action-remove| User clicks 'No, remove it' button on Paste Check|
|editCheck-paste|check-shown-presave; check-shown-midedit| Paste check was shown pre-save or mid-edit. An event will be sent for every check shown.|
|editCheck-paste|edit-check-feedback-shown| Decline survey is presented after user elects to keep text|
|editCheck-paste|edit-check-feedback-reason-[whatever you picked]| User selects a decline survey option and clicks 'submit'|
|editCheck-paste|check-control-[listener]|Logs when Paste Check would have been shown to someone in the control group|
|editCheck-paste|check-learn-more|User clicks on the learn more about copyright violation link within Paste Check|
[[ https://docs.google.com/spreadsheets/d/1C_0lWfpwZ5eparDd-njsX0knPTiK1zEavPX8BwdCiOA/edit?gid=2021246936#gid=2021246936 | instrumentation spec ]]
=== Progress
**Next steps**
- [ ] Megan to finish populating requirements
- [ ] David to confirm instrumentation is implemented
- [ ] Esther to QA
- [ ] Megan to QA
=== Done
- [ ] Editing QA verifies `===Requirements` are being logged client-side
- [ ] @Mneisler verifies `===Requirements` are being logged server-side