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

Something the person did: an order, a basket left

event

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. Greets, then says three days later what is coming.

2. 2

   The abandoned basket

   Trigger: your shop reports cart.abandoned. An hour later, what they left, with its link; again the next day — unless they bought in between.

3. 3

   The birthday

   Trigger: their birthday field. One e-mail on the day, in their time zone.

4. 4

   After a purchase

   Trigger: your shop reports order. A week later, how did it go?

Drafts in the language of the list: read them, put your words in, start.

Each step says what share of those who entered reached it, and an e-mail says how many left, were opened, were clicked — by people, not by machines. Where the line shortens is where they leave.