This list is not exhaustive, and partners are not required to send every event. AIQ will use whatever events are available, and Flow options will adjust automatically based on what each integration supports.
PII Note: For all events, send PII when you have it (email, phone, customer ID). If not, AIQ will still accept anonymous events and attempt identity resolution when the customer later identifies.
Order Events (POS or Ecom)
order_created — early lifecycle, pre-purchase triggers
order_completed — core purchase automations
Including product name, category, SKU, Brand, Price, Discount, etc.
order_fulfilled — post-pickup/delivery messaging
order_canceled — suppress/send issue Flows
order_refunded — retention or service Flows
Order Events (Ecom)
checkout_started — checkout abandonment
cart_updated — cart intent logic
cart_abandoned — abandoned cart Flows
Behavior Events (Ecom)
active_on_site — engagement scoring
We use tab is open + cursor position change within last 10 min
viewed_product — browse abandonment
viewed_brand — brand Flows
viewed_category — category Flows
added_to_cart — pre-abandonment logic
removed_from_cart — friction detection
started_product_review — allows follow-up nudges
completed_product_review — thank-you messages or reward incentives
Customer Events (POS or Ecom)
customer_created — welcome/onboarding Flows
customer_updated — identity + compliance
customer_optin_status_changed — opt-ins/outs reflected instantly
Inventory Events (POS or Ecom)
back_in_stock — item is available again
price_drop — item price decreased
new_product_added — new item listed for sale
low_inventory — item stock is running low
Other
customer_checked_in — in-store Flows
customer_checked_out — post-visit messaging
customer_assigned_to_budtender — budtender-specific flows or recs