Skip to content
Letterhead Letterhead Letterhead Help Center
Admin Tools

Branch a simple series automation

Edit in CMS

You can add conditional branches to a Simple Series automation to send subscribers down different paths — a Yes path and a No path — based on a condition you choose. Each reader’s journey then adapts to their actual behavior or profile, and you can nest branches inside one another to build decision trees of any depth.

  1. Open the automation for editing and add a conditional branch where you want the journey to split.
  2. Choose a criteria type: Audience (profile details and tags — see Split an automation by subscriber attributes) or Engagement (opens or clicks on your newsletters).
  3. Configure the paths for subscribers who do and don’t meet the condition.
  4. Save and activate.

Choose Opens or Clicks, then decide which emails count: your most recently published newsletters, or specific issues you pick. Set a minimum — and optionally a maximum — number of opens or clicks for a subscriber to take the Yes path.

When matching by clicks, you can narrow the condition to particular links instead of any click. Letterhead gathers every unique link from the newsletters in scope, deduped and ready to pick, so a follow-up path fires only for readers who clicked a particular article or call to action — leave the field empty to match a click on any link. The same narrowing works on click-based triggers.

Add another branch inside either path of an existing one, at any depth, to respond to combinations of conditions — engagement first, then subscription tier, for example. The workflow canvas lays nested branches out as a readable tree, so even deeply nested logic stays easy to follow and edit.

  • Send a re-engagement path to subscribers who haven’t opened recent issues
  • Offer a promotion to readers who clicked a specific product link
  • Trigger a follow-up sequence when someone clicks a particular product or service link
  • Tag readers who click through to a specific article or topic
  • Send reminders only to readers who clicked an event announcement
  • Run separate follow-up paths for different calls to action in the same newsletter
  • Build a progressive qualification flow — check multiple attributes in sequence, like engagement level first, then subscription tier

Send a test email from any step before activating. Once the automation runs, each branch displays how many subscribers took that path — see Monitor a running automation — so you can confirm the tree splits your audience the way you intended.

For everything else the Automations area can do, see Working in Automations.

Still can’t find what you need? Contact support.