Event taxonomy

A stable taxonomy prevents fragmented dashboards and broken comparisons over time.

• Prefer snake_case event names (for example onboarding_step_complete).
• Keep event names action-focused and past-tense where possible.
• Use consistent property keys (for example always plan_id, not mixed planId/plan).
• Version intentionally: add new events/properties instead of silently changing semantics.