Triggers

Triggers initiate automated Journeys. Once triggers and configuration options are set, Journeys will run in perpetuity once activated.

Cart Abandon

This trigger will fire when a session with cart items is abandoned.

Step by Step Guide: Build a cart abandonment journey.

This trigger will fire when a session with product views is abandoned.

Step by Step Guide: Build a browse abandonment journey.

This trigger will fire on a specified number of purchases. For example, you could start a campaign for loyal customers on their 5th conversion.

This trigger will fire on every conversion, regardless of which number it is.

This trigger will fire after a specified number of days since a conversion occurred.

Step by Step Guide: Build a win back journey.

This trigger will fire before/after a specified number of days relative to a specific date, like a customer's birthday.

This trigger will fire when a customer is added to a specified list. Multiple lists can be selected as triggers.

Step by Step Guide: Build a new subscriber welcome series.

This trigger will fire when a customer is removed from a specified List. Multiple lists can be selected as trigger lists.

This trigger will fire when a customer is added to a specified Segment. Multiple segments can be selected as trigger segments.

This trigger will fire when a customer is removed from a specified Segment. Multiple segments can be selected as trigger segments.

This trigger will fire when a tag is applied to a customer profile.

This trigger will fire when a tag is removed from a customer profile.

This trigger will fire when a qualifying price change occurs.

This trigger will fire on demand when the Journey is activated. On-Demand triggered Journeys are useful when you're attempting to:

Send a series of broadcast-style emails with logic in the Journey (e.g. send email #2 only if email #1 was opened and clicked)
Make modifications to a large number of customers at once (e.g. mass unsubscribe, set inactivity, apply tags, etc)

This trigger will fire when an inbound webhook event is processed.