Journey Builder Interview Guide: Real SFMC Use Cases and Business Logic Explained
Abandoned Cart Journey in Salesforce Marketing Cloud – Complete Step-by-Step Breakdown
The journey shown in screenshot is a classic Abandoned Cart Recovery Journey. Its goal is simple:
A customer adds products to their cart but does not complete the purchase. SFMC automatically reminds them and tries to bring them back to complete the order.
This use case is used by almost every major e-commerce brand such as Amazon, Flipkart, Myntra, Nike, Adidas, and Walmart because abandoned carts directly impact revenue.
Business Problem
Imagine this scenario:
Customer Action
John visits your website.
Adds:
iPhone 17 Pro
AirPods Pro
Total Cart Value = $1,500
Leaves the website without purchasing.
Without automation:
Customer forgets
Competitor captures sale
Revenue lost
With SFMC Journey:
Reminder email sent
Follow-up email sent
Special offer sent if needed
Customer returns and purchases
Journey Architecture
Website/App
↓
API Event
↓
Wait 1 Hour
↓
Cart Reminder Email
↓
Wait 1 Day
↓
Decision Split
/ \
Purchased Not Purchased
| |
Exit Offer Email
|
Exit
Step 1: API Event Entry Source
What Happens Here?
Journey starts when website sends cart information to SFMC through API.
The API Event is the trigger.
Real-Life Flow
Customer adds items to cart.
Website backend captures:
{
"ContactKey":"10001",
"Email":"john@gmail.com",
"FirstName":"John",
"CartValue":"1500",
"Products":"iPhone 17 Pro",
"CartID":"ABC123"
}
This payload is sent to SFMC Event API.
SFMC immediately injects customer into Journey.
Why API Event?
Because:
Real-time
No file imports
No automation dependency
Immediate journey entry
Interview Question
Why use API Event instead of Data Extension Entry Source?
Answer:
API Event provides real-time customer entry whereas Data Extension Entry Source depends on scheduled evaluations.
Step 2: Wait Activity (1 Hour)
Why Wait 1 Hour?
Journey intentionally pauses customer for 1 hour.
Reason:
Many customers return naturally.
Example:
John gets distracted.
30 minutes later:
Opens laptop again
Completes purchase
If we send email immediately:
❌ Annoying
Instead:
Wait 1 hour.
Business Logic
Cart Abandoned
↓
Wait 1 Hour
↓
Check Natural Purchase Behaviour
Benefits
Higher customer experience.
Lower email fatigue.
Better engagement.
Step 3: Cart Reminder Email
After waiting 1 hour:
Customer receives first email.
Email Example
Subject
Did you forget something?
Email Content
Hi John,
Looks like you left something behind.
Your cart is waiting:
✔ iPhone 17 Pro
✔ AirPods Pro
Complete your order now.
Personalization Used
AMPscript variables:
%%FirstName%%
%%Products%%
%%CartValue%%
Dynamic Content Example
If Cart Value > $1000
Premium Customer Message
If Cart Value < $100
Budget Purchase Message
Data Source
Usually from:
Journey Data
or
Entry Event Data
Step 4: Wait Activity (1 Day)
After reminder email:
Journey waits for 24 hours.
Why?
Customer needs time.
Example:
Email arrives at:
Monday 10 AM
Customer may purchase:
Monday 8 PM
No need for another email immediately.
Business Reason
Avoid spamming.
Give customer decision window.
Improve sender reputation.
Reduce unsubscribes.
Step 5: Decision Split
This is the most important activity.
Journey now asks:
Did customer purchase?
Purchased Path
Condition:
Purchase_Status = True
OR
OrderID exists
OR
Purchase Event received
If Purchased
Customer moves to:
Exit Journey
Reason:
Goal achieved.
No further communication needed.
Real Example
John:
Added Cart
↓
Received Reminder
↓
Purchased Product
Journey stops.
Why Important?
Without this:
Customer could receive:
10% Discount Offer
AFTER already purchasing.
Customer becomes frustrated.
How Decision Split Checks Purchase
Common Methods:
Method 1
Check Purchase Data Extension
ContactKey EXISTS
Method 2
Salesforce Sales Cloud Object
Order Object
Method 3
API Event
Purchase Confirmation Event
Method 4
Synchronized Data Source
MC Connect synced order data.
Step 6: Not Purchased Path
If customer has NOT purchased:
Journey moves down path.
Logic
Customer Ignored Reminder
Now stronger persuasion is required.
Step 7: Cart Offer Email
This email contains incentive.
Example Subject Lines
Complete your purchase and save 10%
Your cart expires tonight
Limited-time discount waiting for you
Email Content
Hi John,
Still thinking about it?
Complete your order within 24 hours and enjoy:
10% OFF
Use Code:
SAVE10
Advanced Personalization
If Cart Value > $1000
15% Discount
If Cart Value < $100
Free Shipping
AI-Powered Version
Einstein Engagement Scoring can determine:
Best Send Time
Best Offer
Best Subject Line
Step 8: Exit Journey
After offer email:
Customer exits.
Journey completed.
Complete Customer Example
Day 1
10:00 AM
Customer adds shoes to cart.
11:00 AM
Reminder Email Sent.
Day 2
11:00 AM
Decision Split evaluates.
Scenario A
Customer Purchased
Exit Journey
No more emails.
Scenario B
Customer Did Not Purchase
Offer Email Sent
↓
Exit Journey
SFMC Components Used
| Component | Purpose |
|---|---|
| API Event | Journey Entry |
| Contact Builder | Contact Model |
| Journey Builder | Orchestration |
| Email Studio | Emails |
| Data Extension | Cart Data |
| Decision Split | Purchase Check |
| Tracking Data | Reporting |
| AMPscript | Personalization |
How This Is Implemented in Real Projects
Website
Sends cart abandonment data through API.
SFMC
Receives event.
Journey
Sends reminder.
Purchase System
Updates order table.
Decision Split
Checks purchase status.
Offer Email
Sent only if no purchase.
KPIs Monitored
Recovery Rate
Recovered Carts / Total Abandoned Carts
Example:
500 recovered
2000 abandoned
Recovery Rate = 25%
Revenue Recovered
Recovered Orders Value
Example:
$50,000/month
Email Metrics
Open Rate
CTR
Conversion Rate
Revenue Per Email
Unsubscribe Rate
Senior-Level SFMC Interview Discussion
If asked about this journey in a 5–8 year SFMC interview, explain:
"This is a real-time API-triggered abandoned cart journey. Customers enter through an API Event when cart abandonment occurs. A reminder email is sent after a one-hour delay. The journey then waits for 24 hours before evaluating purchase behavior using a Decision Split connected to order or purchase data. Customers who have completed the purchase exit immediately, while non-purchasers receive an incentive-based recovery email. This approach improves cart recovery rates, increases revenue, and prevents unnecessary communications to customers who already converted."
This is one of the most common and revenue-generating Journey Builder implementations used in enterprise SFMC environments.
Multi-Step Abandoned Cart Journey in Salesforce Marketing Cloud
A Real-World Enterprise Cart Recovery Strategy
Instead of sending just one reminder and one offer, this journey uses a progressive recovery approach, where customers receive multiple reminders over several days, with purchase checks after each stage.
This is how large e-commerce brands typically recover abandoned carts.
Business Objective
The goal is:
Recover as many abandoned carts as possible without annoying customers.
Every reminder has a different purpose.
| Objective | |
|---|---|
| Reminder 1 | Friendly reminder |
| Reminder 2 | Create urgency |
| Reminder 3 | Last chance recovery |
| Decision Splits | Prevent unnecessary emails |
Complete Journey Flow
Customer Abandons Cart
↓
API Event
↓
Wait 8 Hours
↓
Cart Reminder 1
↓
Wait 1 Day
↓
Purchased?
↓ ↓
Yes No
Exit ↓
Cart Reminder 2
↓
Wait 3 Days
↓
Purchased?
↓ ↓
Yes No
Exit ↓
Cart Reminder 3
↓
Exit
Stage 1: API Event
What Happens?
Customer adds products to cart but leaves without purchasing.
Website sends event to SFMC.
Example:
{
"ContactKey":"10001",
"Email":"john@gmail.com",
"Product":"Nike Air Max",
"CartValue":"200",
"CartID":"ABC001"
}
The event enters Journey Builder immediately.
Why API Event?
Real-world reasons:
Instant Entry
No waiting for automation schedules.
Real-Time Marketing
Customer receives communication while purchase intent is still fresh.
Better Conversion
Most cart recoveries happen within first 24 hours.
Stage 2: Wait 8 Hours
Why Not Send Immediately?
Many marketers make the mistake of sending reminders within minutes.
Customers often:
Get distracted
Receive a call
Lose internet connection
Continue shopping later
Sending email instantly can feel pushy.
Example
Customer abandons cart:
9:00 AM
Journey waits until:
5:00 PM
Now reminder becomes relevant.
Stage 3: Cart Reminder 1
Purpose
Gentle Reminder
No discount.
No pressure.
Just a nudge.
Example Subject Lines
You left something behind
Your cart is waiting
Still interested?
Example Email
Hi John,
Looks like you left these items in your cart.
Nike Air Max
Running Socks
Complete your purchase before stock runs out.
Marketing Psychology
At this stage:
Customer may simply have forgotten.
No need to reduce profit margins by offering discounts yet.
Stage 4: Wait 1 Day
Journey waits another 24 hours.
Why?
Give customer enough time to:
Read email
Return to website
Purchase naturally
Many customers convert here.
Stage 5: Decision Split #1
Now SFMC checks:
Did customer purchase?
Purchased Path
If Yes:
Customer exits immediately.
Why Exit?
Imagine customer buys after Email 1.
If journey continues:
Customer receives:
Reminder 2
Reminder 3
Even after buying.
Bad experience.
Data Sources Used
Decision Split may check:
Purchase DE
ContactKey exists
Order Table
OrderID found
Sales Cloud Object
Order Status = Completed
API Event
Purchase Confirmation Event
Example
Customer Journey
Monday
Cart Abandoned
↓
Monday Evening
Reminder 1 Sent
↓
Tuesday Morning
Customer Purchases
↓
Exit Journey
Done.
Not Purchased Path
If customer did not buy:
Journey moves to Reminder 2.
Stage 6: Cart Reminder 2
This is more aggressive.
The customer already ignored:
Website visit
Reminder 1
Now we increase urgency.
Purpose
Create Fear of Missing Out (FOMO)
Example Subject Lines
Items in your cart are selling fast
Only a few left in stock
Your cart may expire soon
Example Email
Hi John,
Your cart is still active.
Nike Air Max
Only a few items remain in stock.
Complete your order today.
Why No Discount Yet?
Enterprise brands try:
Reminder
Urgency
Discount
before sacrificing profit.
Stage 7: Wait 3 Days
Now customer gets a longer cooling period.
Reason
By now customer has already seen:
Website
Reminder 1
Reminder 2
Sending emails daily may look spammy.
Business Logic
Give customer space.
Protect sender reputation.
Avoid unsubscribes.
Stage 8: Decision Split #2
After 3 days SFMC checks again:
Has customer purchased?
Purchased Path
If Yes:
Exit Journey.
Example
Customer buys after Reminder 2.
Journey immediately stops.
Why This Matters
This prevents situations like:
Customer buys product
then receives:
20% OFF
next day.
Customer gets angry because they paid full price.
Stage 9: Cart Reminder 3
This is the final recovery attempt.
Purpose
Last Chance Conversion
Typical Tactics
Discount
10% OFF
Free Shipping
Free Delivery Today
Coupon
SAVE10
Scarcity
Last chance before cart expires
Example Subject
Final Reminder: Complete your purchase today
Example Email
Hi John,
Your cart is about to expire.
Use code SAVE10 for 10% OFF.
Offer expires tonight.
Why Offer Comes Last
A common enterprise strategy:
Reminder 1 → No Incentive
Reminder 2 → Urgency
Reminder 3 → Incentive
This protects revenue.
Many customers purchase without needing discounts.
Exit Journey
After Reminder 3:
Customer exits.
Journey completed.
Timeline Example
Day 0
Customer abandons cart.
Day 0 + 8 Hours
Reminder 1 Sent.
Day 1
Purchase Check.
Purchased
Exit.
OR
Not Purchased
Reminder 2 Sent.
Day 4
Purchase Check.
Purchased
Exit.
OR
Not Purchased
Reminder 3 Sent.
Day 4
Journey Ends.
SFMC Components Used
| Component | Usage |
|---|---|
| API Event | Real-time entry |
| Journey Builder | Orchestration |
| Email Studio | Reminder emails |
| Data Extension | Cart data |
| Decision Split | Purchase validation |
| AMPscript | Personalization |
| Contact Builder | Contact management |
| Tracking Data Views | Reporting |
Senior-Level SFMC Interview Explanation
If an interviewer asks about this journey:
"This is a multi-touch abandoned cart recovery journey triggered through an API Event. Customers enter the journey when a cart abandonment event occurs. The journey follows a progressive engagement strategy with three reminder emails spread across four days. After each major communication, Decision Splits evaluate purchase activity using order or transaction data. Customers who complete a purchase exit immediately, while non-converters continue through increasingly persuasive recovery communications. This design maximizes cart recovery while minimizing unnecessary emails and protecting customer experience."
Anniversary Journey in Salesforce Marketing Cloud – Complete Breakdown
This journey is one of the simplest-looking journeys in SFMC, but in real projects it can be extremely powerful for customer engagement, loyalty, and retention.
What Is This Journey?
The purpose of this journey is:
Automatically send an email to customers on their anniversary date.
The anniversary can be:
Customer registration anniversary
First purchase anniversary
Membership anniversary
Loyalty program anniversary
Subscription anniversary
Partner anniversary
Employee work anniversary
Journey Flow
Event Entry
↓
Anniversary Email
↓
Exit Journey
Looks simple.
But the real magic happens in the Entry Event configuration.
Business Scenario
Let's assume:
Customer registered on:
11 June 2025
Today:
11 June 2026
Exactly one year later.
SFMC automatically identifies the anniversary date and sends a personalized email.
Step 1: Event Entry Source
The journey starts from the lightning bolt icon.
This is an Event Entry Source.
Unlike API Events, this event is generally driven by:
Contact Data
Data Extension Data
Salesforce Object Data
Scheduled Event Definitions
Example Data Extension
| SubscriberKey | FirstName | AnniversaryDate | |
|---|---|---|---|
| 1001 | john@gmail.com | John | 2026-06-11 |
| 1002 | sara@gmail.com | Sara | 2026-06-11 |
When the date arrives:
2026-06-11
Customers enter the journey automatically.
How SFMC Knows It's the Anniversary?
Usually one of two methods:
Method 1: Contact Builder Attribute
Store:
AnniversaryDate
Example:
2026-06-11
Journey checks daily.
When today's date matches:
Customer enters.
Method 2: Automation + Entry DE
Most common in projects.
Automation runs daily.
SQL finds anniversary customers.
Populates:
Anniversary_Entry_DE
Journey reads from that DE.
Real Enterprise Architecture
Customer Table
↓
SQL Query Activity
↓
Anniversary DE
↓
Journey Entry
↓
Email Send
Step 2: Anniversary Email
This is the heart of the journey.
Purpose
Make customer feel valued.
Not promotional.
Relationship-focused.
Example Subject Lines
Customer Anniversary
Happy 1 Year With Us 🎉
Membership Anniversary
Thank You For Being With Us
Loyalty Anniversary
Another Amazing Year Together
Subscription Anniversary
Celebrating Your Anniversary With Us
Example Email Content
Hi John,
Today marks one year since you joined our community.
Thank you for being part of our journey.
As a token of appreciation, we've added
500 bonus loyalty points to your account.
Thank you for choosing us.
Team XYZ
Personalization Used
Typically:
%%FirstName%%
%%MembershipTier%%
%%YearsWithUs%%
%%RewardPoints%%
Dynamic Content Example
Gold Members
1000 Bonus Points
Silver Members
500 Bonus Points
Platinum Members
VIP Reward
Real-World Example
E-commerce
Customer registered:
11 June 2025
Anniversary:
11 June 2026
Email:
Happy 1 Year With Us!
Enjoy 15% Off
Banking Example
Customer opened account:
11 June 2021
Anniversary:
11 June 2026
Email:
Thank you for banking with us for 5 years.
Telecom Example
Customer subscription started:
11 June 2024
Anniversary:
11 June 2026
Email:
Celebrating 2 years together.
Travel Industry Example
Customer joined loyalty program:
11 June 2023
Anniversary:
11 June 2026
Email:
You've been traveling with us for 3 years.
Why No Wait Activities?
Because anniversary date itself is the trigger.
The customer is already entering on the correct day.
No need for:
Wait Activities
Decision Splits
Additional Checks
Why No Decision Split?
Goal:
Send Anniversary Email
Once sent:
Journey Complete
No further action required.
Step 3: Exit Journey
After email delivery:
Customer exits immediately.
Behind-the-Scenes Automation (Most Common Setup)
Many SFMC developers create:
Daily Automation
Runs every morning.
SQL Query
Example Logic:
SELECT
SubscriberKey,
EmailAddress,
FirstName,
AnniversaryDate
FROM Customer_Master
WHERE
MONTH(AnniversaryDate) = MONTH(GETDATE())
AND DAY(AnniversaryDate) = DAY(GETDATE())
This finds customers whose anniversary is today.
Target DE
Anniversary_Entry_DE
Journey reads from this DE.
Advanced Version (Enterprise)
Instead of only sending an email:
Event
↓
Email
↓
Wait 3 Days
↓
SMS
↓
Exit
or
Event
↓
Email
↓
Wait 2 Days
↓
Check Opened?
↓
Resend Email
But your screenshot shows the basic version.
KPIs Measured
Delivery Rate
Delivered / Sent
Open Rate
Opened / Delivered
CTR
Clicks / Delivered
Reward Redemption
If coupon offered.
Revenue Generated
If anniversary offer included.
SFMC Components Used
| Component | Purpose |
|---|---|
| Journey Builder | Journey Orchestration |
| Event Entry Source | Customer Injection |
| Data Extension | Anniversary Records |
| Automation Studio | Daily Anniversary Selection |
| SQL Query Activity | Anniversary Logic |
| Email Studio | Email Creation |
| AMPscript | Personalization |
| Contact Builder | Customer Data |
Interview Explanation (4–7 Years SFMC)
"This is an Anniversary Journey triggered through an Event Entry Source. Customers enter the journey when their anniversary date matches the configured event criteria. Typically, an Automation Studio process identifies anniversary customers daily and populates an entry Data Extension. The journey sends a personalized anniversary email using attributes such as First Name, Membership Tier, Loyalty Points, or Years With Us. After the email is delivered, customers exit the journey. This type of journey is commonly used for customer retention, loyalty engagement, membership milestones, and subscription anniversaries."
Although this journey has only one email and one exit, it is a very common production journey because it helps strengthen customer relationships and increases long-term retention with minimal operational effort.
Birthday Journey with Coupon Redemption Tracking – Complete Enterprise Use Case
This journey is much more sophisticated than a simple Birthday or Anniversary email.
It doesn't just send a birthday greeting.
It actually tracks whether the customer redeemed a birthday coupon, sends reminders if they haven't, and stops communication once they redeem it.
This is a real-world loyalty and retention journey used by retailers, restaurants, beauty brands, airlines, banks, and subscription companies.
Business Objective
The goal is:
Celebrate the customer's birthday and encourage them to make a purchase using a special birthday coupon.
Instead of simply wishing them happy birthday, the company wants:
Increased engagement
Coupon redemption
Additional revenue
Customer retention
Complete Journey Flow
Birthday Event
↓
Happy Birthday Email
↓
Wait 3 Days
↓
Redeemed Coupon?
↓ Yes
Join
↓
Offer Redemption Email
↓
Exit
↓ No
Offer Reminder
↓
Wait 1 Day
↓
Redeemed Coupon?
↓ Yes
Join
↓
Offer Redemption Email
↓
Exit
↓ No
Final Offer Reminder
↓
Exit
Business Scenario
Let's say:
Customer:
Name: John Smith
Birthday: June 11
Company policy:
Birthday Coupon = 20% OFF
Valid for 4 Days
On June 11:
Customer receives:
Happy Birthday John 🎉
Here's a 20% Birthday Coupon
Now SFMC starts tracking whether he uses the coupon.
Step 1: Event Entry Source
The lightning icon is the Entry Event.
How Customers Enter
Usually through:
Birthday Data Extension
SubscriberKey
EmailAddress
BirthDate
CouponCode
Automation Studio
Every morning:
SELECT *
FROM Customer_Master
WHERE MONTH(BirthDate)=MONTH(GETDATE())
AND DAY(BirthDate)=DAY(GETDATE())
Results are loaded into:
Birthday_Entry_DE
Journey injects customers automatically.
Step 2: Happy Birthday Email
This is the first communication.
Purpose
Celebrate customer.
Create emotional connection.
Deliver coupon.
Example Subject
Happy Birthday John! 🎂
Email Example
Hi John,
Happy Birthday from all of us!
To celebrate your special day,
enjoy 20% OFF your next purchase.
Coupon Code:
BIRTHDAY20
Offer expires in 4 days.
Personalization
Using AMPscript:
%%FirstName%%
%%CouponCode%%
%%ExpirationDate%%
Why Birthday Emails Work
Birthday campaigns usually generate:
High Open Rates
High CTR
High Conversion Rates
Because customers expect them.
Step 3: Wait Activity (3 Days)
Journey waits:
3 Days
Why?
Give customer enough time to:
Open email
Visit website
Make purchase
Redeem coupon
No need to send reminders immediately.
Step 4: Decision Split #1
After 3 days SFMC asks:
Has coupon been redeemed?
This is the most important step.
How Redemption Is Tracked
Several methods:
Method 1: Coupon Redemption DE
Example:
| SubscriberKey | CouponRedeemed |
|---|---|
| 10001 | True |
Decision Split checks:
CouponRedeemed = True
Method 2: Order Table
Coupon code used during checkout.
Method 3: Sales Cloud Object
Order Status updated.
Method 4: API Event
Website sends:
{
"SubscriberKey":"10001",
"CouponUsed":"True"
}
Redeemed Path
If coupon was used:
Customer moves to upper path.
Step 5: Join Activity
This orange activity combines contacts from different branches.
Think of it as:
Merge Traffic
No matter how customer reached here:
All redeemed customers are merged into one path.
Why Use Join?
Without Join:
You would need duplicate emails.
Join keeps journey clean.
Step 6: Offer Redemption Email
Sent only to customers who actually redeemed the coupon.
Purpose
Thank customer.
Confirm success.
Encourage future purchases.
Example Email
Hi John,
Thanks for celebrating your birthday with us!
We're glad you redeemed your birthday reward.
Enjoy your purchase.
Marketing Benefit
Customers feel:
Reward Received
Purchase Completed
Brand Appreciated
Step 7: Exit Journey
Redeemed customers exit.
Journey complete.
Not Redeemed Path
Now let's follow customers who ignored the first email.
Step 8: Offer Reminder Email
Customer has not used coupon.
Send reminder.
Subject Example
Your Birthday Gift Is Waiting 🎁
Email Example
Hi John,
Don't forget your birthday reward.
20% OFF expires soon.
Use code:
BIRTHDAY20
Why Reminder Works
Many customers:
Open email
Forget about it
Plan to buy later
Reminder increases redemption significantly.
Step 9: Wait Activity (1 Day)
Journey waits:
1 Day
Purpose:
Give customer one final chance.
Step 10: Decision Split #2
Journey checks again:
Has customer redeemed coupon?
Redeemed After Reminder
Customer now:
Reminder Received
Coupon Redeemed
Moves to:
Join
↓
Offer Redemption Email
↓
Exit
Why This Is Smart
Customer receives:
Birthday Email
Reminder Email
Purchase
Thank You Email
Personalized experience.
Not Redeemed Again
Customer still ignored:
Birthday Email
Reminder Email
Journey enters final stage.
Step 11: Final Offer Reminder
Last communication.
Example Subject
Last Chance To Use Your Birthday Gift
Example Email
Hi John,
Your birthday coupon expires today.
Use code:
BIRTHDAY20
This is your final reminder.
Why Final Reminder?
Creates urgency.
Psychology:
Fear of Missing Out (FOMO)
Often generates last-minute conversions.
Step 12: Exit Journey
After final reminder:
Customer exits.
Journey complete.
Real Customer Example
Day 0
Birthday Email Sent.
Day 3
Check Redemption.
Scenario A
Coupon Used.
Thank You Email
↓
Exit
Scenario B
Coupon Not Used.
Reminder Sent
↓
Wait 1 Day
↓
Check Again
Scenario B1
Coupon Used After Reminder.
Thank You Email
↓
Exit
Scenario B2
Still Not Used.
Final Reminder
↓
Exit
Why This Journey Is Enterprise-Level
This journey demonstrates multiple advanced SFMC concepts:
Event-Based Entry
Birthday-triggered customer entry.
Behavioral Tracking
Tracking coupon redemption.
Decision Splits
Evaluating customer actions.
Wait Activities
Controlled communication timing.
Join Activities
Merging customer paths.
Dynamic Personalization
Unique coupon codes.
Customer Lifecycle Marketing
Birthday → Offer → Reminder → Redemption → Thank You
Components Used
| SFMC Component | Purpose |
|---|---|
| Event Entry Source | Birthday Trigger |
| Email Activity | Birthday & Reminder Emails |
| Wait Activity | Delay Communications |
| Decision Split | Redemption Check |
| Join Activity | Merge Redeemed Paths |
| Data Extension | Coupon Tracking |
| AMPscript | Personalization |
| Automation Studio | Birthday Audience Creation |
Interview Explanation (5–8 Years SFMC)
"This is a birthday coupon redemption journey. Customers enter based on their birthday date and receive a personalized birthday email containing a coupon code. The journey waits three days and evaluates coupon redemption using a Decision Split. Customers who redeem the coupon are merged through a Join Activity and receive a thank-you/redemption confirmation email. Customers who do not redeem receive reminder communications followed by another redemption check. If the coupon remains unused, a final reminder is sent before exit. This journey combines lifecycle marketing, behavioral tracking, decisioning, and coupon management to improve customer engagement and revenue."
This is the type of journey that interviewers like because it showcases Decision Splits, Join Activities, behavioral data tracking, personalization, and customer lifecycle orchestration all in a single use case.
Event Follow-Up Journey in Salesforce Marketing Cloud
Post-Event Attendee vs No-Show Engagement Journey
This journey is a classic Event Follow-Up Journey used after webinars, conferences, product launches, workshops, training sessions, and virtual events.
Unlike previous journeys that focused on purchases or coupons, this one focuses on event attendance behavior.
The business goal is:
Send different follow-up communications depending on whether someone attended the event or not.
Real Business Scenario
Imagine your company hosts a webinar:
Event
Topic: Salesforce Marketing Cloud Advanced Journey Builder
Date: June 11, 2026
Time: 3 PM
500 people register.
After the webinar:
320 attended
180 did not attend
Sending the same email to everyone would be a mistake.
Attendees and non-attendees need different messaging.
That's exactly what this journey does.
Journey Architecture
Event Registration Data
↓
Data Extension
↓
Decision Split
/ \
Attended Did Not Attend
↓ ↓
Thank You We Missed You
↓ ↓
Exit Exit
Step 1: Data Extension Entry Source
The journey starts from a Data Extension Entry Source.
Unlike an API Event, contacts enter through a DE.
Example Entry Data Extension
| SubscriberKey | FirstName | AttendanceStatus | |
|---|---|---|---|
| 1001 | john@gmail.com | John | Attended |
| 1002 | sara@gmail.com | Sara | Did Not Attend |
This data is typically loaded after the event ends.
How Is Attendance Data Collected?
Most companies use:
Webinar Platforms
Zoom
Webex
GoToWebinar
Microsoft Teams
These platforms provide attendance reports.
Example Export
Email,AttendanceStatus
john@gmail.com,Attended
sara@gmail.com,Did Not Attend
Imported into SFMC.
Automation Process
Zoom/Webinar Platform
↓
Attendance Report
↓
Import Activity
↓
Event_Followup_DE
↓
Journey Entry
Step 2: Decision Split
This is the brain of the journey.
The split evaluates:
AttendanceStatus
Rule
IF AttendanceStatus = Attended
Go to Thank You path.
Else
Did Not Attend
Go to We Missed You path.
Why Decision Split?
Because attendees and no-shows have completely different experiences.
Attendee Mindset
They:
Invested time
Consumed content
Showed interest
Need appreciation.
Non-Attendee Mindset
They:
Registered
Intended to attend
Missed the event
Need recovery messaging.
Path 1: Attended
Customers who attended move to:
Thank You Email
Thank You Email Purpose
Goals:
Show appreciation
Build relationship
Share event materials
Encourage next action
Example Subject Lines
Thank You for Attending!
Thanks for Joining Our Webinar
We Appreciate Your Participation
Example Email
Hi John,
Thank you for attending our webinar.
We hope you found the session valuable.
As promised, here are the resources:
✔ Presentation Deck
✔ Webinar Recording
✔ Documentation
Thank you for being part of the event.
Business Benefits
This email often includes:
Resources
Presentation Slides
Recording
Watch Again
Next Steps
Book Demo
Survey
Rate The Session
Example for SFMC Webinar
Thank you for attending our
Advanced Journey Builder Session.
Download:
- Journey Builder Guide
- AMPscript Cheat Sheet
- Webinar Recording
Exit Journey
After thank-you email:
Customer exits.
Why Exit?
Objective achieved.
No further communication required.
Path 2: Did Not Attend
Contacts who missed the event enter:
We Missed You Email
Purpose
Recover engagement.
Keep customer interested.
Prevent lost opportunities.
Example Subject Lines
Sorry We Missed You
Couldn't Attend? Watch The Recording
You Missed The Live Session
Example Email
Hi Sara,
We noticed you couldn't attend the webinar.
No worries.
You can still access:
✔ Event Recording
✔ Presentation Slides
✔ Resource Guide
Watch on demand anytime.
Why This Works
Instead of losing the lead:
Company gives them another chance.
Marketing Psychology
Customer thinks:
Good.
I can still watch it later.
The lead stays warm.
Real Enterprise Example
Suppose:
Product Launch Webinar
1000 registrations.
Attendees
Receive:
Thank You Email
Product Demo Link
Sales Consultation Link
Non-Attendees
Receive:
Recording Link
Product Brochure
Future Event Invitation
SFMC Components Used
| Component | Purpose |
|---|---|
| Data Extension Entry | Journey Entry |
| Decision Split | Attendance Evaluation |
| Email Activity | Follow-Up Communication |
| Exit Activity | Journey Completion |
| Automation Studio | Attendance Import |
| Contact Builder | Contact Data Storage |
Typical Data Extension Structure
| Field | Type |
|---|---|
| SubscriberKey | Text |
| EmailAddress | |
| FirstName | Text |
| EventName | Text |
| AttendanceStatus | Text |
| EventDate | Date |
Reporting Metrics
Marketing teams usually track:
Attendee Email
Open Rate
Click Rate
Survey Completion
No-Show Email
Recording Views
Click Rate
Re-Engagement Rate
Advanced Version Used by Enterprises
Many companies extend this journey:
Data Extension
↓
Decision Split
/ \
Attended No Show
↓ ↓
Thank You Recording Email
↓ ↓
Survey Wait 3 Days
↓ ↓
Exit Reminder Email
↓
Exit
But your screenshot shows the simplified version.
Interview Explanation (4–8 Years SFMC)
"This is an event follow-up journey driven by a Data Extension containing attendance data. After an event concludes, attendee information is imported into SFMC. A Decision Split evaluates the Attendance Status field. Contacts who attended receive a Thank You email containing event resources, recordings, surveys, or next-step actions. Contacts who did not attend receive a We Missed You email with access to the recording and supporting materials. This approach improves attendee engagement, maximizes event ROI, and ensures personalized post-event communication based on customer behavior."
Path Optimizer Email A/B Test Journey in Salesforce Marketing Cloud
Testing Which Email Performs Better Before Scaling
This journey demonstrates one of the most powerful Journey Builder features:
Path Optimizer
Instead of guessing which email will perform better, SFMC automatically splits the audience, tests multiple versions, and helps marketers identify the winning approach.
This is commonly used by enterprise marketing teams to improve:
Open Rates
Click Rates
Conversions
Revenue
Engagement
Business Problem
Imagine your marketing team wants to send a promotion email.
The question is:
Which email will generate more sales?
Nobody knows.
Marketing Team Suggests:
Version A
Subject:
Get 20% OFF Today
Version B
Subject:
Your Exclusive Discount Is Waiting
Both seem good.
Instead of guessing, SFMC tests both.
Journey Architecture
Audience
↓
Data Extension
↓
Path Optimizer
/ \
50% 50%
↓ ↓
Email A Email B
\ /
Winner Analysis
↓
Exit
Step 1: Data Extension Entry Source
Journey starts from a Data Extension.
Example:
| SubscriberKey | |
|---|---|
| 1001 | john@gmail.com |
| 1002 | sara@gmail.com |
| 1003 | mike@gmail.com |
Suppose:
Total Audience = 10,000 Contacts
These customers enter the journey.
Why Data Extension?
Because this journey is generally campaign-based.
Examples:
Promotional Campaign
Newsletter
Product Launch
Holiday Sale
Flash Sale
The audience is already prepared.
Step 2: Path Optimizer
This orange activity is the star of the journey.
What Does Path Optimizer Do?
It automatically divides customers into multiple paths.
In your screenshot:
Path A = 50%
Path B = 50%
Example
10,000 customers enter.
SFMC automatically splits:
5,000 → Email A
5,000 → Email B
Why Use Path Optimizer?
Without testing:
Send One Email
Hope It Works
With Path Optimizer:
Test Multiple Ideas
Measure Results
Choose Winner
Much smarter.
What Can Be Tested?
Most people think only subject lines.
Actually, Path Optimizer can test:
Subject Lines
20% OFF Today
vs
Exclusive Offer For You
Email Designs
Different layouts.
CTA Buttons
Shop Now
vs
Claim Offer
Discounts
10% OFF
vs
15% OFF
Content Strategy
Emotional Copy
vs
Product-Focused Copy
Path A
Customers assigned to Path A receive:
Email A
Example
Subject:
Get 20% OFF Today
Email:
Hi John,
Enjoy 20% OFF on all products.
Offer expires tonight.
Path B
Customers assigned to Path B receive:
Email B
Example
Subject:
Your Exclusive Discount Is Waiting
Email:
Hi John,
We've reserved a special offer just for you.
Claim your discount now.
What Happens Next?
Customers interact with the emails.
SFMC tracks:
Opens
Clicks
Conversions
Revenue
Example Results
After campaign:
| Metric | Email A | Email B |
|---|---|---|
| Open Rate | 25% | 31% |
| Click Rate | 8% | 12% |
| Conversion Rate | 3% | 5% |
Winner
Clearly:
Email B Wins
Because:
Higher Opens
Higher Clicks
Higher Conversions
Flag Activity (Orange Flag)
The flag icon after Email A represents:
Path Optimizer Evaluation Point
This is where SFMC gathers results from all paths.
What Does It Measure?
Depending on configuration:
Open Rate
Which email generated more opens?
Click Rate
Which email generated more clicks?
Conversion Rate
Which email generated more purchases?
Revenue
Which email generated more money?
Real Enterprise Example
Suppose:
Audience
100,000 Customers
Test Sample
10% Test Audience
Split into:
5,000 Email A
5,000 Email B
Results
After 24 hours:
Email B Wins
Remaining Audience
90,000 Customers
Receive:
Winning Version (Email B)
This is the most common enterprise setup.
Example Use Cases
Black Friday Campaign
Test:
Black Friday Starts Now
vs
Early Access To Black Friday Deals
Product Launch
Test:
Meet Our New Product
vs
Something Exciting Is Coming
Abandoned Cart
Test:
You Left Something Behind
vs
Your Cart Is Waiting
Newsletter
Test:
June Newsletter
vs
Top Marketing Insights This Month
Why A/B Testing Matters
Without testing:
Assumption-Based Marketing
With Path Optimizer:
Data-Driven Marketing
Common Winning Metrics
Most organizations optimize for:
Open Rate
For subject-line testing.
Click Rate
For content testing.
Conversion Rate
For sales-focused campaigns.
Revenue Per Email
For e-commerce brands.
SFMC Components Used
| Component | Purpose |
|---|---|
| Data Extension Entry | Audience Source |
| Path Optimizer | A/B Testing |
| Email Activity | Test Variants |
| Tracking | Measure Results |
| Exit Activity | Journey Completion |
Advanced Enterprise Version
Large organizations often use:
Data Extension
↓
Path Optimizer
/ | \
Email A B C
\ | /
Winning Path
↓
Send Winner To Remaining Audience
Testing:
3 Subject Lines
3 Designs
3 Offers
All automatically measured.
Interview Explanation (5–8 Years SFMC)
"This journey demonstrates the use of Path Optimizer for A/B testing. Contacts enter through a Data Extension and are automatically split into two equal groups. Each group receives a different email variant. SFMC tracks performance metrics such as opens, clicks, conversions, or revenue depending on the configured success criteria. The results are evaluated through the Path Optimizer activity, enabling marketers to identify the highest-performing email version. This feature supports data-driven optimization and is commonly used for subject line testing, creative testing, offer testing, and campaign performance improvement."
Re-Engagement Journey in Salesforce Marketing Cloud
Winning Back Inactive Subscribers Before They Churn
This is one of the most important lifecycle journeys in SFMC because it directly impacts:
Sender Reputation
Deliverability
Subscriber Retention
Email Engagement
List Hygiene
The purpose of this journey is simple:
Identify inactive subscribers and try multiple times to re-engage them before marking them as inactive.
This is a journey you'll find in almost every mature SFMC implementation.
Business Problem
Imagine:
You have:
1,000,000 Subscribers
But:
300,000 haven't opened or clicked
any email in the last 180 days.
These contacts are hurting:
Open Rates
Engagement Metrics
Sender Reputation
Eventually Gmail and Outlook start thinking:
Your emails are unwanted.
This affects even your engaged subscribers.
Journey Architecture
Inactive Subscribers
↓
We Miss You
↓
Wait 3 Days
↓
Engagement Split
/ \
Yes No
Exit ↓
CTA Reminder
↓
Wait 3 Days
↓
Engagement Split
/ \
Yes No
Exit ↓
Last Chance
↓
Wait 3 Days
↓
Engagement Split
/ \
Yes No
Exit ↓
Update Contact
↓
Exit
Real Business Scenario
Suppose:
Customer:
John
Has not:
Opened email
Clicked email
Purchased
For:
180 Days
Automation identifies John as inactive.
John enters this journey.
Step 1: Data Extension Entry Source
Journey starts with:
Data Extension
Typically populated through SQL.
Example SQL
SELECT
SubscriberKey,
EmailAddress,
FirstName
FROM MasterSubscribers
WHERE LastOpenDate < DATEADD(day,-180,GETDATE())
This identifies inactive subscribers.
Entry DE Example
| SubscriberKey | LastOpen | |
|---|---|---|
| 1001 | john@gmail.com | 180 days ago |
| 1002 | sara@gmail.com | 220 days ago |
These contacts enter the journey.
Step 2: "We Miss You" Email
This is the first recovery attempt.
Goal
Remind subscribers why they joined.
Create curiosity.
Encourage engagement.
Example Subject Lines
We Miss You
It's Been A While
Come Back And See What's New
Example Email
Hi John,
We've noticed you haven't visited us recently.
A lot has changed.
Check out:
✔ New Products
✔ Exclusive Offers
✔ Fresh Content
We'd love to see you again.
Why This Email Matters
Many people simply:
Forget
Change priorities
Miss emails
A gentle reminder often works.
Step 3: Wait Activity (3 Days)
Journey waits:
3 Days
Why?
Give customer enough time to:
Open
Click
Visit website
No need to pressure immediately.
Step 4: Engagement Split #1
This is where Journey Builder becomes powerful.
SFMC asks:
Did customer engage?
What Counts As Engagement?
Depending on configuration:
Open
Opened Email
Click
Clicked Link
Website Visit
Custom event.
Purchase
Order recorded.
YES Path
Customer engaged.
Example:
John opened email.
Journey considers him reactivated.
Action
Exit Journey
Why Exit?
Goal achieved.
No need for more recovery emails.
NO Path
Customer ignored first attempt.
Journey continues.
Step 5: CTA Reminder Email
CTA = Call To Action.
This email is stronger.
Purpose
Create urgency.
Encourage specific action.
Example Subject
Don't Miss Out
Your Benefits Are Waiting
Example Email
Hi John,
You still have access to:
✔ Exclusive Discounts
✔ Early Access Promotions
✔ Member Benefits
Click below to explore.
Marketing Psychology
First Email:
Friendly Reminder
Second Email:
Value Proposition
Now customer understands what's being missed.
Step 6: Wait 3 Days
Again:
3 Days
Purpose:
Allow time for engagement.
Step 7: Engagement Split #2
SFMC checks again:
Did customer engage after Reminder?
YES Path
Customer:
Opened
Clicked
Purchased
Journey exits.
NO Path
Still inactive.
Move to final stage.
Step 8: Last Chance Email
This is the final re-engagement attempt.
Goal
Create maximum urgency.
Example Subject Lines
Last Chance To Stay Subscribed
Do You Still Want To Hear From Us?
Your Subscription May Be Removed
Example Email
Hi John,
We've tried reaching you.
If you'd still like to receive updates,
please click below.
Otherwise we'll reduce future communications.
Why Last Chance Works
People react to loss.
Psychology:
Fear Of Missing Out
Many subscribers re-engage here.
Step 9: Wait 3 Days
Final waiting period.
Step 10: Engagement Split #3
SFMC performs one last check.
Did customer engage?
YES Path
Subscriber is saved.
Journey exits.
NO Path
Customer remains inactive.
Now we take action.
Step 11: Update Contact Activity
This is one of the most valuable enterprise features in this journey.
What Happens?
Journey updates subscriber data.
Example:
Before:
| SubscriberKey | Status |
|---|---|
| 1001 | Active |
After:
| SubscriberKey | Status |
|---|---|
| 1001 | Inactive |
Common Updates
Flag Subscriber
EngagementStatus = Inactive
Suppression Flag
SuppressFromMarketing = True
Re-Engagement Failed
ReengagementStatus = Failed
Subscriber Tier
Dormant
Why Update Contact?
Future campaigns can exclude inactive users.
Benefits
Improves:
Open Rate
Inactive users removed.
Deliverability
Mailbox providers see better engagement.
Sender Reputation
Healthier email program.
Real Enterprise Workflow
Inactive Subscriber
↓
Re-engagement Journey
↓
Still Inactive?
↓
Update Contact
↓
Suppression List
↓
Exclude From Future Sends
Example Timeline
Day 0
We Miss You Email
Day 3
Check Engagement
Day 3
CTA Reminder
Day 6
Check Engagement
Day 6
Last Chance Email
Day 9
Final Check
Day 9
Update Contact
Day 9
Exit Journey
SFMC Components Used
| Component | Purpose |
|---|---|
| Data Extension Entry | Inactive Audience |
| Email Activities | Re-engagement Campaign |
| Wait Activities | Delay Evaluation |
| Engagement Splits | Measure Opens/Clicks |
| Update Contact | Update Subscriber Status |
| Exit Activity | End Journey |
| Automation Studio | Identify Inactive Users |
| SQL Query Activity | Audience Creation |
Interview Explanation (5–8 Years SFMC)
"This is a re-engagement journey designed for inactive subscribers. Contacts enter through a Data Extension populated using engagement criteria such as no opens or clicks within a defined period. The journey sends a series of progressively stronger re-engagement emails separated by wait periods. After each email, Engagement Splits evaluate whether the subscriber opened or clicked. Engaged contacts exit the journey immediately, while inactive contacts continue through additional recovery attempts. If the subscriber remains inactive after all attempts, an Update Contact activity flags the record as inactive or suppressed, allowing future campaigns to exclude unengaged users and protect sender reputation."
Welcome Journey in Salesforce Marketing Cloud
The Most Important Customer Lifecycle Journey
If there is one journey that almost every company using Salesforce Marketing Cloud should have, it's the Welcome Journey.
Why?
Because the first few days after a customer subscribes are when engagement is at its highest.
This journey introduces the brand, builds trust, and guides new subscribers toward their first meaningful action.
Business Objective
The goal is:
Turn a new subscriber into an engaged customer.
This journey helps:
Increase open rates
Build trust
Educate customers
Drive first purchase
Improve retention
Real Business Scenario
Imagine someone signs up on your website.
Customer
Name: John Smith
Email: john@gmail.com
Signup Source
Newsletter Signup Form
or
Account Registration
or
Product Trial Registration
The moment John signs up, he enters this Welcome Journey.
Journey Architecture
New Subscriber
↓
Data Extension Entry
↓
Welcome Email 1
↓
Wait 1 Day
↓
Welcome Email 2
↓
Wait 1 Day
↓
Welcome Email 3
↓
Exit Journey
Total Journey Duration:
2 Days
Why Use Multiple Welcome Emails?
Most companies make a mistake.
They send:
One Welcome Email
and stop.
But customers cannot learn everything about a company from one email.
Instead:
Email 1
Introduce the brand.
Email 2
Educate.
Email 3
Drive action.
This creates a much better onboarding experience.
Step 1: Data Extension Entry Source
The journey starts from:
Data Extension
Example Entry Data Extension
| SubscriberKey | EmailAddress | FirstName | SignupDate |
|---|---|---|---|
| 1001 | john@gmail.com | John | 2026-06-11 |
How Contacts Enter?
Usually through:
Website Registration
Create Account
Newsletter Signup
Subscribe Now
Lead Form
Download Ebook
Free Trial
Start Trial
Real Architecture
Website Form
↓
Data Extension
↓
Journey Entry
Step 2: Welcome Email 1
This is the first impression.
Goal
Introduce brand.
Set expectations.
Build trust.
Example Subject Lines
Welcome to Our Community 🎉
Thanks for Joining Us
We're Glad You're Here
Example Email
Hi John,
Welcome to our community!
We're excited to have you with us.
Over the next few days you'll discover:
✔ Exclusive Content
✔ Product Updates
✔ Member Benefits
Thank you for joining.
Why Email 1 Is Important
Research consistently shows:
Welcome emails often achieve:
Highest Open Rates
Highest Click Rates
Because customer just subscribed.
Interest is fresh.
Step 3: Wait Activity (1 Day)
Journey waits:
1 Day
Why Wait?
Avoid overwhelming customer.
Let them digest first email.
Build anticipation.
Step 4: Welcome Email 2
This email is educational.
Goal
Show value.
Teach customer about products or services.
Example Subject
Here's How To Get Started
Example Email
Hi John,
Let's help you get started.
Here are some resources:
✔ Beginner Guide
✔ Product Tutorials
✔ Help Center
✔ FAQs
Everything you need is here.
SaaS Example
If company sells software:
Create First Project
Invite Team Members
Explore Dashboard
E-commerce Example
If company sells products:
Best Sellers
Top Categories
Popular Products
Banking Example
Activate Account
Set Up Online Banking
Explore Benefits
Marketing Goal
Reduce confusion.
Increase product adoption.
Step 5: Wait Activity (1 Day)
Again:
1 Day
Why Another Wait?
Customer shouldn't receive:
3 Emails In One Day
Spacing improves engagement.
Step 6: Welcome Email 3
Now we move to conversion.
Goal
Encourage action.
Generate revenue.
Drive engagement.
Example Subject
Ready To Take The Next Step?
Example Email
Hi John,
Now that you've explored our platform,
here's a special offer for you.
Use code:
WELCOME10
and enjoy 10% OFF your first purchase.
Common CTA Examples
E-commerce
Shop Now
SaaS
Upgrade Plan
Education
Start Learning
Banking
Apply Today
Why Put Offer in Email 3?
Because:
Email 1
Relationship
Email 2
Education
Email 3
Conversion
This sequence converts better than immediately pushing sales.
Step 7: Exit Journey
After Email 3:
Exit Journey
Customer onboarding complete.
Real Customer Timeline
Day 0
Customer signs up.
↓
Welcome Email 1
Day 1
Welcome Email 2
Day 2
Welcome Email 3
↓
Exit Journey
Example for Different Industries
E-commerce
Email 1:
Welcome to Nike
Email 2:
Explore Top Products
Email 3:
10% OFF First Order
SaaS
Email 1:
Welcome to the Platform
Email 2:
How to Use Features
Email 3:
Upgrade to Premium
Banking
Email 1:
Welcome to Our Bank
Email 2:
Digital Banking Guide
Email 3:
Explore Credit Card Benefits
SFMC Components Used
| Component | Purpose |
|---|---|
| Data Extension Entry | New Subscribers |
| Email Activities | Welcome Series |
| Wait Activities | Message Spacing |
| Exit Activity | Journey Completion |
| Automation Studio | Feed Entry DE |
| Contact Builder | Contact Management |
KPIs Tracked
Open Rate
Measure engagement.
Click Rate
Measure interest.
First Purchase Rate
Measure conversion.
Account Activation Rate
Measure onboarding success.
Revenue Generated
Measure business impact.
Advanced Enterprise Version
Large companies often enhance this journey:
Welcome Email 1
↓
Wait
↓
Engagement Split
/ \
Opened Not Opened
↓ ↓
Email 2 Resend Email
↓
Wait
↓
Decision Split
↓
Offer Email
This creates a personalized onboarding experience.
Common Interview Questions
Why is a Welcome Journey important?
Because engagement is highest immediately after signup. It helps build trust, educate customers, and drive early conversions.
Why use wait activities?
To avoid overwhelming subscribers and to create a structured onboarding experience.
Why send multiple welcome emails?
Different emails serve different objectives:
Introduction
Education
Conversion
Senior-Level Interview Explanation (4–8 Years SFMC)
"This is a multi-step welcome onboarding journey triggered through a Data Extension entry source. New subscribers enter after registration or subscription. The first email focuses on brand introduction and expectation setting. After a one-day wait, a second email educates users about products, services, or platform features. Following another wait period, a third email drives a key business action such as a purchase, upgrade, or account activation. The journey helps improve customer onboarding, increase engagement, and accelerate conversion during the period when subscriber interest is highest."
Welcome Journey with Engagement-Based Personalization
Smart Onboarding Journey Using Engagement Splits
This journey is a more advanced version of the standard Welcome Journey.
Instead of sending the same sequence to everyone, it adapts based on whether the subscriber engages with the first email.
This is the type of onboarding journey many mature SFMC implementations use because it creates a more personalized customer experience.
Business Objective
The goal is:
Deliver different onboarding experiences based on subscriber engagement behavior.
The journey answers:
Did the customer interact with Welcome Email 1?
If yes:
Continue normal onboarding.
If no:
Try to re-engage before continuing.
Journey Architecture
New Subscriber
↓
Welcome 1
↓
Wait 1 Day
↓
Engagement Split
/ \
Yes No
↓ ↓
Join Welcome 1a
↓ ↓
Welcome 2 Wait 1 Day
↓ ↓
Wait 1 Day Engagement Split
↓ / \
Welcome 3 Yes No
↓ ↓ ↓
Exit Join Welcome 1b
↓ ↓
Welcome 2 Exit
↓
Wait 1 Day
↓
Welcome 3
↓
Exit
Real Business Scenario
A new customer signs up:
| Field | Value |
|---|---|
| Name | John |
| john@gmail.com | |
| Signup Date | June 11 |
John enters the Welcome Journey.
Now SFMC starts tracking whether he engages with the first email.
Step 1: Data Extension Entry
The journey begins with a Data Extension.
Example:
| SubscriberKey | EmailAddress | FirstName |
|---|---|---|
| 1001 | john@gmail.com | John |
Contacts typically come from:
Website Registration
Newsletter Signup
Landing Pages
CRM Sync
Mobile App Registration
Step 2: Welcome Email 1
This is the first onboarding email.
Purpose
Introduce the brand.
Set expectations.
Build trust.
Example Subject
Welcome to Our Community 🎉
Example Email
Hi John,
Thank you for joining us.
We're excited to have you with us.
Here's what you'll receive:
✔ Product Updates
✔ Exclusive Offers
✔ Helpful Resources
Step 3: Wait 1 Day
Journey waits:
24 Hours
Reason:
Allow subscriber time to interact.
Step 4: Engagement Split
This is where the journey becomes intelligent.
SFMC checks:
Did subscriber engage with Welcome Email 1?
What Counts as Engagement?
Usually:
Open
Opened Email
Click
Clicked Link
Both
Many organizations configure:
Open OR Click
YES Path (Engaged Subscriber)
Customer opened or clicked.
Example:
John opened Welcome Email.
Why This Matters
The subscriber is interested.
No need to resend anything.
Continue onboarding.
Join Activity
The engaged customer immediately enters the Join activity.
Think of Join as:
Merge Traffic
After joining:
Customer continues to Welcome 2.
Step 5: Welcome Email 2
Purpose:
Educate customer.
Example Content
Getting Started Guide
✔ Top Features
✔ Tutorials
✔ Best Practices
✔ Help Center
Step 6: Wait 1 Day
Pause for:
24 Hours
Step 7: Welcome Email 3
Purpose:
Drive conversion.
Example
Use code WELCOME10
Get 10% OFF
Step 8: Exit Journey
Customer exits after completing onboarding.
NO Path (Did Not Engage)
Now let's look at customers who ignored Welcome 1.
Why Is This Important?
Many subscribers:
Miss the email
Were busy
Didn't notice it
Opened inbox later
Sending the exact same onboarding sequence may not be effective.
Step 5A: Welcome 1a Email
This is a recovery email.
Think of it as:
Second Attempt
Example Subject
Just Making Sure You Didn't Miss This
Example Content
Hi John,
We wanted to make sure you saw our welcome message.
Here's what you're missing:
✔ Exclusive Resources
✔ Member Benefits
✔ Product Updates
Why Send Welcome 1a?
Instead of assuming lack of interest, give the subscriber another opportunity to engage.
Step 6A: Wait 1 Day
Again wait:
24 Hours
Step 7A: Second Engagement Split
SFMC checks again:
Did subscriber engage after Welcome 1a?
YES Path
Subscriber finally engages.
Example:
Opened Welcome 1a
Now they are interested.
Join Activity
Customer joins the main onboarding flow.
Why Use Join?
Without Join:
You would need duplicate versions of:
Welcome 2
Welcome 3
Join keeps journey clean.
Continue Journey
Subscriber receives:
Welcome 2
↓
Wait
↓
Welcome 3
↓
Exit
Same as engaged users.
NO Path Again
Customer ignored:
Welcome 1
AND
Welcome 1a
Now we have a problem.
Step 8A: Welcome 1b
Final attempt.
Example Subject
Do You Still Want To Hear From Us?
Example Email
Hi John,
We've tried reaching you.
If you'd like to stay updated,
please confirm your interest.
Purpose
Final engagement attempt before ending onboarding.
Exit Journey
After Welcome 1b:
Customer exits.
Customer Examples
Scenario 1 – Engaged Immediately
Welcome 1
↓
Open
↓
Welcome 2
↓
Welcome 3
↓
Exit
Scenario 2 – Engaged Later
Welcome 1
↓
No Open
↓
Welcome 1a
↓
Open
↓
Welcome 2
↓
Welcome 3
↓
Exit
Scenario 3 – Never Engaged
Welcome 1
↓
No Open
↓
Welcome 1a
↓
No Open
↓
Welcome 1b
↓
Exit
Why This Journey Is Better Than the Previous Welcome Journey
Previous Journey:
Everyone receives same emails.
This Journey:
Different experience based on engagement.
Benefits:
✅ Better Open Rates
✅ Better Click Rates
✅ Reduced Email Fatigue
✅ Improved Customer Experience
✅ Higher Conversion Rate
✅ Personalized Onboarding
SFMC Components Used
| Component | Purpose |
|---|---|
| Data Extension Entry | New Subscriber Source |
| Email Activities | Welcome Communications |
| Wait Activities | Timing Control |
| Engagement Splits | Open/Click Evaluation |
| Join Activities | Merge Customer Paths |
| Exit Activities | End Journey |
Enterprise Enhancement
In real projects, after Welcome 1b, companies often update customer status:
EngagementStatus = Unresponsive
or move them into:
Low Engagement Segment
for future targeting.
Interview Explanation (5–8 Years SFMC)
"This is an engagement-based onboarding journey. New subscribers enter through a Data Extension and receive a Welcome email. After a wait period, an Engagement Split evaluates whether they opened or clicked the email. Engaged subscribers continue directly through the onboarding sequence, while non-engaged subscribers receive a reminder welcome email. A second Engagement Split evaluates engagement again. Subscribers who engage are merged back into the primary onboarding flow using a Join Activity, while those who remain inactive receive a final recovery email before exiting. This approach improves onboarding performance by adapting communication based on subscriber behavior."
Comments
Post a Comment