Optimization of adding tracking event concepts in growth
Thoughts on some items/pain points
- uniqueness using category and name not enforced.
- current timestamp scheme misses opportunity to give date in a more readable format like migrations do.
- 1 file per tracking event seems sub-optimal. I would love to have something that matched our workflow a bit more and did 1 file per concept. For instance:
- Invite members modal in the top nav, I would like to be able to group all those events in 1 file as it maybe easier to consume on a testing level for verification.
- render, click_cancel, click_x, invite_successful
- I could then easily run a browser test and validate snowplow micro receives in it.
- render, click_cancel, click_x, invite_successful
- Invite members modal in the top nav, I would like to be able to group all those events in 1 file as it maybe easier to consume on a testing level for verification.
- recent MR for contextual discussion !112958 (merged)
- process for changing events and notifying product analytics team.
- standardize tracking conventions - naming, etc.
- things maybe changing a bit soon in &9610 (closed)
Plan
In general coordinate any updates below with ~"group::product intelligence"
-
Update event generator to use a more standard timestamp format that is used in migrations/metrics definitions/etc - !112961 (merged) -
Update snowplow docs and generator for force option - !112972 (merged) -
Update trigger source events for invite members modal to use underscore( _
) instead of hyphen(-
) - !129410 (merged)
Edited by Doug Stull