Provide company wide standards for event tracking.
Problem
As we build out the tracking systems and implement tracking throughout the application(s), it should be important that we do this holistically and consistently.
Proposal
First, we need to make sure we account for, and enable other teams to implement tracking in an easy and consistent fashion at multiple levels of the codebase. This includes Vue, HAML, and raw JavaScript for the frontend focused teams, and consistent methods for use within Ruby (and likely the Rails) levels as well. An important step here is to create wrapper interfaces for snowplow (and potentially others, pendo for instance) so if any point we want to expand or change our tracking services, we can do so with minimal coding effort.
Having that foundation in place will enable us to:
-
Add better documentation on how to implement tracking for existing features, as well as new features -
Add more clarity on what's being tracked, and why -
Provide ideas for how to create insights for teams who may not be focused on growth directly -
Add a new "Implements tracking" checkbox to MR templates and encourage tagging a growth team member to review
The final step, around adding this to MRs, is largely to make sure that we capture in documentation what's being tracked and the objective of those tracking events.
Result
We will have better and more consistent tracking, more data to assess, make assertions about, and ultimately test hypotheses on, while maintaining transparency in what we're doing and why.