Exit conditions and goals

A run normally works through its steps until the end of its branch. Exit conditions and goals change that as soon as the contact does something, wherever the run is, including while it waits: an exit condition ends the run, and a goal moves it forward to the goal step.

Goal steps, and exit conditions, goals and waits on workspace or custom events, are included with Pro, Business and Custom plans. On Pay as you go, saving an automation that adds them returns 403 with "error": "plan_required". Automations that already have them keep them after a downgrade.

Exit conditions

Exit conditions are on the automation’s Settings tab, under Exit conditions. When one matches for a contact, their run in this automation is canceled at once: waiting steps are dropped and no more steps run. The run’s status becomes Canceled, with the note Met an exit condition.

There are two kinds:

• When something happens: an event for the contact, chosen like a trigger, with its options. For example Custom event purchase sent with the Events API (events from the tracking script don’t end runs), Tag added customer, Contact updated with Field that changed Purchased, or Unsubscribed. Custom events and orders take an optional filter, for example only orders with total greater than 50.
• When the contact matches: rules on the contact, as in a Condition step. For example “has tag customer” or “Purchased is true”. These are checked every time the contact changes and before every step, so a contact who already qualifies never gets the next email, even if the change came in a moment earlier.

Exit conditions apply to runs already in progress as soon as you save them, keep working while the automation is paused, and need a Contact automation. An automation can have up to 20.

The Emailit team can also exit on Placed an order and Abandoned a cart from Commerce, on Removed from segment for a tracked segment, and use Segment and Purchases rules in conditions. These are in alpha, like Commerce and segments. Contacts who leave a segment because someone edited its rules don’t exit.

Leave when removed from the audience

For automations started by Added to audience, turn on Leave when removed or unsubscribed from the audience that started the run. A contact’s run is then canceled when they’re removed from that audience, unsubscribe from it, or unsubscribe from all marketing email, for example when your shop removes them from an “Abandoned carts” audience after a purchase. The run’s note is Left the audience. A Remove from audience or Subscribe / unsubscribe step of the run itself doesn’t end that run.

Contact automations created in the dashboard have this turned on. Automations created with the API have it off unless you set exit_on_audience_removal: true. Without it, a run continues after the contact leaves; marketing emails still skip contacts who unsubscribed.

With the API

Set settings.exit_conditions when you create or update the automation. Each entry is an event matcher (the trigger key in event and its options) or { "condition": { "match", "rules" } }:

{
  "settings": {
    "exit_on_audience_removal": true,
    "exit_conditions": [
      { "event": "contact.on_event", "event_name": "purchase" },
      { "event": "contact.on_event", "event_name": "c:order.completed", "filter": { "match": "all", "rules": [{ "field": "properties.total", "operator": "greater_than", "value": 50 }] } },
      { "event": "contact.tag_added", "tag": "customer" },
      { "condition": { "match": "all", "rules": [{ "field": "custom_fields.purchased", "operator": "is_true" }] } }
    ]
  }
}

Goals

A Goal step marks a point the run should get to as soon as the contact meets the goal. When the contact meets it, their run jumps there from wherever it is: the steps and waits in between are skipped (marked skipped in the run), the goal is marked reached, and the run continues with the steps after the goal. Goals are included with Pro, Business and Custom plans.

For example, a trial sequence sends a tip every three days, with a goal “Tag added paid” near the end followed by a thank-you email. A contact who upgrades on day 2 skips the remaining tips and gets the thank-you right away.

A run reaches each goal at most once, and goals inside a random split branch don’t return to the split afterwards. Like exit conditions, goals keep working while the automation is paused.

With the API, a goal is a goal step: { "event": { "event": "contact.tag_added", "tag": "paid" }, "if_not_met": "continue" } or { "condition": { ... } }.

Move contacts between automations

• Start automation starts another automation for the contact. Turn on Move the contact to end the current run afterwards.
• Remove from automations cancels the contact’s runs in other automations you pick, or in Every other automation.

For example, when your shop tags buyers customer through the API, a “Buyers” automation started by that tag can remove them from every promotional automation and move them to onboarding:

{
  "steps": [
    { "key": "bought", "type": "trigger", "trigger": "contact.tag_added", "config": { "tag": "customer" } },
    { "key": "leave", "type": "action", "action": "exit_automation", "config": { "all": true } },
    { "key": "onboard", "type": "action", "action": "run_automation", "config": { "automation_id": "aut_3Mv8Xq2nKp5Lt", "exit_current": true } }
  ],
  "connections": [
    { "from": "bought", "to": "leave", "branch": "default" },
    { "from": "leave", "to": "onboard", "branch": "default" }
  ]
}

Related