Documentation overview

Journeys

Build it once. It keeps running. A journey is an automation your AI CMO runs over time – a welcome series, a win-back play, a weekly content engine – built on a visual canvas and executed for you, person by person.

Creating a journey

Journeys in the sidebar gives you three ways in:

  • Describe it. Type what you want – "every Monday, research AI news and draft a LinkedIn post" – and press Draft it. The AI builds the journey and opens it on the canvas for review. Nothing is saved until you save it.
  • Templates. A gallery of ready-made journeys in two groups – Get customers (lead welcome, launch amplifier, SEO content engine, ad creative refresh and more) and Keep customers (win-back for at-risk, reactivation, loyalty boost, referral ask). One click opens the template on the canvas.
  • Blank canvas. New journey starts you from a trigger and an empty canvas.

Every journey belongs to one brand profile and works in that brand's voice – the builder header shows which.

Or ask for one in Chat – see Journeys built in chat.

Journeys built in chat

Ask in Chat the way you'd brief a colleague – "a three-email win-back for customers who haven't bought in 90 days", "a welcome series when someone signs up". Chat builds the journey as a draft and opens it on the canvas beside the conversation, the same steps you see in Journeys. Nothing is live: a journey built in chat starts only when you press Start in Journeys.

The emails are written as it is built. Each email step is written while the journey is being built, saved to your Library under the journey's campaign, and shown on its step – a miniature, the subject and the pre-header. That email is what the step sends, word for word; each person still gets their own details in the fields it uses (their first name, their company). Click a step on the canvas to read its email at full size, at desktop or phone width.

Some emails are written each time the journey runs instead, and their step says Written when it runs, with the brief it is written from:

  • an email that comes after a step producing something it uses – the code from a Grant promo step, research from Research topic – because it needs what that step produces for each run;
  • every email in a Repeat journey, so each run sends something new.

Chat's reply says which emails were written and which wait for a run, and why.

Who it goes to. A journey for a group of people – a win-back, an offer to a segment – starts with an Audience trigger marked as needing setup. Choose the audience in Journeys before you press Start.

How the written emails go out follows your brand's own approval setting – Brand → Messaging → Review & approval, Require approval before a marketing send:

  • On: each step holds every run until someone approves it – find them in Activity under Needs you.
  • Off: the email goes out when a run reaches its step.

Service journeys – receipts, confirmations, account notices – are never held. Emails written each time the journey runs are always held for approval, whatever the setting: nobody has read them before they would go out.

Credits: building the journey costs 3 credits, and each email written for it costs what writing that email in chat costs (12 credits). An email written each time the journey runs is charged on every run.

The building blocks

