Overview
Consistent naming makes your data easier to understand, query, and maintain. This guide covers recommended conventions for events, properties, and user attributes.Event Naming
Use snake_case
Use Action Verbs
Events should describe what happened:Include Object and Action
Pattern:{object}_{action} or {action}_{object}
Use Past Tense for Completed Actions
Group Related Events
Use prefixes to group related events:Property Naming
Use snake_case
Be Specific
Include Units
Use Boolean Prefixes
Use Consistent Prefixes
User Profile Properties
Identity Properties
Lifecycle Properties
Web3 Properties
Anti-Patterns
High-Cardinality Event Names
Dynamic Event Names
Excessive Granularity
PII in Event Names
Naming Checklist
Before shipping tracking code, verify:1
snake_case
All event and property names use snake_case
2
Clear action
Event names describe a specific action
3
Specific properties
Properties are specific (not just
amount or value)4
Units included
Numeric properties include units (
_usd, _seconds, etc.)5
Boolean prefixes
Boolean properties use
is_, has_, was_, can_6
No PII in names
PII is in properties, not event/property names
7
Consistent
Similar events use consistent naming patterns
Examples by Category
E-commerce / DeFi
User Lifecycle
Web3 Specific
Next Steps
Implementation Guide
Full implementation patterns
Track Events
SDK track() reference