Skip to main content
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 Installed or Application Opened (SDKs send these automatically)

Headers

string
required
HTTP Basic Auth. See Events Authentication.
string
default:"application/json"
required
Must be application/json.

Body

string
Identified user ID. At least one of userId or anonymousId is required.
string
Anonymous user ID if the user is not identified. Required if userId is not provided.
string
required
Name of the event (for example "Order Completed").
object
Event-specific data (for example order_id, revenue, currency).
string
When the event occurred, as ISO 8601.
object
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:

Response

Successful requests return HTTP 200 with an empty JSON object.