Record an event, or a batch
Writes down what a person did: an order, a basket left behind, a page seen. Events start automations (trigger The person does something), feed segments, and an event named order with a value is credited as revenue to the e-mail that earned it.
Send one event as the body, or up to 1,000 under events. In a batch each row gets its own answer, in the order it came: one bad row does not cost the others. The person does not have to be a subscriber yet: the event is kept under their address and joins their profile when they subscribe.
Authorizations
An API token. The "read" ability: GET routes only. "read + write": every route.
Headers
Replay a write safely: the same key gives back the first answer for 24 hours (header Idempotent-Replay: true).
255Body
- Option 1
- Option 2
Yours to choose. order is counted as revenue; cart.abandoned starts the ready-made basket journey.
100^[A-Za-z0-9 _.:-]+$"cart.abandoned"
Whatever describes it. Available in the e-mails of the automation it starts, as {{ event.… }}.
In the smallest unit: 1250 is 12.50 €. Requires currency.
x >= 03Now, when absent. At most one day ahead.
Your own identifier — an order number. The same reference twice is recorded once.
255