This ticket is for capturing instrumentation work that will need to be done for #anti-harassment project, #ipbee_ip-blocked_editor_experience.
== What do we want to learn?
- How many times account creation happened using the IPBEE popup?
- The success rate for account creation. Break down on dimension: device: mobile vs desktop.
- Did user finish the editing after account creation?
- How many times login happened using the IPBEE popup?
- How many times user clicked “login”
- The success rate for login.
- Did user finish the editing after login?
- Hypothesis to test: more people will complete the creating an account and finish editing.
- More account creations
- More edits from newcomers
- More editors are newcomers
== Next steps in data process (bolding indicates step we are currently on):
PM and Data Analyst coordinate to identify experiment design, research questions, metrics and guardrails for the new feature and associated metrics.
Data analyst creates a list of events that need to be tracked to calculate each metric.
**Engineers review the event list and comment on whether we’re already tracking with existing instruments and if new instrumentation is required. New tickets created for any new instrumentation needed.**
Data analyst works with engineers to figure out what the new instrumentation should look like and where to store the events.
Data analyst documents all of the above in the instrumentation spec
PM signs off on the plan
== Instrumentation Spec
Documentation: [[ https://docs.google.com/spreadsheets/d/1Q3eeXl-Z8ae5yt7l7tXQK0EgUXi76_vVrbSs7i_6Ees/edit?usp=sharing | Instrumentation Spec ]]