A customer fills their cart, hesitates, and leaves without buying. If you learn about it tomorrow morning, the moment is gone. They have moved on, the impulse has cooled, and your gentle reminder arrives like a letter to an empty house. But if you learn about it within seconds, while they are still nearby, a small nudge can bring them back.
That gap, between tomorrow and now, is what real-time data in Data Cloud is all about.
The old rhythm: overnight batch
For a long time, data moved on a slow schedule. Systems gathered up the day’s activity and processed it overnight. You woke up to yesterday’s picture. For many things, that is perfectly fine. Yesterday’s sales totals do not change, and reviewing them in the morning works well.
But some moments only matter while they are happening. An abandoned cart, a shipment marked delayed, a support case suddenly escalated, a subscription about to lapse. By the next morning, the chance to respond helpfully may already have passed. Batch is patient, and patience is sometimes the wrong tool.
The new rhythm: real-time
Real-time ingestion brings data into Data Cloud almost the instant it occurs. Instead of waiting for a nightly run, the signal flows in within seconds. The platform’s unified profile updates while the event is still fresh, so what Data Cloud knows about a customer matches what is true right now.
Relevance has a clock on it. The same message that delights a customer in the first minute can annoy them a day later. Real-time data is how you stay inside that window.
This immediacy is not about speed for its own sake. It is about meeting people in the moment that matters to them.
Reacting with data actions
Bringing data in quickly is only half the story. The other half is doing something with it. This is where data actions come in.
A data action lets Data Cloud respond automatically when a condition is met. A cart sits abandoned for a few minutes, and a data action fires. A subscription status flips to “at risk,” and a data action signals it. Rather than a person noticing later and reacting, the platform itself reacts the moment the rule is satisfied.
So the full real-time loop looks like this:
- Something happens — a customer abandons a cart.
- Real-time ingestion carries that event into Data Cloud in seconds.
- The unified profile updates to reflect the new reality.
- A data action fires, triggering the right response while it still matters.
Each step is fast, and the speed is the whole point.
A bridge to platform events
If you have read about integration, this rhythm may feel familiar. In the Salesforce platform, platform events are a way for systems to announce “something just happened” and let others react immediately, rather than constantly asking “anything new yet?”.
Real-time data in Data Cloud carries the same spirit. Both are built on the idea that the moment of the event is precious, and the systems around it should respond to that moment rather than discover it hours later. If you understand platform events, you already understand the heartbeat behind real-time Data Cloud. They are cousins in the same family of thinking: announce, listen, react.
When real-time is worth it
A beginner’s honest question is, should everything be real-time? No, and chasing that would only add complexity. The skill is knowing which signals are time-sensitive.
Ask yourself a simple question about any piece of data: does its value fade with time? A customer’s lifetime total can update overnight and lose nothing. An abandoned cart loses almost all its value by morning. Reach for real-time where the answer is “yes, the value fades fast,” and let batch handle the calm, slow-moving rest.
Music taught me that timing is not a detail laid on top of a piece. It is the piece. The same note played a half-beat late is simply a different, lesser sound. Data is no different. The right message at the right second feels like care. The very same message a day late feels like noise. Real-time data is how Data Cloud keeps its timing true.
So as you grow with Data Cloud, picture this: data arriving the instant it is created, a profile staying honest minute by minute, and an action ready to fire while the moment is still warm. That is what it means for the platform to react the moment something happens.
Your next step
Continue exploring how data moves and acts inside Data Cloud:
- Data Streams: Getting Data Into Data Cloud — the ingestion that real-time builds on.
- Your First Segment in Data Cloud — putting reactive, fresh data to use.
- Platform Events Explained — the announce-and-react pattern behind real-time thinking.
- Browse more in the Data Cloud category.