Quick Start
Fire a custom event from your application:Event Structure
Events have a name and optional data payload:Naming Conventions
Use descriptive, snake_case names that follow a consistent pattern:Setting Up Triggers
Triggers in the dashboard can listen for custom events and perform actions. Create a trigger with:- Trigger Type:
Custom Event - Event Name: The exact event name you fire (e.g.,
checkout_abandoned) - Action: What happens when the event fires
Trigger Actions
Conditional Triggers
Use event data to conditionally trigger actions:cartTotal > 200.
Common Use Cases
E-commerce Events
SaaS Events
Content & Engagement
User Journey Events
Implementation Patterns
React Integration
Vue Integration
Vanilla JavaScript
Scroll Depth Tracking
Time on Page
Combining with Identity
Events are more powerful when combined with user identity:Debugging Events
Check the browser console for event confirmation:Best Practices
- Use consistent naming — Establish a naming convention and stick to it
- Include relevant context — Add data that helps understand the event
- Avoid PII in event data — Don’t include emails, names, or sensitive info in event payloads (use
identify()instead) - Test triggers — Verify events fire correctly before deploying
- Document your events — Maintain a list of events and their meanings
Next Steps
Identity
Associate events with user profiles
Webhooks
Send event data to external systems