Submit an event asynchronously

Submits a consumer event asynchronously. No per-request rate limit - use for high-volume or bulk integrations. May return 429 only if the downstream ingestion queue is saturated. Only event_id is returned; person identification occurs asynchronously after the request returns.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
data
object | null
required

Open map of fields submitted with an event. May include keys beyond those listed here. email is the primary identity key and the only field that enables profile merging. partner_user_id is a secondary lookup key and is not guaranteed unique.

string
required

Name of the event being submitted (for example, conversion or registration). Required.

string
required

ISO 8601 timestamp of when the event occurred. Optional; defaults to the time the request is received. Use for backdated events.

Responses

Language
Credentials
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json