ddfat.md

Design Decision For Analytics Tracking

• Event name is following [this convention](Naming conventions: one step towards clean data) an Object-Action Framework eg.
  • Object: Account, Action: Signed Up
  • Object: Post, Action: Created
• Following that, means we can separate module (file) by object. eg. account has its own module.
• in each module, we can implement the detail about the tracking
  • params
  • transformation (if needed)
• if the tracking function seems do similar transformation before every calls, consider moving those logic into the tracking function itself. (eg. post.engaged)
• if the tracking depends on state changes, consider creating a component with hook in it to capture state changes from the context, app state, or any global-ish state (eg. ProfileUpdateTracker)