Met with @ifried today and talked about the data assets. Here's the preliminary list of potential metrics to track moving forward (which we discussed today):

Registration Tool:

• Distinct participants registered in period
• Distinct organizers that joined as organizers in period
• Number of new accounts created in period
• New events in period
• Mobile vs desktop [for engineering &/or design decisions] TESTING NEEDED
• Devices [for QA purposes; may be satisfied as a preset notebook that QA engineer can run] TESTING NEEDED

Survey data:

• Age, gender, confidence TESTING/COLAB NEEDED

Event creation data:

• Event url & page creator name TESTING NEEDED

Event invitations: T365292
Event list:

• Pageviews
  • To the main page (pageviews) TESTING NEEDED
  • To event pages (referral source tracking) TESTING NEEDED

Met with @ifried yesterday and reviewed planning and status including data assets. Here's the current metrics we'll track moving forward:

Registration Tool:

Distinct participants registered in period
Distinct organizers that joined as organizers in period
Number of new accounts created in period
New events in period

Potentially data from T365292 and T365407 queries, assuming there's time to setup those pipelines and that the data is helpful for the team (testing|dissecting re: the latter is a necessary first step). When work on those two tickets is complete, and the data is available, I will pause the work on this ticket and will shift to completing those two tasks as a priority.