Events
event list · triggers · webhooks in · cart.updated · order.placed · cart.abandoned · user.signed_up · tracking events
Events from your shop
Section titled “Events from your shop”Sent by the Azimea plugin or app in your shop, or read from the platform. They follow the same contract on every platform.
| Event | What it means | When it happens | Who sends it |
|---|---|---|---|
cart.updated | The cart changed: a product added, removed or a quantity changed. | On every change to the cart, even before the visitor is known. | Shop plugin or storefront script; Azimea itself for Shopify and MerchantPro |
cart.cleared | The cart was emptied. | When the visitor removes the last product. | Shop plugin or storefront script |
contact.identified | The visitor became known: they typed their email at checkout. | When the email field is filled in. | Shop plugin or storefront script |
order.placed | An order was placed. | When the shop records the order. | Shop plugin or the platform's webhooks |
order.updated | An order's status changed (paid, shipped, cancelled, refunded). | On every status change. | Shop plugin or the platform's webhooks |
customer.upserted | A customer account was created or changed in the shop. | On registration or a profile change. | Shop plugin or the platform's webhooks |
subscriber.created | Someone signed up to the newsletter, with the proof of their consent when they ticked a box. | On a newsletter sign-up (form, popup, checkout box). | Shop plugin, the platform's webhooks or your API |
subscriber.removed | Someone left the shop's own newsletter: marketing to them stops. | When they unsubscribe in the shop. | MerchantPro webhooks or a shop plugin |
contact.erasure_requested | The shop asks for a person's data to be erased (GDPR). | When the shop receives an erasure request. | Shopify's GDPR webhook or a shop plugin |
Events Azimea records
Section titled “Events Azimea records”Azimea’s own facts about a contact, shown on their timeline. Flows start on these.
| Event | What it means | When it happens | Who sends it |
|---|---|---|---|
order.placed | Azimea recorded a new order on the contact's timeline. | When the order arrives, from any source. | Azimea |
order.paid | An order was paid. | When an order reaches the Paid status. | Azimea |
order.cancelled | An order was cancelled. | When an order reaches the Cancelled status. | Azimea |
order.refunded | An order was refunded. | When an order reaches the Refunded status. | Azimea |
cart.abandoned | Azimea's verdict that a cart was left: it starts the abandoned-cart flow. | 30 minutes without change, with products and an address, and no order. | Azimea |
contact.subscribed | A contact became a subscriber: a newsletter or form sign-up starts welcome flows; someone who ticked marketing while creating a shop account starts the flows on new customer accounts. | When a contact's consent becomes Subscribed. | Azimea |
Suggested events from your product
Section titled “Suggested events from your product”Your product can send any event name to POST /events. These are the names the ready-made product flows start on; use
them and those flows work without changes.
| Event | What it means | When it happens | Who sends it |
|---|---|---|---|
user.signed_up | A person created an account in your product. | Right after sign-up. | Your product, through POST /events |
user.activated | A person reached the moment your product counts as "they got it" (their first project, first payment, first report). | When you decide activation happened. | Your product, through POST /events |
trial.ending | A person's trial ends soon. | A few days before the end of the trial, as you choose. | Your product, through POST /events |
subscription.started | A person started paying. | On the first successful payment. | Your product, through POST /events |