Knowledge base
Customer journeys and orchestration
A campaign is one message. A journey is the automated, multi-step path a customer travels, with waiting, branching, and sends along the way. This is the orchestration layer where a marketer actually works.
7 min read · Updated June 28, 2026
Campaign versus journey
These two get used interchangeably and should not be. A campaign is a single send: one email, one push. A journey is the orchestrated sequence of logic and multiple messages over time. In Iterable specifically the relationship is concrete: each message step inside a journey is itself a campaign, so a journey is a coordinated set of campaigns plus the timing and branching between them. A campaign can also stand alone, such as a one-time blast.
The building blocks
Every journey builder, including Iterable Studio, is a visual canvas of steps. The names vary by vendor, but the shape is always trigger, wait, branch, act, exit:
- Start: how a user enters, for example when an event occurs, an API call fires, or they join a list or segment.
- Wait: a time delay (pause for a set duration) or a hold until something happens (wait for an action or a profile change).
- Branch: split users down different paths based on their attributes or behavior, often a simple yes or no condition.
- Act: send a message on a channel, update the user profile, or push the user to an external system.
- Exit: the rules for how and when a user leaves the journey.
Vocabulary note
Older Iterable material calls these "Workflows." The current product calls them "Journeys," built in a canvas called "Studio." Same idea, newer name.
Want to see it move? The interactive journey visualizer renders two sample journeys as a live node graph: press play to watch a customer travel the trigger, wait, branch, and send steps, then flip the branch condition and watch them reroute.
Who enters, and when
Two send styles cover most of marketing. Event-triggered journeys add a user in real time the moment something happens (a purchase, a price drop they were watching). Blast or scheduled sends go to an entire list at once, immediately or on a recurring schedule. Triggered is behavioral and continuous; blast is one-shot to an audience.
Audiences come from segmentation. A static list is a fixed set that changes only when you update it. A dynamic segment recomputes itself from a query, so it is always current but heavier to evaluate. A real-time trigger adds a single user the instant an event lands, with no list scan at all.
Dynamic is not free
Dynamic segments feel effortless but are computationally expensive, especially as journey entry in high-frequency journeys. Platform guidance, including Iterable, is to prefer static lists where possible and filter at entry rather than admitting everyone and filtering later.
Frequently asked questions
What is the difference between a campaign and a journey?
A campaign is one message. A journey is the multi-step orchestration around several messages, with waits and branches. In Iterable, each message step in a journey is a campaign.
When should I use a triggered journey versus a blast?
Use a triggered journey for behavior-driven, per-user moments (onboarding, cart abandonment). Use a blast for a one-time announcement to a whole audience, such as a product launch.
Should I always use dynamic segments?
No. Dynamic segments are powerful but expensive to evaluate. Where the audience is stable, a static list performs better, and filtering at journey entry beats admitting everyone and branching them out later.
Keep reading
Sources
Part of the MarTech and customer engagement field notes on this site. Written by Antoni K Pestka.