Usage
Events and naming
Model user or system actions consistently so your funnels, flows, and insights remain durable as the product evolves.
Source of truth
server/engine/cmd/sankofa/main.goEvents in Sankofa represent user or system actions. Good events are:
- action-oriented
- stable over time
- scoped to one meaningful thing happening
Good examples
signup_completedcheckout_startedpayment_failedinvite_acceptedapi_request_failedworkspace_created
Keep properties for context
Use properties for the dimensions that vary:
- plan
- currency
- screen
- source
- failure_code
- experiment_variant
This keeps the event namespace compact while preserving the detail needed for analysis.