Real-Time Audience Activation in Marketing Cloud Next

Most legacy marketing automation platforms process audience changes on a schedule — a batch job runs every hour, every 4 hours, or nightly, and contacts who qualify for a campaign enter it on the next batch cycle. This delay, often invisible to the team running the campaign, is actually a significant quality problem.

A contact who visits your pricing page at 9am and receives a relevant follow-up email at 9:15am is far more likely to engage than one who receives the same email the following morning. The signal is still fresh. The intent is active.

Marketing Cloud Next, built on Salesforce Data Cloud, processes audience qualification in near-real-time. This article explains how it works and which campaign types benefit most.

What "Real-Time" Actually Means in Data Cloud

Real-time in the context of Data Cloud and Marketing Cloud Next means "as fast as the data pipeline can process the event" — which, in practice, is typically 2–15 minutes from the triggering event to campaign entry.

The sequence:

1. A contact performs an action (visits a page, submits a form, changes a CRM field value)
2. The event is captured by the relevant data source (website tracking script, Salesforce CRM, or an API call)
3. Data Cloud ingests the event via a real-time data stream
4. Identity resolution updates the relevant Unified Individual
5. Segment membership is re-evaluated for the affected Unified Individual
6. If the Unified Individual now qualifies for a Segment-Triggered Flow, they enter the flow
7. The first email (or other action) in the flow executes

The 2–15 minute window is dominated by steps 3–5. The ingestion and segment evaluation happen continuously for real-time streams — there is no batch window.

[Screenshot: Comparison diagram of real-time vs batch audience activation timing]

A timing diagram showing two scenarios: Batch activation (event at 9am, batch run at 6pm, campaign entry at 6:10pm = 9+ hour delay) vs Real-time activation (event at 9am, stream ingestion at 9:03am, segment re-evaluation at 9:04am, campaign entry at 9:05am = 5 minute delay)

id: real-time-vs-batch-timing

Setting Up Real-Time Data Streams

The foundation of real-time activation is the data stream configuration. Data Cloud supports two stream types: batch (scheduled refresh at intervals) and real-time (continuous processing as events arrive).

For real-time audience activation, the data streams for the activation triggers must be configured as real-time:

Website Engagement stream: By default, the website engagement stream processes events in near-real-time as the tracking script fires. No additional configuration required — the stream processes page visits, form submissions, and custom events as they occur.

CRM data stream: The Salesforce CRM data stream can be configured for real-time processing using Salesforce's Change Data Capture (CDC). When CDC is enabled for the relevant objects (Contact, Lead, Account), field changes in CRM are propagated to Data Cloud within minutes rather than on a batch schedule.

To enable CDC for the CRM stream:

1. In Salesforce Setup, enable Change Data Capture for Contact and Lead objects
2. In Data Cloud, configure the CRM data stream to use CDC instead of full-object refresh
3. Validate by making a test field change in CRM and verifying it appears in Data Cloud within 5 minutes

[Screenshot: Real-time data stream configuration in Data Cloud]

The data stream configuration panel showing a Salesforce CRM stream with the processing mode set to 'Real-time (Change Data Capture)', the CDC objects listed (Contact, Lead, Account), and the last processed event timestamp showing a recent update

id: real-time-data-stream-config

Segment-Triggered Flows for Real-Time Activation

The primary mechanism for real-time campaign activation in Marketing Cloud Next is the Segment-Triggered Flow. When a contact enters (or exits) a segment, the flow fires automatically.

A Segment-Triggered Flow has three properties that enable real-time activation:

Entry trigger: A segment qualification change. A contact enters the flow when they newly match the segment criteria. A contact exits when they no longer match.

Re-entry rules: Whether a contact can re-enter the flow after previously completing it. For real-time activation use cases (e.g. pricing page visit), re-entry is often appropriate — a contact who visits the pricing page twice in two months should be eligible for the follow-up flow both times.

Entry evaluation frequency: How often segment membership is re-evaluated. For Segment-Triggered Flows connected to real-time data streams, this runs continuously.

