Event taxonomy: naming conventions that scale

Your analytics is only as good as your event names. A consistent taxonomy means your team — and the AI agents that read your metrics API — can ask questions without re-learning your data model. The goal is boring, predictable, queryable names.

Use snake_case for every event name: signup_click, plan_upgraded, checkout_completed. Reserve dots for namespacing vendored events, like adwords.conversion, so you never collide with your own events. Keep properties flat and typed: boolean for toggles, number for amounts, string for ids. Avoid reusing a property name for two different types — agents and humans alike will thank you.

Design funnels around verbs, not pages: start_checkout, add_payment_info, purchase. Because Tracabit stores eventParams per event, you can attach metadata like plan or value without changing the event name. That keeps your funnel definitions stable while your property vocabulary grows.

Document the taxonomy where your team already works — a markdown file in your repo or the Resources hub. Then enforce it in review: every new track() call should point to the documented name. Consistent events become the contract that makes agent-readable analytics reliable.