Journey Builder has three Journey types, and the transactional one is the only way to legally email someone who has unsubscribed. Here's when we pick each in production engagements.
When a client asks us to "set up an email flow in SFMC," the first fork in the road is Journey type. Journey Builder offers three, and picking the wrong one means either overbuilding or - worse - breaking compliance by sending to unsubscribed contacts.
Here's how we pick, and the cases where the choice is non-obvious.
When someone says "Journey Builder," this is almost always what they mean. Multi-Step Journey has the full canvas: waits, decision/engagement/random splits, exit criteria, goal tracking, the works.
Use for:
90% of Journeys we build end up as Multi-Step. It's the swiss army knife of Journey Builder.
Single Send Journey sends one email to an audience, no waits, no splits. That's it.
Why use it instead of Automation Studio's Send Email activity?
Use for:
If the only thing you need is the email going out on a schedule, Automation Studio is fine. If the client will ask "how did that send perform?" and expect to click into a dashboard, Single Send Journey is the quieter option.
This is the type most teams miss. Transactional Send Journey is a special mode designed for system-triggered, legally-required emails: order confirmations, password resets, OTP codes, shipping notifications.
Three important differences from Multi-Step Journey:
Use for:
The mistake we see: teams build order confirmations as Multi-Step Journeys. It works for subscribed customers. The moment someone has unsubscribed from marketing, their order confirmation never arrives, and support starts getting tickets about "why didn't I get a receipt?" The fix is a Transactional Send Journey, which the legal team actually wants there anyway.
If you're mixing marketing content into what should be a transactional email, you're breaking the promise of the transactional exemption - and you can lose that privilege if flagged. Transactional means "receipt, notification, service." Anything with "buy more" language belongs in a Multi-Step Journey, even if it shares a trigger with a transactional.
Journey type is decided before any dragging happens on the canvas. Get it right on day one - the rebuilds if you're wrong are painful, especially for transactional flows where the migration touches API triggers, compliance flags, and the sender profile. When scoping a new Journey, the first question we ask the client is which of the three categories the flow lives in. The drag-and-drop comes after.
Building an SFMC stack from scratch? Our Salesforce team sets up Journey types, sender profiles, and API triggers on production engagements. Get in touch ->
See our full platform services for the stack we cover.
SalesforceNov 19, 2025
A Marketing Cloud developer doesn't need to read the GDPR text. They need to know which questions to raise at discovery and which fields to build in SFMC. Here's the short version.
Read More
SalesforceJul 30, 2025
Marketing intern forgets to remove [DRAFT] from the subject line. 500,000 production emails go out with '[DRAFT] This Week's Exclusive Offers'. Subject/Preheader Validation blocks this with five minutes of configuration.
Read More
SalesforceMar 11, 2026
Beyond the basic sendable DE, SFMC has several DE types with specific behaviors. Knowing when to use each saves architecture rebuilds later. Here's the reference sheet we use.
Read More
SalesforceOct 29, 2025
Journey Builder gives you five split types, and picking the wrong one is how you end up with a flow that runs clean but reports the wrong numbers. Here's how we tell them apart on production engagements.
Read MoreWe build trust by delivering what we promise – the first time and every time!
We'd love to hear your vision. Our IT experts will reach out to you during business hours to discuss making it happen.
"Collaborate, Elevate, Celebrate where Associates - Create Project Excellence"
SapotaCorp beyond the IT industry standard, we are
