Every automation starts with a trigger. This is the complete list, including what each trigger needs to work.
Subscriber triggers
- New subscriber: fires when someone joins a list or segment (choose which, or any). The most common trigger for welcome series.
- Subscriber data changed: fires when a field on the subscriber changes.
- Date based: fires on a date field, for example a birthday.
Website triggers
These require the website tracking script on your site, and only fire for identified subscribers.
- Website visit: fires on a page visit.
- Product viewed: fires on product views. Optional filters: product ID, product category (matches the category sent by the tracking event, case-insensitive) and a minimum number of views within a counting window (1 to 90 days, default 7). With minimum views set to 4, the flow only starts once the same product has been viewed 4 times inside the window. Combine with the profile filter "placed order - zero times - last 7 days" to reach browsers who have not bought.
- Custom event: fires on events you send yourself from your site or backend. Event properties become merge tags in the flow's emails.
E-commerce triggers
These require a connected store (Shopify or the WooCommerce plugin) under Integrations.
- Cart abandoned: fires when a checkout has been untouched for the abandonment time you set - any number of hours from 1 to 336 (14 days), default 24. If re-entry or a profile filter blocks enrollment, the checkout is retried on a later run rather than dropped. A purchase marks the cart converted (email matching ignores capitalization), which stops the flow. Checkouts with no items, and checkouts last touched more than 7 days ago, never start the flow - so turning on an abandoned cart flow does not mail every old cart in your store's history.
- Order created: fires when an order is placed.
- Order fulfilled: fires when an order ships.
- Order cancelled: fires when an order is cancelled.
- Customer created: fires when the store creates a customer.
- Back in stock: fires when a product a subscriber asked about is back in stock. A request stays pending and retries if the subscriber cannot be enrolled yet.
Things to know
- There is no "tag added" trigger; use profile filters on tags instead
- E-commerce event data (order number, cart total, product name) is available as merge tags in the flow's emails
- Store webhook enrollments that fail are retried for 48 hours