Track
Data Pipelines
Track
Record a user action or business event
POST
Track
Description
Record a user action or business event. This is the most commonly used endpoint for custom event tracking. Short alias:POST /v1/t
When to use:
- Any user action: button tapped, purchase completed, feature used
- Business events from your server: subscription renewed, payment failed
- Device lifecycle events such as
Application InstalledorApplication Opened(SDKs send these automatically)
Headers
HTTP Basic Auth. See Events Authentication.
Must be
application/json.Body
Identified user ID. At least one of
userId or anonymousId is required.Anonymous user ID if the user is not identified. Required if
userId is not provided.Name of the event (for example
"Order Completed").Event-specific data (for example
order_id, revenue, currency).When the event occurred, as ISO 8601.
Optional environment metadata (device, OS, app, IP, locale, and more). SDKs populate this automatically. See Context Object.
Semantic events
Certain event names trigger special handling beyond the standard event pipeline:| Event name | Special behavior |
|---|---|
Device Created or Updated | Routes to device registration pipeline |
Device Deleted | Soft-deletes device record (active=false) |
Device Registered | Routes to device logs table |
Device Updated | Routes to device logs table |
User Deleted | Sets is_deleted=true on profile, deactivates all devices |
User Suppressed | Sets is_suppressed=true, blocks all channel delivery |
User Unsuppressed | Clears suppression flag |
Application Installed | Routes to device logs table |
Application Opened | Routes to device logs table |
Application Backgrounded | Routes to device logs table |
Application Foregrounded | Routes to device logs table |
Application Crashed | Routes to device logs table |
Response
Successful requests returnHTTP 200 with an empty JSON object.