Start with an audience event
Choose how contacts qualify to enter, then confirm the source data and contact identity are correct.
Journey Builder Basics: Plan Your First SFMC Journey
Learn how a Salesforce Marketing Cloud Journey Builder journey brings together an entry source, activities, decision logic, and clear contact-exit rules. Follow a practical welcome-series example from audience selection through testing.
What is Journey Builder?
Journey Builder is the Salesforce Marketing Cloud Engagement tool for creating and managing automated, multi-step communications. A contact enters from a configured source, follows the path defined by activities and rules, and exits when the journey reaches its end or an applicable exit condition is met.
Design the contact experience
Arrange messages, waits, and decision points in an order that matches the customer need.
Define safe outcomes
Decide when a person may re-enter, when they should exit, and how you will validate each path.
Before you build: Journey Builder capabilities and available activities can depend on your Marketing Cloud edition, installed features, channel configuration, permissions, and account setup. Confirm details in your own tenant.
The core Journey Builder building blocks
Think of a journey as a controlled sequence: define who can enter, determine what happens next, and decide how to handle contacts who no longer qualify.
01 · ENTRY
Entry source and audience
An entry source determines how contacts enter a journey. Depending on the use case and enabled features, it may be based on an audience such as a data extension, an event, or another supported source. Validate required fields, contact keys, eligibility, and the intended entry cadence before activation.
02 · ACTIVITIES
Messages and actions
Activities represent what the journey does. Common examples include sending an email, waiting for a period, evaluating a decision, or performing a configured channel or automation action. Availability varies by account and setup.
03 · BRANCHING
Decision splits
A decision split routes contacts based on data and criteria available to the configured activity. Define the conditions, the matching data source, and a clear default path for contacts who do not meet a branch rule.
04 · TIMING
Waits and schedules
Wait activities control timing between steps. Select timing that makes sense for the customer and business process, and consider how schedule settings and time zones affect when communications are delivered.
05 · LIFECYCLE
Re-entry, goals, and exits
Choose whether and when a contact can enter again. Where available and appropriate, configure goals and exit criteria to stop contacts from receiving messages after they convert, become ineligible, or meet another defined condition.
06 · RELEASE
Validation and activation
Review the canvas, entry source, audience, content, links, branches, timing, and exit behavior. Use the available validation and test tools in your account, and get the required approvals before activating a production journey.
Example: a simple welcome journey
Imagine a subscriber becomes eligible for a welcome series. This outline is a planning example; implement and test the entry source, content, data, and timings in your own SFMC account.
Entry sourceEligible new subscriber
Welcome emailConfirm signup and set expectations
WaitAllow time for engagement
DecisionEvaluate the chosen criterion
Meets the rule
Continue to the relevant follow-up activity, or exit if the contact has already completed the journey’s objective.
Does not meet the rule
Use the intended alternative path, such as a different follow-up or a respectful end to the series.
A Journey Builder decision split is not automatically the same as an email open or click. Use only engagement signals and tracking data supported by the configured activity and account, and account for privacy-related measurement limitations.
Plan the journey before opening the canvas
- Outcome: State the customer outcome and business goal in one sentence.
- Eligibility: Define who can enter, required data, exclusions, and consent or communication preferences.
- Identity: Confirm the contact key and relationships required by the selected entry source.
- Paths: Sketch each decision branch and its fallback before adding activities.
- Timing: Choose waits and delivery windows that fit the customer experience and operational constraints.
- Exit and re-entry: Prevent duplicate or irrelevant messages by defining when contacts leave and when they may return.
- Measurement: Decide how success will be evaluated and which reliable data source supports that measure.
Journey testing checklist
Before activation, walk through the journey as different contacts—not just the ideal case.
- Confirm the entry source contains the fields and contact identity expected by the journey.
- Test records that qualify, do not qualify, have missing values, and match each decision branch.
- Verify message content, personalization fallbacks, links, and channel configuration.
- Review wait timing, send windows, time-zone assumptions, and any schedule restrictions.
- Check re-entry and exit behavior, including what happens after a conversion or changed preference.
- Confirm the intended version, approvals, monitoring owner, and rollback or pause procedure.
Practice safely: The SFMCpulse Journey Builder Playground is an educational simulation and does not connect to or publish journeys in a Salesforce Marketing Cloud account.
Common beginner mistakes
Building before checking the entry data
Missing attributes, incorrect keys, or unexpected eligibility can put contacts on the wrong path. Validate representative entry records first.
Leaving branch outcomes unclear
Every decision needs an intentional outcome, including contacts that do not match any explicit rule. Document and test the fallback path.
Forgetting re-entry and exit behavior
Without deliberate lifecycle rules, a contact may repeat a message or continue after the intended goal. Decide these rules during planning.
Activating without testing realistic cases
Test missing data, alternate branches, timing, and content—not only the happy path—and confirm your organization’s approval process.
Journey Builder basics FAQs
What is an entry source in Journey Builder?
An entry source defines how contacts become eligible to enter a journey. The sources available depend on your account and enabled features; validate the data and contact identity required for the source you choose.
What is the difference between a decision split and an engagement split?
A decision split evaluates configured data and criteria to route a contact. An engagement split is intended to branch based on tracked engagement with a prior message or activity, where supported. Their data availability and evaluation behavior differ, so test the selected activity in your account.
Can a contact enter the same journey more than once?
Re-entry behavior depends on the journey’s configured entry settings and contact lifecycle. Choose the appropriate option for the use case and verify how it behaves before activation.
Does the SFMCpulse playground publish a real journey?
No. The playground is a browser-based educational simulation. It does not connect to Salesforce Marketing Cloud, access customer data, or activate journeys.
Ready to practice?
Explore a guided Journey Builder simulation, then continue to advanced architecture topics.