UC1 : The Cart That Was Never Lost: A Story of Identity, Timing, and Experience

Today, I’m trying something new. A different way of writing. A different way of explaining.

Instead of breaking things into steps and diagrams, I’ve told this as a story — how a simple cart abandonment actually unfolds behind the scenes. This isn’t theory. This is a real-world use case, the kind most of us have worked on… but rarely explained this way.

If you’ve ever wondered:

• Why some journeys feel perfectly timed

• How systems “recognize” the same customer across channels

• What actually happens between data and engagement

…this one is for you.

Curious to know if this storytelling style works for you —does it make things easier to understand, or should I go back to the usual format? Would genuinely love your thoughts in the comments

Cart Abandonment

Use case covers Marketing cloud engagement with Data 360.

A Story the Customer Never Sees — But Always Feels

It’s 9:10 PM.

Ananya is browsing a retail website on her laptop. She wasn’t planning to buy anything, but a pair of shoes catches her attention. She adds it to her cart, explores a few more options… and then closes the tab.

No purchase. No checkout. Just another incomplete session.

For her, it’s nothing.

For the system, it’s the beginning of a story.

The System Sees Activity — Not a Person

At this point, the website has captured everything it needs:

a product view, a cart addition, a session trail.

But something is missing.

There is no identity.

The system doesn’t know who this is. It only knows that someone showed intent.

This data quietly flows into Salesforce Data Cloud, where it sits as behavioral information — useful, but disconnected.

The system is waiting.

The Moment Identity Becomes Real

Later that night, Ananya opens the mobile app.

This time, she logs in.

That single action changes everything.

Now the system has a key — an email, a known identifier — something it can anchor to.

Behind the scenes, Data Cloud connects:

• the anonymous web session

• the mobile login

• her existing CRM profile

What looked like separate interactions now becomes one continuous story.

This is the moment identity resolution does its work — not loudly, not visibly, but critically.

A Decision Is Made — Quietly

No message is sent yet.

There is no immediate reaction.

Instead, the system evaluates:

There is a cart.There is no purchase.The activity is recent.The customer is now known.

This is not campaign logic. This is decisioning.

A segment forms silently — not as a list, but as intent.

The Response Is Chosen, Not Triggered

This insight moves into Salesforce Marketing Cloud.

Now the system is no longer asking what happened.

It is asking what should happen next.

Ananya is active on mobile, so the first response is not email.

It is a push notification.

Not immediate. Not intrusive. Just well-timed.

“You left something behind.”

The System Waits

There is no rush to follow up.

If she doesn’t act, the system gives space.

After a short interval, it reaches out again — this time through email.

The message reflects what she saw earlier. Not generic, not repeated, just familiar.

At this point, the system is not increasing pressure.

It is maintaining context.

What the Customer Experiences

From Ananya’s perspective, this feels simple.

A reminder at the right time.A message that makes sense.No overload. No confusion.

It doesn’t feel like multiple systems reacting.

It feels like one brand paying attention.

What Actually Happened Behind the Scenes

What looks simple is rarely simple.

Behind this experience was a sequence of decisions:

• behavioral data captured from multiple channels

• identity stitched at the right moment

• segmentation based on real intent

• orchestration across channels

None of this was visible.

But all of it was necessary.

The Shift That Matters

Before this approach, cart abandonment is reactive.

A trigger fires, a message is sent, and the process ends there.

With Salesforce Data Cloud and Salesforce Marketing Cloud, it becomes something else.

The system stops reacting to events.

It starts understanding people.

Final Thought

From the outside, this is just a reminder.

From the inside, it is a connected system interpreting intent, making decisions, and responding with context.

That is the difference between sending messages…

…and creating experiences.