This endpoint creates a new event for a user, persisting the event in Permutive for downstream consumption, such as for segmentation, insights, or routing to a data lake. It validates the event against the schema defined in your workspace, and generates an event ID for the event and optionally enriches the event with geo, ISP, and contextual data.
400 error will be returned. Where Permutive hasn’t received an event type before, it will infer the event’s schema.
Event schemas are viewable in the Permutive Dashboard. To migrate an event schema, please email support.
properties JSON object is limited to 950 KB to ensure platform performance.
If an event exceeds this size limit, it will be rejected and a 400 error will be returned.
This boolean parameter determines whether to enrich the event with geo, ISP, and natural language processing data. By default, this is set to true.
This boolean parameter is used to describe whether the event originated from a Permutive SDK on a client's device, where true denotes the event was from an SDK and false denotes an out-of-SDK event.
By default, this parameter is set to true. If you are interacting with this endpoint directly, rather than through a Permutive SDK, please set this parameter to false.
You must provide either a user_id or a non-empty list aliases of prioritized aliases to specify the user that the event belongs to.
If a user_id is provided, it will be used directly to identify the user, ignoring any aliases provided. If only aliases are provided and none match, a new user ID is generated and the aliases are synced to it.
The name of the event collection this event belongs to. The name is case-insensitive and must only contain characters in [a-zA-Z0-9_].
The Permutive user ID of the user that the event belongs to.
If you do not provide a user ID, you must provide a non-empty list of aliases in the aliases field.
A non-empty list of prioritized aliases that the user is associated with. If you do not provide a list of aliases, you must provide a user ID in the user_id field.
Prioritized aliases allow customers to express which identifiers they consider most reliable or authoritative for resolving user identities.
When multiple aliases are provided, priorities are used to determine the order in which aliases are attempted for resolution to a Permutive user ID, where priority 0 has the highest priority.
1The identifier for the view in which the event is taking place. This is used to group events within a single page or screen view.
The identifier for the session in which the event is taking place. This is used to group events within a user session.
The list of segment codes that the user belonged to at the time of the event.
The list of cohort IDs that the user belonged to at the time of the event.
The properties that belong to this event. These properties must adhere to the specific schema configured for this event collection.
Event created successfully
The Permutive user ID of the user that the tracked event belongs to.
The name of the event collection the tracked event belongs to. The name is case-insensitive and must only contain characters in [a-zA-Z0-9_].
The ISO 8601 timestamp of the event.
The identifier for the view in which the tracked event took place.
The identifier for the session in which the tracked event took place.
The list of segment codes that the user belonged to at the time the event was tracked.
The list of cohort IDs that the user belonged to at the time the event was tracked.
The properties that belong to the tracked event. These properties adhere to the specific schema configured for this event collection.