How to name analytics events
Short, stable names make every chart readable.
Use snake_case in object_verb form, past tense. Names are constants: never build them from user data.
| Good | Avoid |
|---|---|
project_created | CreateProject, click_button_3 |
checkout_completed | checkout-completed-for-alice |
timer_started | start |
invoice_sent | invoice sent! |
- Allowed characters:
A-Z a-z 0-9 _ . : -, up to 64. - Track meaningful actions: activation, core feature usage, conversion. Not every click or render.
- 5–15 events is typical for a product.
- Don’t name an event
page_viewed: it’s reserved for page views, which the SDK tracks for you. See Page views.
Related guides
DocsEvent props without personal data: limits and the PII guardAdd context to events without collecting personal data.DocsAPI reference: init, trackEvent, flushThree functions. None of them throw, and calls before init are ignored.DocsQuickstart: cookieless analytics in 5 minutesInstall the SDK, call init once, and see your first event. Five minutes, no cookie banner.