Common use cases
Flow Events
4 min
docid\ bcrbfcoetju7 goim0yue is currently in internal testing an external beta will be announced shortly in the meantime, we are actively working with integrated partners to identify and ingest events that can be used as flow triggers the following list are possible events that partners could send to aiq to trigger a flow and/or as conditions in splits and audiences 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 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 other customer checked in — in store flows customer checked out — post visit messaging customer assigned to budtender — budtender specific flows or recs