Skip to main content
Events capture user behavior and feed segmentation, workflows, and analytics.

​
What Events Power

  • behavior history and timeline context
  • event-driven tag assignment and removal
  • workflow trigger relevance
  • troubleshooting of ingestion and processing

​
Data Flow At A Glance

  1. Client sends event payload.
  2. Event enters incoming processing pipeline.
  3. On success, canonical event appears in Events.
  4. On failure, Incoming Events exposes status and process_error.

​
Endpoint Families

Common client routes:
  • POST /api/v1/client/events
  • POST /api/v1/client/events/bulk
  • GET /api/v1/public/authenticated/events
  • GET /api/v1/public/authenticated/events/incoming
Use API Reference for exact auth and schema details.

​
Event Type Vocabulary

Supported event type values:
  • signup
  • purchase
  • core_activity
  • referral
  • feature_used
  • support_ticket
  • cart
  • re_engagement
Keep your event naming and enum usage stable across environments.