Journeys that know when to stop

A subscription

subscribed

A tag added

tag_added

A tag removed

tag_removed

A date of yours: birthday, renewal

date_attribute

An API call

webhook

By hand

manual

Wait (minutes, months, or until Tuesday at 9), wait for an event, send, tag, untag, branch on a condition, split A/B, subscribe to another list, unsubscribe, call a webhook, stop.

Every step counts who is there and who is through.

“Give them three days to open.” Two paths: they did, they did not. Open, click, buy.

Three goals: a tag received, a purchase, a link clicked. Whoever reaches it leaves the journey, counted as a success. Whoever unsubscribes, or receives the tag you choose, leaves too.

The editor is a column read from top to bottom, with two branches under each condition. No arrow gets lost, and last year’s journey can be read again in ten seconds.

1. 1

   The welcome

   Trigger: subscription. Three e-mails, two days apart. Goal: the first purchase.

2. 2

   The birthday

   Trigger: a date attribute. One e-mail at nine, in their time zone.

3. 3

   The wake-up, then the clean goodbye

   A segment of people gone quiet. One e-mail, seven days to open it; if not, unsubscribe them.

Recipes to build, not templates that ship.