Tracked Events
Send user actions + associate traceIds to users.
This is an advanced feature. We recommend exploring our SDKs and other integrations first before implementing a direct integration with our API endpoint. The most common use case for this endpoint is to send errors and tracked events from mobile and iOS devices.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Headers
Specifies whether this data is coming from a production source or not.
The name of the dataset you'd like to associate this data to. Not required, but highly recommended.
Body
A string UUIDv4 that uniquely identifies the event. Ensure the id looks something like this 62de9447-5d6b-496a-9164-d26f77fc8547.
The id does not need to include the dashes. If not set, we will generate an id on the server side.
This id is treated as a traceId so subsequent spans or logs with this id will be correlated with this tracked action.
The value of the event. This may be something like Opened App or Started Onboarding. Label this as something that would
cue you to know what the user was doing in this moment.
Not required. The category of the action, for example this could be Click or Navigate.
The timestamp of the event in JSON format (ie. 2023-11-25T13:08:50.782Z)
A key, value pairing of arbitrary event metadata that is useful to tag to your event.
Was this page helpful?