Send a server-side event
Ingest a single tracking event from your server. The event is transformed into Upstack’s canonical event and processed exactly like a pixel event — identity resolution, enrichment, analytics, and real-time forwarding to your configured destinations.
Use a standard event name (e.g. purchase, add_to_cart) or your own
custom name. Names must match ^[a-zA-Z][a-zA-Z0-9_]*$.
Each call generates a new event id, returned as eventId.
Required scope: events:write.
Authorizations
Your Upstack API key. Starts with upstack_.
The pixel id the request targets.
Body
Event name — a standard event or your own custom name.
100^[a-zA-Z][a-zA-Z0-9_]*$"purchase"
Limited end-user identity. Describes the END USER, not your server.
Convenience for monetary value; folded into the event data.
10Event properties. Standard e-commerce fields are recognized. Additional custom keys are allowed, but each value must be a primitive or a shallow array of primitives (no nested objects).