Real-time marketing’s most useful job may be stopping you from doing something embarrassing.
Real-time marketing has been sold with a lot of fireworks. Instant personalization.
Immediate activation. The perfect message in the perfect channel at the perfect moment.
That all sounds wonderful. In practice, one of the most valuable real-time decisions is often much quieter:
Don’t send that email. The customer completed the purchase. Stop the abandoned-cart journey.
A serious service case was opened. Pause the upsell. The subscriber changed her consent. Update her eligibility.
A prospect asked about financing. Route the request while she is still actively considering the purchase. The value isn’t simply that the company can communicate faster.
It’s that the company can recognize when the customer’s situation has changed and adjust before the next interaction makes the brand look disconnected.
Batch processing isn’t the villain
There is nothing inherently wrong with batch processing. A weekly report can be weekly.
A quarterly planning audience doesn’t need to refresh every few seconds.
A large historical data set may be perfectly appropriate for a scheduled load.
The problem starts when a scheduled process is being used for a decision whose value expires before the file arrives.
A customer changes her consent at 10:00 a.m. The activation platform receives the change overnight.
For the rest of the day, the company is working with information that is already wrong.
A prospect requests an appointment. Sales receives the request the next morning.
By then, the prospect may have booked somewhere else. A customer completes a purchase.
The marketing journey doesn’t find out for four hours. The cart reminders continue. Batch isn’t bad.
Batch is bad when the customer moment expires before the business knows it happened.
Don’t start by asking what can be real-time
Platforms such as Salesforce Data Cloud can support streaming data, real-time identity and rapid activation when the architecture is configured for those use cases.
That capability is important. It is also easy to overengineer.
I wouldn’t begin by asking, “How do we make everything real time?”
I would ask:
Where is delay currently costing us money, trust or compliance?
That question creates a very different roadmap.
It focuses the investment on the moments where speed changes the result.
Not every click deserves an immediate reaction.
Not every profile attribute needs to update in milliseconds.
Not every audience needs to be recalculated continuously.
The goal is not to make the entire organization move faster.
The goal is to help the organization respond at the speed the customer moment requires.
Four questions for every real-time use case
Before building a real-time journey, work through four simple questions.
What happened?
Be precise.
Did the person view a product once?
Did she return three times?
Did she request an appointment?
Did she complete the purchase?
Did she change her consent?
Did a service case reach a particular severity?
A vague signal usually creates a vague and inconsistent response.
Who did it?
Can the business identify the person with enough confidence to act?
Is she an anonymous visitor?
An existing customer?
A contact connected to a valuable business account?
Someone who has already purchased?
Someone with an open complaint?
Someone who has not consented to the communication being considered?
Speed without context is where companies get themselves into trouble.
What should change?
Should the person enter a journey?
Should she leave one?
Should a salesperson receive a task?
Should the website experience change?
Should marketing pause?
Should a service team be alerted?
The answer is not always another message.
Sometimes the smartest automation is a suppression.
Where should the change appear?
The action may need to occur in email, SMS, the website, sales, service, a store or several places at once. This is where architecture matters.
A real-time decision is not very useful when the signal reaches one channel quickly but the rest of the business continues operating with the old information.
Put a clock on the customer moment
Here is a simple exercise I use when teams are trying to prioritize real-time use cases.
1. Write down five customer events that matter to the business.
2. Next to each one, write the maximum acceptable delay.
3. Note the ideal delay. The longest delay the business can tolerate before the information loses value or creates risk.
A consent change may need to affect activation very quickly. A completed purchase should update an abandoned-cart experience within minutes.
A high-intent financing inquiry may need a prompt human response.
A weekly audience used for planning may be perfectly fine refreshing overnight.
This exercise keeps the team from treating “real time” as one universal requirement.
It also helps prevent an expensive architecture from being built around use cases that don’t need it.
Start with moments that lose value quickly
For most organizations, I would begin with a small number of high-value moments.
Consent and communication eligibility should be near the top of the list. A privacy decision should reach the systems responsible for activation as quickly and reliably as the business can support.
Completed purchases should influence cart, cross-sell and post-purchase communications.
Serious service issues should change the promotional experience.
Appointment requests, financing questions and product-availability inquiries should reach the right person while the customer’s intent is still active.
These aren’t flashy use cases. They are the moments customers notice.
Real-time can make a bad decision worse
Real-time technology does not repair weak data. It does not fix a duplicated profile.
It does not clarify an ambiguous consent rule. It does not decide who owns the response.
It simply moves the information and executes the decision faster. That means a duplicate customer may receive two immediate messages instead of two delayed messages.
A poorly defined behavior may trigger a journey that should never have started.
An incorrect consent rule can create a problem before anyone has time to catch it.
Real-time is not a permission slip to automate assumptions.
Before activating a use case, make sure the signal is understood, the identity is reliable enough, the consent is current, the decision has an owner, and the outcome can be measured.
The faster the process moves, the more deliberate those decisions need to be.
Relevance really does have a clock
Some customer moments stay useful for days. Others lose value in minutes.
A financing request is different after the customer has already made a decision.
An appointment request is different after she has booked with a competitor.
A product search is different after the purchase is complete.
A complaint should change the customer experience before the next promotion arrives.
That is the practical value of real-time marketing. It isn’t an endless race to send faster.
It is the ability to notice that the situation changed and respond while the response still matters.
Bring one moment with a clock on it
At Mar Dat,we help teams distinguish between what truly needs to happen in real time, what can happen near real time and what is perfectly fine remaining on a scheduled process.
That honest answer can save a company a lot of money and complexity.
Bring one moment where timing matters. A purchase. A consent change.A service escalation.
An appointment request. A high-intent action. We’ll map what happened, who did it, what should change and where the action needs to show up.
These three problemsare connected. When systems don’t share information effectively, the business pays a sync tax. When the same person appears as several unrelated records, every team works with part of the truth.
When customer information arrives too late, the company responds after the moment has changed. Architecture, identity, and real-time activation can feel like technical topics.
Your customer experiences them in very human ways.
She experiences them when you remember what she bought.
When you recognize that she already has a relationship with the company.
When you stop a message that no longer makes sense.
When you respond while she still needs help.
I have spent years helping teams turn complicated technology environments into something marketers can use, leaders can trust, and customers don’t have to think about.
When these examples feel familiar, don’t prepare a polished presentation. Send me the screenshot. Bring the broken journey. Show me the two dashboards that disagree.
