Everyone says their CDP activates in real time. But scratch the surface, and it’s mostly “real-time-ish” — fast at the edges, batch in the middle.

That wouldn’t be a problem if vendors were honest about it. Instead, we get bold claims about streaming ingestion, instant segmentation, and sub-second activation… even when the architecture under the hood can’t support it.

Real-Time at the Edges, Batch in the Middle

At Real Story Group, we’ve repeatedly tested and observed this pattern: vendors showcase real-time ingestion and webhook-based triggers. That demos great. However, once data enters their systems, “batch” processing takes over for many aspects. For example, enrichment happens on a schedule. Segments update overnight. Identity stitching may run hourly.

And that shiny activation layer? Often delayed or disconnected from what just happened upstream.

This is what we call being "real-time-ish."

What Real-Time Actually Requires

Here’s the kicker: for true real-time personalization or activation, every single step in the Martech pipeline (and not just the CDP) must operate in real-time.

• Ingestion: Sure, most CDPs support streaming
• Enrichment: Often delayed by third-party lookups or internal rule engines
• Identity Resolution: Frequently done in batches, especially for probabilistic models
• Segmentation: Typically runs on a cadence; sometimes hourly, often nightly
• Decisioning & Activation: Trigger-based, but not always synced with upstream freshness

If even a single stage introduces lag, your so-called "real-time" campaign is just a fast batch job.

But Are You Even Activating in Real-Time?

Here’s where the second fallacy creeps in. Even if your CDP could deliver data in milliseconds… would you actually use it that way?

• Are you dynamically adjusting your web content in-session?
• Are your emails triggered in real-time?
• Do you have creative variants ready to match behavior or intent instantly?

Most brands don’t.

Instead, we see:

• Static journeys built in orchestration tools
• Daily or weekly audience refreshes
• One-size-fits-all creative
• Manual campaign approvals and batch workflows

So let’s be honest: even if your CDP was lightning-fast, the rest of your marketing stack and process probably aren’t.

The Salesforce Case Study

Let’s remember the Salesforce Genie whistleblower complaint. One of the central issues was that Salesforce continued to market its Data Cloud (then called “Genie”) as a real-time CDP, despite much of it still being stitched together via batch processes and internal sync jobs. The illusion of real-time, until you scratched beneath the surface.

This is not unique to Salesforce. It’s an industry-wide pattern.

The "Right-Time" Alternative

Here’s what savvy teams do instead:

• Identify specific use cases where real-time truly matters (e.g., cart abandonment, fraud mitigation, high-intent lead routing)
• Set SLA benchmarks (e.g., <500ms response time for specific events)
• Let batch do the heavy lifting where it suffices (e.g., daily model updates)
• Focus on consistent data freshness and integrity, not just low-latency

What You Should Do

• Ask vendors to walk you through a real-time end-to-end use case, not just ingestion.
• Push for observability at each step: When was the data updated? When was the segment re-evaluated?
• Map your activation flows: where do you need speed, and where is "good enough" fine?
• Don’t confuse real-time data movement with real-time decisioning

Final Word

Real-time isn’t a feature. It’s a system-wide discipline. Most marketers don’t need it everywhere, but they do need to know where it breaks.

If your CDP promises zero-latency and sub-second decisions, remain sceptical. Ask them: "Real-time… all the way through?"

Want help decoding your vendor’s claims? That’s what we do. Check out RSG’s uncompromising CDP evaluations.