Drag steps from the left rail. The main groups:

  • Triggers – a journey can carry several, each with its own audience scope and its own on/off switch: Audience (a segment or picked people enter when you publish, or on a schedule – see An audience on a schedule), Manual (you run it yourself), Repeat (a schedule – hourly, daily, weekdays, weekly on one or several days, monthly), On event (a person enters when something happens – a form submitted on a specific landing page, a specific tracked link clicked, a lifecycle stage change, or one of your own events).
  • Messaging: Email, SMS, Push, WhatsApp, Website message – covered below. Record an event sends nothing: it adds an event to the person's data for your other journeys to use (see Record an event).
  • Flow: Wait (pause for a while), Wait for event (hold the person until they do something), Wait until time (hold them until a date and time), Condition (branch yes/no – on rules built like an audience, on one event, on a profile attribute, "did they open the email?", "did they click a tracked link?" and more), Did they…?, In audience?, Day & time (weekends one way, weekdays the other), A/B split, Notify me (an alert to you with the run's results), and Goal (the finish line). Note and Section annotate the canvas for whoever opens it next – they are never executed.
  • And the rest of the toolkit: social posts (LinkedIn, X and X threads, Facebook, Instagram), blog and SEO articles, images, ad drafts, web research, page scraping, tracked links, webhooks to call your own systems, and reusing content from your library. Content steps work draft-first – the AI writes, you approve.

Event triggers

The On event trigger enrolls a person the moment something happens. The list is your brand's own: every event your site, your systems or the platform sends for the brand appears in it, with how many have arrived so far and the stored name underneath (so it can be matched against your tracking plan). Everyone who can open the brand sees the same list.

  • Activity – someone submits a landing-page form, clicks a tracked link, completes a survey, or is active on your website (daily)
  • Website – Signed in on your site, Signed up on your site (new to the brand) and Signed in or signed up on your site (either one) (see Signed in and signed up); someone submits a form on your site; or converts – once per conversion type your site has sent, so a sign-up your site reports as a conversion (Signed up) is its own line too
  • Website behaviour – someone views a page, scrolls down a page (or 25 / 50 / 75 / 90 / 100 % of it), leaves a page with how far they scrolled, clicks or sees a button, sees a page element, shows exit intent, rage-clicks, starts filling a form, or abandons one. These arrive about ten minutes after the visit, and only for visitors who were identified at the time (which needs their marketing consent)
  • Lifecycle stage changes – becomes a New customer, a Potential loyalist, Loyal, a Champion, At Risk, Can't Lose, goes Hibernating or becomes Lost. A save play can run itself the day someone starts slipping (how the stages drive lifecycle marketing). Customers who get no stored stage never fire one: anyone on a Blocks everything blacklist, erased, or with a support conversation marked sensitive and not cleared, and the other cases listed under "Who gets no stored stage or score" in Customer Intelligence
  • Support – contacts support, has their issue resolved, turns unhappy in a conversation, or rates one
  • Website messages – sees or clicks one of your website messages
  • Consent – gives or withdraws e-mail, SMS, WhatsApp, push or website consent: E-mail consent given, SMS consent withdrawn and the rest, recorded from 10 Nov 2026 on. A journey that asks people for their consent can start on it, wait for it or measure it as its goal. On the trigger, Which changes start it is People's own choices only unless you choose Every change, imports and database pulls too: an import or a database pull can record consent for thousands of people at once. Consent events never count toward the brand's event volume
  • Recorded by journeys – an event one of your journeys recorded on the person with a Record an event step (see Record an event)
  • Everything else your brand holds – the e-mails you sent and what happened to them, purchases, and any event your systems push or your site sends (registered in Data → Events), under its own name

The event is chosen from the same searchable list the audience builder uses, with the same names. + Refine narrows it on any field the event carries – the channel a signup came through, the form, the page, how far someone scrolled, and the event's own amount, currency, channel, source and campaign: where channel is any of affiliate, paid_social, where amount is more than 100. The field list, the comparisons and the value suggestions are the audience builder's (see Building an audience). A filter row with a field but no value is marked, and the journey will not publish until it is finished or removed – an unfinished filter would otherwise let every event of that kind through.

Event triggers are polled continuously; a matching person is enrolled and their run starts within about a minute of the event reaching us. An event that reaches us late (a batch from your systems, the daily website activity) still starts the journey, as long as it happened in the last 48 hours – an import of older history never does.

The same list and the same filters are offered by Wait for event ("until this person …" – only an event that passes the filters wakes the person), by the Goal ("count a conversion when the person …"), and by the If / else check did they do something? (one event) (the Did they…? step in the palette): yes when the person viewed the bonus page at least once since they entered this journey, or in the last 7 days, narrowed by the event's fields. So a journey that starts on a login can branch on whether the person also viewed a page, deposited or abandoned a form. Website behaviour arrives about ten minutes after the visit – put a Wait before the check when it should see what they just did.

The If / else a profile attribute check reads any field of the person's contact record, their customer record or how they registered with the brand – the same list the audience builder offers, with the same comparisons. It works however the person entered the journey.

How someone registered fills in after the registration, not at it: the registration record is written about 10 minutes after the sign-up, and its registration source and channel are set when it settles, seven days after. Until then those fields are empty and the check takes No. So a welcome that branches on them right after a sign-up needs a Wait before the check – 10 minutes for the affiliate ID, tag or promo code, 7 days for the source or channel. The step says so when you choose such a field, and plainly when the journey starts at the sign-up and nothing before the step waits long enough; a run's log says "registration not settled yet" when that is why it took No.

Signed in and signed up

Your site names its visitor to us when they sign in and when they sign up, and it does not say which. We tell the two apart by whether your brand already had the person at that moment, so every event list has three lines in its Website group:

  • Signed in on your site – your site named someone your brand already has a contact for, by that e-mail or customer ID.
  • Signed up on your site (new to the brand) – your site named someone your brand had no contact for. It is the first time we hear of them.
  • Signed in or signed up on your site (either one) – both. A journey built on this line before 11 Nov 2026 keeps working as it was.

Each is one event per sign-in or sign-up, recorded when your site newly names the visitor, not on every page they open while signed in (see Identified: a sign-in or a sign-up). Pick any of the three in the On event trigger, Wait for event, Did they…?, the Goal and the audience builder. A welcome that should reach only new people starts on Signed up on your site (new to the brand); a message for returning customers starts on Signed in on your site.

What to know before you build on them:

  • "New to the brand" is about your contacts, not about the accounts on your site. Someone who registered on your site before your brand's data reached The AI CMO counts as a sign-up the first time they sign in. Someone already in your contacts, from an import for example, counts as a sign-in when they register on your site.
  • When your site reports the registration itself as a conversion, that conversion has its own line, Signed up. Use that line when the journey must start on the registration and nothing else.
  • An address a visitor types into one of your website messages is neither a sign-in nor a sign-up. It counts only on the either-one line.
  • Events recorded before 11 Nov 2026 do not say which they were, and neither does an event we could not check in time. They count only on the either-one line.

If / else on rules

When one event or one attribute is not enough, the If / else check do they match rules? (events, profile, audiences) takes a whole rule, built in the audience builder: signed up since they entered this journey, and industry is agency or ecommerce, except people who approved a campaign in the last 30 days. Everything the builder offers works here – groups, any event with its filters, counts, sequences, totals of a value, profile fields, membership of an audience – plus one window of its own: since they entered this journey.

The panel shows the rule as lettered lines with their sizes, the rule in words, and Match right now – how many people would take the Yes path if they reached the step at this moment (a since they entered this journey window counts everything they did, because nobody has entered yet). Edit rules opens the full builder; Use these rules brings them back to the step. A did they do something? or a profile attribute check can grow into a rule with Combine with more conditions – the check becomes condition A.

The rule is checked for each person when they reach the step: Yes if they match, No if they do not or we cannot tell who they are. In Activity, a run shows which lettered conditions held. A journey with an unfinished rule will not publish.

Day & time – weekends one way, weekdays the other

The Day & time step (check what day and time is it?) sends people down one of two paths depending on when they reach it.

  • On these days – pick the days, Monday to Sunday. Saturday and Sunday are picked to start.
  • At these times – All day, or Between two times. A range that crosses midnight belongs to the day it starts on: Friday 22:00 to 02:00 includes 01:00 on Saturday.
  • Whose clock – Each person's own time reads the time in the person's timezone when we know it, otherwise in the journey's send-hours timezone, otherwise UTC. A run with no person is read the same way without the person's own timezone.
  • Name the paths – what the two ways out are called on the canvas (When it matches and Any other time). The names follow the days you pick – Saturday and Sunday read Weekend / Weekdays – until you type your own.

The step is checked the moment a person reaches it: put it right after the trigger to split on when they entered, or after a Wait to split on when they get there.

An audience on a schedule

An Audience trigger has When they enter: Once, when published (everyone in the audience enters when you publish, and publishing again picks up people added since) or On a schedule. On a schedule uses the same schedule settings as Repeat – every few hours, every day at one or several times, weekdays, chosen days of the week, or a day of the month. Each time it runs, the audience is refreshed and the people in it at that moment enter – blacklisted people never do, and every message they get is checked as usual (see Who enters – and who never will). Nobody enters at publish; the first entry is the first scheduled time, and Run now does one run the same way.

People still in the journey are never entered twice. Whether people who finished come back at the next run is the journey's re-entry setting in Settings – the trigger panel says which way it is set. Turn re-entry on when the same people should go through again.

Put together with Day & time:

  • Audience – VIP players, on a schedule, every day at 10:00
  • Day & time – Saturday and Sunday
    • Weekend → the weekend offer e-mail
    • Weekdays → the weekday reminder text

Starting a journey from your own systems (API)

Your backend can start a published journey for one person directly – "order shipped", "deposit made", "support ticket resolved" – without waiting for any poll:

http
POST https://theaicmo.com/api/journeys/trigger
Authorization: Bearer <your API key>

{
  "journey_id": "<the journey's id>",
  "email": "customer@example.com",
  "event": { "order_number": "1042", "amount": 89.90 },
  "idempotency_key": "order-1042-shipped"
}
  • Create the key in Settings → API keys and tick Trigger journeys. The journey's own brand is used, so you do not need to send client_id. A key can start any journey on a brand its owner may edit – including journeys a teammate built. An organization key can start journeys only on brands of its organization. A journey with no brand belongs to the organization its builder's work is billed to; an organization key starts it only when that is the key's organization, and otherwise answers 404 journey_not_found.
  • Name the person by email, external_id or both. Someone who is not a contact yet is created on the journey's brand. When you send both, they must be the same person – if they point at two different contacts, nothing is enrolled and the answer is 409 identity_conflict.
  • Someone the call creates starts with no e-mail marketing consent ("Not granted"): a Service journey reaches them, a Marketing journey sends them no e-mail. When your own system holds their consent, send "consent": { "email": true } and it is recorded on their consent history. For someone already in your contacts it counts only when this "Not granted" is all that stops marketing to them – it never overrides an unsubscribe or a withdrawn consent – and leaving it out, or sending false, never changes anyone.
  • event properties (up to 20 – text, numbers or true/false) reach your message copy as {{ event.order_number }}, which fills with 1042. Text longer than 500 characters is cut.
  • idempotency_key makes retries safe: the same key returns the same run instead of starting a second one – even when two retries arrive at the same moment. The key names the run, so use a new one for each person. A person already inside the journey is never double-enrolled either.
  • Every door still applies: people on a blocking suppression list are refused (and the refusal is recorded), unsubscribed contacts can enter service journeys but not marketing ones, and the journey's own re-entry rule decides whether someone can go through twice. A person erased on request is never re-created; if that cannot be checked at the moment, nothing is enrolled and the answer says to retry.
  • The run starts within about a minute; the reply carries its id so you can find it in the journey's Activity.

Personal tokens – any message, their data

Every message step (email, SMS, push, website message) fills in per-recipient tokens at send time. Write {{p.first_name}} and each person gets their own name; any contact field works – {{p.company}}, {{p.phone}}, {{p.external_id}} – and so does any column you've ever imported: a CSV with a loyalty_tier column makes {{p.loyalty_tier}} available in every message with no setup.

The warehouse adds what no contact field holds – each person's actual behavior, computed fresh at send time: {{p.total_spent}}, {{p.order_count}}, {{p.last_purchase_date}} (as "12 Jul 2026"), and {{p.days_since_last_purchase}}. "You've placed 14 orders with us – the last on 12 Jul 2026" writes itself.

Properties on your events work the same way – anything you see in the Data hub. If your site sends a deposit event with method: "card", then {{p.method}} fills with that person's most recent value. The lookup only runs for tokens nothing else answered, so it costs nothing on ordinary sends.

Add a fallback with a pipe – {{p.first_name|there}} writes "there" when the field is empty, so "Hi ," never reaches a customer. A token that doesn't exist renders as nothing.

Your brand's own details fill in the same way, from Settings → Brand: {{brand.name}}, {{brand.website}}, {{brand.logo_url}} and {{brand.primary_color}} – in an e-mail's subject and body, an SMS, a push, a website message's headline, text and button, and a webhook body (see Personalizing your messages).

On top of the field tokens you can define audience-valued tokens under Audience → Personalization → Messages: one token name, a different value per audience – {{p.offer}} can be "20% off" for VIPs and "10% off" for everyone else, with an Everyone value as the fallback. If a defined token shares a name with a contact field, the defined token wins. The Messages tab lists every token your data already supports, click-to-copy.

When a message waits for approval

A message that is already written when you publish the journey goes out without a second approval. Publishing the journey is its approval. A brand that requires approval is the exception, below.

  • A message you typed into the step (Content: I write it) and an item you picked from your Library (from my library) go out to each person who reaches the step. The step's settings do not offer save as a draft for review, and its card reads Publishes automatically.
  • A message the AI writes for each person (the AI writes it) is new on every run, so nobody has read it before it would go out. Set to save as a draft for review, the journey pauses at the step for each run and the card reads Draft for review: approve it in Activity (filter Needs you) and the journey publishes it. Set to publish automatically, it goes out as written.
  • A step that uses the text of the step before it (from the step before) keeps the choice as well, because what arrives may be written for each person. Set to save as a draft for review, it is held for each run.
  • When a picked Library item is no longer there, the step writes a fresh text for each person instead, and the run's Activity says so. A step set to save as a draft for review holds that text for review.

A brand that requires approval keeps the choice. With Require approval before a marketing send switched on (Brand → Messaging → Review & approval), the settings of these steps still offer save as a draft for review, and a step set to it reads Draft for review. A typed message or a Library item in such a step is held for every run until someone approves it in Activity.

A held step sends nothing before its approval. A Library item you edit while a run waits goes out as it reads when you approve.

Service journeys are never held, and a Test run sends nothing.

The Email step

The Email step is AI-written: you give it a prompt ("Monthly product update – friendly, one CTA to the changelog"), choose Campaign (one message, one CTA) or Newsletter (a multi-section issue), and the journey drafts it for your approval before anything sends. An email from your Library can be used as it is instead, or you can write it yourself (I write it); either goes out to each person who reaches the step, without an approval for each person – see When a message waits for approval. A journey built in chat arrives with its emails already written – see Journeys built in chat.

On the canvas each Email step shows what it sends: an email from your Library as a miniature with its subject and pre-header, an AI-written one as the brief it is written from. The pre-header is the line inboxes show after the subject; it goes out at the top of the email, personalised like the subject, and an email whose design already carries one keeps its own.

  • Send to: by default, the person moving through the journey. You can instead broadcast to a segment – each run emails the whole audience, however large it is. It goes out in batches of 500 and picks up where it left off on the next run, so nobody is silently left out. Unsubscribed people are always skipped.
  • Test send: send just that email to any address, subject prefixed [Test].
  • Goal: under Goal, Success is A purchase, A conversion, A form submitted or A specific event…, Within 1 to 30 days of getting it (7 to start). It only measures: who gets the email and when stay as they are. See Success is on a message step.
  • Setup required once: email sending is configured per brand profile in settings – either The AI CMO sends for you on a verified domain, or use your own provider (Resend, Postmark, SendGrid, or any SMTP). Sending stays off until a verification email arrives, so a misconfigured domain can never send to customers. A domain can live on one Resend account only: if the managed setup says your domain is already registered on another Resend account – usually your own – choose use your own provider and connect with your Resend key instead.

The SMS step

SMS defaults to word-for-word: with "I write it" selected, the text you type is the message that sends – no rewriting, which is what most teams want for compliance-sensitive texts. Switch the Content selector to "the AI writes it from my brief" and the step writes the message fresh from your brief each run instead. Texts written in SMS Studio are in your library – choose from my library on the step ("or write it in SMS Studio" opens the studio). It needs SMS sending connected first (Twilio, Telnyx, Vonage, MessageBird, sms.to, or ProfiSMS), contacts need a phone number, and opted-out numbers are always skipped. STOP replies opt people out automatically.

Under the text, the step counts it the way it goes out – filled in for a sample person, never the placeholders themselves – for a text you write and a text from your library alike. For a text you write, the AI writes or that comes from the step before, Accents chooses between sending without accents (160 characters a part) and keeping them (one accented letter makes the text Unicode, 70 a part); each option shows its parts. Left on the brand's default, a Czech or Slovak brand sends without accents and every other brand as written. A text from your library carries its own choice, set on the text in SMS Studio: the step shows it with a link to change it there, so one text never has two settings. A library text passed on by a From-library step keeps its choice too. A test from the step is filled in for the sample person and sent with the same choice. Like any change to a step, a new choice applies to a live journey once you publish the changes.

The SMS step can carry a measured goal: under Goal, Success is A purchase, A conversion, A form submitted or A specific event…, Within 1 to 30 days of getting it (7 to start). It only measures: who gets the text and when stay as they are. See Success is on a message step.

Connecting a provider takes its credentials and a sender. For ProfiSMS the sender ID is optional – leave it blank and texts go out from your account's default – and when set it must be either a phone number in international form or up to 11 letters, digits, dots or dashes, registered with ProfiSMS; anything else is refused when you save rather than quietly altered on the way out. Verification checks the login against your account without sending anything, or sends one real test text if you give it a number. A postpaid ProfiSMS account verifies at any balance; a prepaid one needs credit.

The Push step

Sends a push notification to the person in the journey. Three routes, any of which works alone:

  • Your mobile app, directly – ship @aicmo/react-native and upload your Firebase service account on the Website SDK page; notifications go straight through your own Firebase project, no third party.
  • Your website – visitors who enabled notifications through the Website SDK get the push in their browser (real phone notifications on Android, iPhone once your site is on their home screen).
  • OneSignal – if your app already runs OneSignal, connect it (Connections → search "OneSignal") and the step notifies through it, matched by the customer id your app registers.

Like SMS, the message defaults to word-for-word ("I write it"), with an AI mode that writes from your brief. You set the title, where a tap lands, and which routes to use – every route available, mobile app only, or browsers only – and the panel previews the notification as the phone will show it. People on your blacklist or self-exclusion lists are never sent – the block happens before anything leaves, on every route.

The Push step can carry a measured goal: under Goal, Success is A purchase, A conversion, A form submitted or A specific event…, Within 1 to 30 days of getting it (7 to start). It only measures: who gets the push and when stay as they are. See Success is on a message step.

The WhatsApp step

Messages the person on WhatsApp through your own WhatsApp Business account (Meta Cloud API). Connect it once under Connections → WhatsApp sending: phone number ID, WhatsApp Business Account ID, and a permanent access token – all three from Meta Business Suite → WhatsApp → API Setup. We verify against Meta before saving.

One honest rule, and it's Meta's, not ours: marketing messages must use pre-approved templates. The node lists your account's approved templates; you pick one, fill its {{1}}, {{2}} variables, and the panel previews the message as the chat will show it. Create and manage templates in WhatsApp Manager – once Meta approves them, they appear in the picker.

Send to the person in the run or broadcast to an audience (contacts need phone numbers; a large audience goes out in batches of 500 and continues on the next run until everyone has been reached). Opt-outs are shared with SMS – a STOP on either channel stops both – and blacklist / self-exclusion rules apply before anything is sent. An optional weekly frequency cap works like the SMS one.

The WhatsApp step can carry a measured goal: under Goal, Success is A purchase, A conversion, A form submitted or A specific event…, Within 1 to 30 days of getting it (7 to start). It only measures: who gets the message and when stay as they are. See Success is on a message step.

The Website message step

Shows a message on your own site to the person in the journey – a corner card, top banner, or modal, rendered by the Website SDK. You control when it appears (immediately, after a delay, at scroll depth, on exit intent, when they arrive from this journey's email, or after an event), how long it stays live, whether a dismissal is final, and what a click does: under After a click, Don't show it again (the choice unless you change it) or Keep showing it once a day. A click is a click on its button, its code copied, an address left in its box, or a click on it in the inbox. It holds in the browser where it happened.

Under Only if you can add conditions, and all of them must hold: The URL has a parameter, A cookie is set and The visitor is signed in. The last one shows the message only on pages where your site has named the visitor (it called identify() there, or your identity cookie is set). A message written for one person is then not shown, counted or marked as read after they sign out, as a popup or in the inbox, and it appears as soon as your site names them again. Use it when your site does not tell us about sign-outs, that is, when it does not call AICMO.reset() on logout. It is off unless you add it.

The step keeps one message for each person, live for the days you set, counted from the last time they passed the step. When a person passes the step again, that same message is brought up to date and is live again, and no second one is ever added. What they did with it in their browser still holds, also when its words have changed: closed stays closed for as long as If dismissed says, and clicked stays clicked where After a click closes it. When a journey has more than one Website message step, a person's messages from its other steps end when a later run writes one for them, so nobody is shown the message of a branch they have left. A run with no person (the journey run for everyone) keeps one message for every visitor the same way. A person your site cannot find, with no e-mail and no customer ID, is skipped. A service message is different: each run writes its own, and none is ended by another.

While the journey is paused, none of its website messages is shown, as a popup or in the inbox, and nothing is counted. Start it again with the people held and the ones that have not ended show again; start it fresh and they end (see Starting a paused journey again). Switching off a trigger alone does not pause the journey: people already in it carry on, and so do their messages.

Each website message can carry a measured goal: under Goal, Success is A purchase, A conversion, A form submitted or A specific event…, Within 1 to 30 days of seeing it (7 to start). It is counted from your data warehouse: each person who saw the message and then reached the goal within those days counts once, and the revenue of a purchase or a conversion is summed. The node shows its performance right on the canvas: shown, clicked, converted, and revenue.

A specific event… counts one event of your brand, chosen from the same list as the journey's Goal: your purchases first, then the events your data warehouse holds for the brand, those your journeys record among them. Refine narrows it on the event's fields, as on an event trigger. The results carry the event's own name and how many of the people who saw the message had it. The journey does not publish until the event is picked and every filter is finished.

On your site now

Once the journey is published, each Website message step says how many people have its message on your site right now, on the step's card on the canvas and first in the step's settings. While the journey is paused, the step says their messages are held back: none of them is shown.

See who lists them, newest first, with when each person last passed the step and when their message ends. To find one person, type their exact e-mail or customer ID.

End it now ends the step's message for everyone who has it now, and End on a row of the list ends it for that one person. An ended message is not shown again until the person passes the step again, when the step brings it back. A message for every visitor shows again the next time the journey runs the step. A change you publish reaches each person the next time they pass the step.

When people still have a message from a step you have taken out of the journey, the canvas says how many at the top, with See who and End them.

Success is on a message step

Every message step – Email, SMS, Push, WhatsApp and Website message – has the same Goal: Success is No goal, A purchase, A conversion, A form submitted or A specific event…, and Within 1 to 30 days (7 to start). A specific event… is chosen from the same list as the journey's Goal: your purchases first, then the events your data warehouse holds for the brand, the consent changes (E-mail consent given, SMS consent withdrawn and the rest) and the events your journeys record (Recorded by journeys) among them. Refine narrows it on the event's fields, as on an event trigger. The journey does not publish until the event is picked and every filter is finished. A goal only measures: it never changes who gets a message or when.

On an Email, SMS, Push or WhatsApp step the counts are for the version you published last. Of the people the step sent its message to since that publish, it counts those who then had the goal within the days after their own send, each person once; a person the step reached again is counted after each of their sends, and still once. The revenue of a purchase or a conversion is summed. The step's panel shows it under the goal, with the event's own name:

Since the last publish: sent to 4,500 people · E-mail consent given: 120 of 4,500

A person is found by the address the message went to, the person in the run, and your brand's contact that holds that address, so a customer e-mailed at their address counts for an event filed under their customer ID. A message the provider may have taken without a clear answer (Not confirmed) counts as sent, as it does everywhere else. A text or WhatsApp message to a phone number that no single contact of the brand holds, or a message to an address that names nobody in your data, is counted as sent, and the panel says those people cannot be matched to their events. When a step has sent to very many people, the panel reads the newest messages for as long as it waits, starts its line with Of the newest messages read since the last publish, and says how far it got. When the messages cannot be read just now, it says so instead of a count. Change the goal and publish again, and the counts start from that publish; until a journey is published with the goal, the panel says counting starts then.

Record an event

The Record an event step (in Messaging: Adds an event to the person's data) sends the person nothing. Its output is an event on the person, which your other journeys and your audiences use like any event your brand holds.

  • Record – choose an event your journeys already record (Recorded by your journeys), or type a new name and pick Record "…". A name the platform keeps for its own events, or one that reads as a purchase or a payment, cannot be picked, and the step says why. A name your website or your imported data already uses is refused when you publish.
  • With – optional properties, up to 20: Add a property, then a name and a value. A value can use the same {{…}} fields as messages, filled in for each person.

The event is recorded on the person in the run once each time they pass the step. Once the journey is saved, it is listed under Recorded by journeys for the On event trigger, Wait for event, Did they…?, If / else rules, the audience builder, the Goal and a message step's Success is. On the person's timeline under Customers it shows with the journey that recorded it: VIP offer made · recorded by the journey "VIP welcome".

Each event the step records counts toward the brand's event volume, like any other event.

Loops. A journey never starts from an event it recorded itself, and the step warns you when it records the event its own journey starts on. When journeys start on each other's recorded events, a chain stops at 3 journeys, counting the one that recorded first: journey A records, B starts on it and records, C starts on that and records, and a fourth journey does not start. The event is still recorded; only the start is left out.

A test run, a run held out by Uplift, and a run with no known person (an e-mail or an ID) record nothing, and the run's Activity says so. Someone whose data was erased never gets one.

Who enters – and who never will

  • Audience triggers enroll everyone in the segment when you publish; publishing again picks up people added since. Each person goes through a journey once.
  • Enroll people in the Activity panel lets you hand-pick contacts into a running journey.
  • Blacklisted people are dropped at the door – they never enroll, and the block is logged. Unsubscribed and opted-out people are skipped at every send step. Frequency caps skip anyone already at their limit – the weekly cap in your sending settings (at most N marketing messages per person per 7 days, across all journeys), and a cross-channel budget on the brand profile if you set one. Service messages are never capped.

Marketing or Service

Under Settings, a journey is either Marketing or Service.

Marketing is the default and everything above applies to it.

Service is for messages the customer needs rather than wants – order confirmations, password resets, payment and account notices. A service journey reaches people who unsubscribed from marketing, so it works differently on purpose:

  • People can re-enter every time it fires. A customer's second order needs its confirmation as much as their first.
  • Send hours and the frequency cap don't apply, and no unsubscribe link is added.
  • No control group is held back, because a "control" for a receipt is a customer who never got one.
  • It can only start from an event or be run by hand, and each step reaches the one person the event is about. Audience triggers, repeat schedules and sending a step to a whole segment are all refused when you publish.

Hard blocks still stop it: bounced addresses, spam complaints, and anyone on a blacklist set to "Blocks everything". Service email also needs its own verified sending domain – see Unsubscribes, opt-outs, and the blacklist.

Running and watching

  • Save keeps a draft. Start publishes; once live, edits go out with Publish changes.
  • Test rehearses the published version without publishing anything. Run now publishes what's on the canvas and runs it.
  • The live canvas shows the running step pulsing, with per-step counts of who's here and who has passed.
  • The Activity panel is the full ledger – every run, step by step: drafts waiting for your approval, sends, branches taken, skips with their reasons, and completions. Filter by Needs you to see only the runs waiting on your approval.

Delivery status

Under every email and SMS step of a run, the Activity panel shows what the provider reported after the send:

  • Delivered with the time, once the provider confirms it. For SMS this is the carrier's delivery receipt; for email it is the provider's delivered event. An email that was opened or clicked says so too.
  • Bounced (email) or Not delivered (SMS) with the provider's reason – an expired message, a wrong number, a dead mailbox. A bounced address is also put on the suppression list, so it is not tried again.
  • Delayed when the mailbox rejected the message temporarily and the provider keeps trying.
  • Sent – no delivery receipt yet right after the send, until the provider reports. Most receipts arrive within a minute; some carriers take hours.

The same lines appear on the person's timeline under Customers, so you can answer "did they get it?" for one person without opening the journey. Receipts need the provider's webhook set up under Connect: ProfiSMS receipts are requested with every message we send and need no setup – and every few minutes we also ask ProfiSMS about any SMS still without a verdict, so a lost receipt (or a message sent before receipts were switched on) still gets its status. Twilio, Resend, Postmark and SendGrid need the webhook URL from the sending card pasted into the provider. Email sent through Resend – your own account or our managed sending – is also asked about every few minutes while it has no verdict, so a status arrives even without the webhook.

Starting a paused journey again

A paused journey runs again only when you start it with Start again in the builder header. It asks how, and shows how many people were in the middle of the journey when it was paused and how many of its website messages are held back. Neither choice is made for you.

  • Start fresh: the people held leave the journey and its website messages end. Then the journey starts, and new people enter from now on. An audience journey that is not on a schedule also enrolls everyone in its audience who has not been in it yet.
  • Continue with the people held: they pick up where they stopped. Anyone whose wait ended during the pause moves to the next step right away, and the journey's website messages show on your site again. Each person finishes the version they entered on.

When nobody is held and nothing from the journey is on your site, Start again starts it at once.

A start runs the published version. Publishing changes while the journey is paused keeps it paused, and the next start runs that version. When you have saved changes you have not published, Start again says so and offers Publish changes first. Run now does not run a paused journey: it opens the same choice.

Whether a person who left may enter the journey again follows its re-entry setting, which a start never resets. A journey that takes each person once does not take them again.

A big journey takes a while to start. Keep the window open until it finishes. If Start fresh stops before it finishes, the journey stays paused and Start fresh again carries on; Continue finishes by itself. A journey paused until a date continues by itself with the people held on that day.

Versions – every publish is kept

Every time you publish, the journey is frozen as a numbered version, and runs already in flight keep following the version they started on – your edits never disturb them. Click the Live · v3 (or Paused) chip in the builder header to see the history. Open any version to put it on the canvas; if it's the one you want back, Save or Publish it – that makes it the new current version, so the history stays an honest record of what actually ran, and when.

Copying and pasting steps

Any step can be copied, a trigger too: one step, or several with the connections between them. The keys are ⌘ on a Mac and Ctrl elsewhere.

  • Select several steps with ⌘-click, Shift-click, or a Shift-drag box around them.
  • Copy with ⌘C, with Copy step (or Copy N steps) on a step's right-click menu, or with Copy this step at the foot of the step's panel.
  • Paste with ⌘V, or right-click an empty spot on the canvas and choose Paste N steps here to put them there.

Pasted steps are new steps with their own settings, so changing a copy never changes the original. In the same journey they land beside the originals; anywhere else, in the middle of what you are looking at. Undo on the confirmation takes them away again, and like any edit they are kept when you save (on a live journey, when you Publish changes). A pasted trigger is one more way in, as one added from the palette would be.

Paste into the same journey, another journey of the brand, or a journey of another brand you can open. The copy waits in the app's open tabs in your browser and is never stored on your computer: close every tab and it is gone. Into another brand, the first brand's own picks are cleared and named in the confirmation, as when a whole journey moves (see Moving a journey between brands).

Moving a journey between brands

Build in a test brand, then move it to production – or hand a proven journey to a second brand:

  • Copy to another brand (Settings → Copy & export) duplicates the journey into any other business profile on your account. The copy lands as an unpublished draft – nothing runs until you publish it there.
  • Export as a file downloads the journey; Import (top of the Journeys page) brings it back in – into another brand, or another account entirely.

Either way, the steps, prompts, schedules, send hours and layout all travel. Brand-specific picks do not: audiences, hand-picked people, promos, tracked links, surveys, landing pages and WhatsApp templates belong to the brand they were chosen in, so those choices are cleared and listed for you – the copy shows a "needs setup" badge exactly where a new pick is needed. Re-select them in the target brand before publishing. A webhook's authorization is cleared too; its address is kept, so check it is the target brand's.

An On event trigger, a Wait for event or a Did they…? whose tracked link, survey, landing page or entry audience was cleared would otherwise take every event of its kind. It reads "needs setup" until you pick one of this brand's or choose "any" on purpose. Until then a wait or a Did they…? stops the journey from publishing, and a trigger is switched off; turned on before its pick is made, it stops publishing too. A journey that has never been published does not publish while every entry is switched off.

Measuring what a journey earns

Turn on the Uplift holdout and a random slice of enrollments (5, 10, or 20%) is deliberately left unmessaged as a control group. Comparing their revenue against everyone else's tells you what the journey actually caused – not just what happened near it.

A read-only role

A person whose role on a brand is read-only (a Viewer, see Teams, roles and access) can open the brand's journeys and see their steps, their numbers and their website messages. They cannot save, publish, run, pause, start again, send a test, add people, end website messages or delete. Where the actions would be, the screen says "Your role on this brand is read-only."