Building an automated journey

A journey is a visual automation: a contact enters at a trigger, then flows down a path of steps you design — sending emails, waiting, and branching based on what they do. It is the most powerful way to automate your marketing in Blankitt.

Open Engage → Journeys → New journey to start.

Journey, sequence, or campaign?

• Campaign — one message, sent once. (A newsletter, a launch.)
• Sequence — the same series of emails to everyone, on a timer. (A four-email onboarding drip.)
• Journey — a branching flow where the path depends on what each contact does. (Welcome → wait → if they opened it send the next step, if not send a nudge.)

If your flow never forks, a sequence is simpler. The moment you want "if this, then that", use a journey. See Journeys vs sequences for a full comparison.

Step 1 — Start from a template (or blank)

When you click New journey you can start from a ready-made template:

• New-lead welcome — form submit → welcome email → wait → branch on whether they opened it.
• DMARC Mail Check rescue — a Mail Check submission → results and fix plan → wait → branch on whether they clicked.
• Win-back — manually enrol a cold list → "we miss you" → wait → re-engage or send a final email.

A template drops the whole flow in, ready for you to edit. Or pick Blank journey to build from scratch.

Step 2 — Set the trigger

Every journey starts with one trigger — the thing that puts a contact into the journey. Click the trigger card at the top to choose:

• Submits a form — the contact filled in one of your forms (optionally a specific form).
• Opens an email — they opened any marketing email from you.
• Clicks an email link — they clicked a link in an email.
• Manually enrolled — you add contacts yourself (good for win-back and one-off pushes).

The form, open and click triggers fire automatically — you do nothing once the journey is active.

Step 3 — Add steps

Below the trigger you will see + Add step. Click it to drop in a step. The flow builds top to bottom, exactly the way you read it. The step types:

Step	What it does
Send email	Sends an email. Same editor as campaigns.
Wait	Pauses — either a fixed delay (e.g. two days) or until the contact does something (opens, clicks).
If / else	Branches the flow. Contacts who match your condition take the If yes path; everyone else takes If no.
A/B split	Randomly splits contacts across two or three paths — for testing different follow-ups.
Goal	An exit-when-they-convert check. If the contact matches, they leave the journey having "converted".
Exit	Ends the journey for a contact.

When you add an If / else or A/B split, you get a branch under each path with its own + Add step — so you build each branch in place.

Step 4 — Insert and reorder

You do not have to build it perfectly the first time:

• Insert between steps — every connection between two steps has a small insert step link. Use it to slot a send, wait, or goal into the middle of an existing flow.
• Reorder — Send, Wait and Goal steps have up and down arrows to swap with their neighbour.

Step 5 — Save and activate

• Save validates and compiles the flow. If something is wrong (a dangling branch, an empty email) you get a clear message — fix it and save again.
• Activate turns the journey on. From then on the trigger enrols contacts automatically and we run the steps for you (we check roughly hourly).

Always Save after editing, then Activate. A journey in draft or paused does not run.

Step 6 — Enrol contacts

• Automatically — once active, anyone who hits the trigger (submits the form, opens the email, etc.) enters the journey.
• Manually — on the journey page, pick an audience and click Enrol. Useful for the manual trigger (e.g. win-back a cold segment).

A contact only enters a journey once — they will not be re-enrolled if they trigger it again.

Step 7 — Watch the runs

The Runs section shows every contact in the journey and where they are:

• Active — moving through steps.
• Waiting — paused on a wait step.
• Completed — reached the end.
• Goal met — hit a goal and left as "converted".
• Exited — left early (unsubscribed, or you removed them).

Click Run due now to process anything due immediately instead of waiting for the next hourly check — handy when testing.

A few journey-design rules

• Start simple. A welcome → wait → if-opened branch is more valuable than a twenty-step maze.
• Every branch needs an end. A path that just stops is fine — but make sure each branch does something useful first.
• Mind the volume. Branches multiply sends. Use Goal and Exit steps to let people leave once they have converted.
• Suppression always wins. Anyone who unsubscribes or hard-bounces leaves the journey automatically — you never email a suppressed contact, even mid-journey.