[Screenshot: Segment-Triggered Flow entry criteria in Flow Builder]

The Flow Builder entry configuration showing a Segment-Triggered Flow with the entry segment set to 'Pricing Page Visitors - Last 24h', re-entry enabled with a 14-day minimum wait between entries, and the evaluation frequency set to continuous

id: segment-triggered-flow-entry

High-Value Real-Time Use Cases

Pricing Page Visitor Follow-Up

A contact who visits your pricing page has demonstrated commercial intent. The best time to follow up is while they are still actively considering. A real-time triggered flow that sends a targeted email within 10 minutes of a pricing page visit performs significantly better than a batch-processed campaign that reaches them the next day.

Segment criteria: Unified Individual where Website Engagement includes a pricing page visit in the last 24 hours AND no open Opportunity AND last outreach was more than 7 days ago.

Flow action: Single email with subject line referencing the pricing context, CTA toward booking a demo or a custom pricing conversation.

Demo Request Immediate Follow-Up

When a contact submits a demo request form, the highest-converting response is immediate acknowledgement followed by a confirmation of what happens next. With real-time activation, this follow-up can go out within minutes of form submission — not after a batch delay.

Segment criteria: Unified Individual where Website Engagement includes a demo form submission in the last 1 hour AND no existing active Opportunity.

Flow actions: Immediate confirmation email, followed by a Salesforce Task creation for the assigned SDR.

CRM Field Change Triggers

When a sales rep updates a Contact's field in CRM — changing their buying stage, their product interest, or their engagement classification — marketing can respond in near-real-time with an appropriate follow-up.

Example: Sales rep marks a Contact as "Champion Identified" → Data Cloud receives the CDC event → Segment re-evaluates → Contact enters a "Champion Enablement" flow with sales content and product deep-dives.

Segment criteria: Unified Individual where Salesforce Contact field "Champion Status" = "Champion Identified" AND no prior Champion flow entry.

[Screenshot: Flow triggered by a website engagement event]

A flow in Campaign Designer triggered by a website pricing page visit event, showing: entry condition (pricing page visit, last 24h), Email 1 (immediate send, pricing-relevant subject line), a 3-hour wait, an open/click branch, and two paths: clicked (route to demo booking confirmation) and not clicked (3-day wait before follow-up email)

id: website-event-triggered-flow

Account-Level Intent Signal Response

When a third-party intent data source sends a signal that a target account is researching your category, a real-time triggered flow can reach known contacts at that account within minutes.

This requires the intent data to be connected as a real-time Data Cloud stream (many intent providers offer webhook-based integration) and a segment that evaluates intent score thresholds.

Batch Activation Is Still Right for Some Use Cases

Real-time activation is not always the appropriate architecture. Batch processing makes more sense when:

• Campaign logic depends on accumulated behaviour over time (e.g. "contacts who visited 5 or more pages in the last 30 days") — a rolling window calculation is batch by nature
• Campaign size and timing are coordinated (e.g. a monthly newsletter that goes to your full database at a specific time) — batch send is the right model
• Processing cost is a consideration — real-time streams consume Data Cloud credits at a higher rate than batch streams; for non-time-sensitive activations, batch is more economical

Design your activation architecture based on the time-sensitivity of the trigger. Pricing page visits, form submissions, and demo requests are time-sensitive — use real-time. Monthly newsletters and quarterly re-engagement programmes are not — use batch.

Summary

Real-time audience activation in Marketing Cloud Next is achieved through real-time Data Cloud data streams combined with Segment-Triggered Flows. The combination enables campaign entry within minutes of a qualifying event — pricing page visit, form submission, CRM field change, or intent signal.

The use cases with the clearest ROI are high-intent triggers: moments where a contact is actively signalling buying consideration. For these use cases, the gap between batch processing and real-time processing is the difference between reaching someone while their interest is active versus reaching them after it has faded.

Want to set up real-time audience activation for your highest-intent signals? Pardive designs and implements real-time activation architectures for Marketing Cloud Next programmes. Book a free activation session.