Marketing automation turns repeatable customer interactions into workflows: a contact qualifies, a defined event starts the process, and the system applies messages or other actions until the person reaches a goal or an exit condition. A customer journey is the experience those steps create across time and channels. To build one well, define the outcome and audience first, then choose the trigger, map only useful branches, set suppression and exit rules, review the whole path, and measure the business result.
What marketing automation does—and what a customer journey means
Marketing automation is software-assisted execution of actions based on contact events, stored properties, or other conditions. A workflow commonly combines an enrollment trigger, eligibility rules, timed steps, messages or operational actions, conditional branches, and stop or redirect conditions.
As an Amazon Associate I earn from qualifying purchases.
A customer journey is the experience you design across those steps. It might begin when someone subscribes, continue with a welcome email, pause for several days, and then take a different path depending on whether the person made a purchase. A journey can span email, SMS, data updates, and operational tasks, but the available channels and builder features depend on the platform and plan.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11The terms are not perfectly interchangeable across vendors. “Journey” may describe the planning concept, a specific visual builder, or a product feature. “Workflow” can likewise refer to a particular automation tool. Treat the customer journey as the experience to plan, then confirm that your chosen platform can implement the triggers, actions, conditions, channels, and exits that experience needs.
#1 Best Overall
How do I create a marketing automation flow?
Plan the logic before building it in a platform. This makes it easier to spot vague eligibility rules, unnecessary messages, and contacts who could remain enrolled after they have already completed the goal.
- Write down one outcome. Choose a result such as welcoming a new subscriber, helping a first-time customer get started, nurturing a qualified lead, or re-engaging an inactive customer. Define what completion looks like in an observable way—for example, a completed onboarding milestone or a purchase recorded by a connected store.
- Define the audience and eligibility. Specify who should enter and who should not. Identify the relevant list, record properties, event, or other data the platform will use. Do not enroll a contact merely because the software allows it; make the rule match the purpose and the person’s eligibility to receive each type of communication.
- Choose one clear enrollment trigger. Decide which event or condition starts the flow: a new subscription, a purchase, a change in lead status, or another supported activity. Mailchimp describes a trigger as the activity or event that adds a contact to a flow. Confirm how the platform treats contacts who already meet the condition when the flow is activated, and whether later repeat events can enroll them again.
- Map the steps. Add only the waits, messages, data updates, and operational actions that move the contact toward the stated outcome. Mark every decision point and write down the condition that sends a contact along each branch. Use a branch when different behavior or status genuinely calls for a different next step.
- Set exits and suppression rules. Decide when a contact has completed the goal, should leave early, or must stop receiving messages. Account for unsubscribes, suppression lists, ineligibility, and other stop conditions. An exit is part of the workflow design, not a cleanup task to postpone until after launch.
- Review the entire experience before activation. Check eligibility, message content, personalization, delays, and every branch—including what happens when a condition is not met. Use the platform’s available preview and publishing controls, but have a person review the actual customer experience before turning it on.
- Confirm measurement prerequisites, activate, and monitor. Check that the necessary tracking and integrations are enabled before interpreting reports. After activation, review delivery and engagement alongside the business outcome, and revise the flow when evidence shows that a step is not serving its purpose.
In Mailchimp’s flow builder, documented step types include conditional and percentage splits, trigger waits, delays, email and SMS messages, webhooks, tagging, and contact updates. Which steps are available can depend on the plan. These are product-specific capabilities, not a universal checklist for every automation platform.
How to map a journey without overbuilding it
A useful map makes enrollment, decisions, and exits legible to someone other than its original creator. Start with the contact’s first qualifying moment and draw forward only as far as the goal requires.
Use a decision table before adding branches
| Journey moment | Question to answer | Example for a new-customer onboarding flow |
|---|---|---|
| Entry | What event or condition enrolls an eligible person? | A recorded first purchase, provided the customer is eligible for the planned communications. |
| First action | What is the smallest useful next step? | Send a welcome or getting-started message. |
| Wait | How much time should pass before the next check or action? | Allow time for the customer to try the product before sending a follow-up. |
| Branch | Which meaningful behavior or status changes the next step? | Continue onboarding differently if a defined setup milestone has or has not been recorded. |
| Exit | What event completes the goal or stops the flow? | Stop the onboarding sequence once its completion condition is recorded, or when the contact becomes ineligible. |
The example is a design pattern, not a prescribed schedule or claim that a particular message will produce a result. Set timing and conditions according to the customer task, the data your systems actually capture, and the communication permissions you have.
Keep branches tied to actionable differences
A branch earns its place when the next action should change based on reliable information—for instance, a status property, a recorded purchase, or an interaction the platform can identify. Avoid branching on data you do not maintain or behavior that the reporting setup cannot observe. Every extra path increases the number of cases to review, test, and maintain.
Make exits explicit
Common exit logic includes goal completion, a change that makes the contact ineligible, an opt-out or other suppression condition, or a transition to a separate process. Check whether each exit is evaluated throughout enrollment or only at specific steps; this behavior is platform-specific. If the platform cannot enforce a required stop condition at the moment it matters, do not assume that drawing the condition on a map will make it work.
How to automate common customer journeys
These patterns show how to translate a goal into workflow logic. The exact trigger names, event data, actions, and channels depend on your platform and connected systems.
Welcome a new subscriber
- Goal: introduce the service or brand and guide a new subscriber to a useful next step.
- Entry: a qualifying subscription event, subject to the subscriber’s eligibility and applicable consent requirements.
- Path: send the welcome message, wait an appropriate interval, and use a relevant condition only if it changes what the person should receive next.
- Exit: stop the welcome sequence when its defined goal is complete, the contact opts out, or another suppression condition applies.
- Measure: check delivery and engagement, then evaluate the intended next step if it can be tracked reliably.
Nurture a qualified lead
- Goal: provide relevant information or route a qualified contact toward an agreed next action.
- Entry: a clear qualification event or status change, not simply the existence of a contact record.
- Path: use waits and conditional steps only where the recorded status or behavior justifies a different follow-up. Include operational actions if the workflow needs to update contact data or hand work to another process.
- Exit: stop or redirect the contact when the qualification status changes, the target action occurs, or the person becomes ineligible.
- Measure: relate message activity to the intended business outcome without treating engagement alone as proof that the automation caused it.
Help a new customer get started
- Goal: guide the customer toward a defined onboarding milestone.
- Entry: a first-purchase or account event that your connected systems record reliably.
- Path: send useful instructions, allow time for action, and branch only on milestones or statuses the system can observe.
- Exit: leave the flow when onboarding is complete, the customer enters a more relevant process, or a suppression rule applies.
- Measure: compare delivery and engagement with the onboarding milestone. If purchase or revenue reporting matters, confirm that the store connection and required tracking are active.
Re-engage a dormant customer or subscriber
- Goal: invite a meaningful next interaction or identify contacts who should no longer receive the sequence.
- Entry: a defined period or status indicating inactivity, based on data the platform can use.
- Path: send an appropriate message and use a recorded response or renewed activity to route the contact.
- Exit: stop the sequence when the person re-engages, opts out, or meets another stop condition.
- Measure: distinguish message engagement from the business outcome that justifies the campaign.
How to measure whether a flow is working
Choose measurements before launch so the team knows which system must capture each event. A dashboard can report activity without proving that the workflow caused the outcome; treat platform attribution as evidence to interpret, not a guarantee of causal lift.
Measure across three levels
- Execution: did eligible contacts enter, did messages deliver, and did exits or suppression conditions behave as intended?
- Engagement: what click, open, unsubscribe, or abuse-report activity does the platform record? Mailchimp’s flow reports include delivery and engagement measures, but open and click figures require the relevant tracking to be enabled.
- Business outcome: did the target action—such as a recorded order, revenue event, or onboarding milestone—occur? Mailchimp’s ecommerce measures depend on a connected store, so confirm that connection before relying on order or revenue reporting.
Do not interpret missing activity as a customer response until you have checked that the measurement feature was enabled and the required data source was connected. Review the relevant platform report documentation for the exact metric definitions and prerequisites before using figures in a business decision.
Set a review cadence and a change record
Review a flow after activation and whenever its audience, content, data sources, or goal changes. Record what changed and why, particularly when an edit alters who enters, what messages they receive, or when they leave. This makes it easier to distinguish a workflow change from a change in audience, tracking, or connected systems.
How to choose an automation platform for a journey
There is no universally best platform established by the product documentation covered here. Compare a candidate against the journey you need to run, not its total feature count.
Recommended Free Tools
| Decision area | Questions to resolve | Why it matters |
|---|---|---|
| Audience and data model | Which records, lists, properties, and events can enroll or segment people? Can the needed data be maintained accurately? | A trigger or branch is only useful if the system can identify the right person and condition. |
| Workflow flexibility | Can it support the required triggers, waits, branches, actions, and exits? | A flow that cannot reliably stop or redirect contacts may not support the intended journey. |
| Channels and integrations | Which channels and business systems can participate, and what connection or setup is required? | Channel support and connected data vary by tool, plan, and configuration. |
| Measurement | Which delivery, engagement, conversion, or revenue measures are available, and what tracking or integrations must be enabled? | Reports depend on prerequisites; a displayed metric is not automatically a causal measurement. |
| Access and operating cost | Which plan includes each required capability? What usage limits, permissions, and ongoing work apply? | Feature availability can depend on plan tier, and workflows need people to review and maintain them. |
| Governance | How does the system handle consent, suppression, data access, testing, and change history? | Governance determines whether the journey can be operated responsibly as its audience and content change. |
Mailchimp flows
Mailchimp’s documentation describes building a flow by choosing an audience and trigger, then adding rules and actions to the flow map. Documented step types include conditional and percentage splits, trigger waits, delays, email and SMS messages, webhooks, tags, and contact updates. The documentation notes that some capabilities depend on plan tier, so the feature list should not be read as a promise that every Mailchimp plan includes every step. Flow reporting includes delivery and engagement measures; open and click tracking must be enabled for those statistics to populate, and ecommerce measures require a connected store.
HubSpot automation and the Journeys sunset
HubSpot documentation describes workflows that enroll records through criteria and execute actions across business processes. Its separate Journeys feature has a time-sensitive status: HubSpot’s journey help page, last updated October 2, 2026, says HubSpot Journeys will be sunset on November 30, 2026, and recommends campaign automation in Marketing Studio as the replacement. The same page says Marketing Studio automation requires opting into its beta. Do not plan a new long-lived process around HubSpot Journeys without accounting for that stated end date; the sunset applies to that feature, not to workflow automation generally.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Consent, suppression, and responsible operation
For US commercial email, the Federal Trade Commission’s CAN-SPAM guidance covers requirements including truthful header information, non-deceptive subject lines, a valid physical postal address, and honoring opt-out requests. The FTC guide is US-specific; a sender must determine which laws apply to its own business, recipients, and jurisdictions. This guide does not establish non-US legal requirements.
Separate legal obligations from vendor controls. HubSpot’s automated email documentation advises sending marketing emails only when explicit consent has been received and explains that unsubscribed or otherwise ineligible contacts are not sent through its marketing email workflow action. That is HubSpot product guidance; it is not a substitute for determining the law that applies to a campaign. In every platform, confirm how opt-outs and suppression lists affect enrollment and message actions, and do not use an automation flow to bypass a contact’s communication status.
Pre-launch review checklist
- The goal is defined in a way the team can observe.
- The trigger enrolls only the intended audience, and eligibility rules are explicit.
- Each branch uses a condition supported by available, maintained data.
- Completion, early exit, opt-out, and other suppression conditions are accounted for.
- Content, personalization, timing, and each branch have been reviewed by a person.
- Required tracking and integrations are active before reports are used to judge outcomes.
- The chosen product feature and plan support the required steps for the period the workflow needs to operate.
Frequently Asked Questions
Is a customer journey the same thing as a workflow?
Not necessarily. A journey is the designed customer experience; a workflow is one way a platform may implement its rules and actions. Vendors use these terms differently, so check whether a product’s “journey” label describes a planning concept or a specific feature.
Can a marketing automation flow include operational actions, not just messages?
Yes, where the platform supports them. Documented examples in Mailchimp include webhooks, tagging, and contact updates in addition to email and SMS actions. Other platforms and plans may offer different action types.
Will opens and clicks tell me whether automation increased sales?
No. Opens and clicks describe tracked engagement, not by themselves a causal sales effect. To assess a sales outcome, ensure the relevant store connection and tracking are in place, then interpret reported orders or revenue in context.
Can I keep using HubSpot Journeys after November 30, 2026?
HubSpot’s help page, last updated October 2, 2026, states that Journeys will be sunset on November 30, 2026. It points to campaign automation in Marketing Studio as a replacement and says that automation requires opting into its beta.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
