Submit events
Submit user interaction events.
Description
Records user behavior that powers personalization, attribution, analytics, and model training.event_id must be the non-zero integer shown for an event in your dashboard. Event names such as "click" are display labels and are not accepted as identifiers.
Request
userId, itemId, eventId, contextId, sessionId, and requestId remain available, but all identifier aliases carry the same integer values. Event batches are capped at 200 events per request by default.
Response
inserted, processed, session) and an embedding_refresh block describing the async user-embedding refresh job that was enqueued for the affected users.
Errors
Authorizations
The access token received from the authorization server in the OAuth 2.0 flow.
Body
- object
- object[]
A user ID, a non-zero dashboard event_id, and a positive NSL-generated item_id are required. context_id is also a positive NSL-generated integer when supplied.
End-user identifier.
"user-abc123"
CamelCase alias for user_id.
Item ID returned by NSL ingestion.
x >= 13187
CamelCase alias for item_id.
x >= 1Non-zero event ID shown in dashboard Event configuration.
CamelCase alias for event_id.
Optional session identifier.
CamelCase alias for session_id.
Recommendation request ID to attribute this event to.
CamelCase alias for request_id.
Optional context ID created in the dashboard.
x >= 1101
CamelCase alias for context_id.
x >= 1101
Surface or placement where the event happened.
"home_feed"
Arbitrary JSON object used for filtering, ranking, and debugging.
Event occurrence timestamp. Numeric values below 1e12 are interpreted as Unix seconds.
1777478400
CamelCase alias for occurred_at.
Legacy timestamp alias.
Legacy client timestamp alias.
CamelCase alias for client_ts.
Response
Inserted events

