Are companies moving from batch campaigns to real-time journey orchestration?

Yes, but by addition, not replacement. In Alium's verified buyer interviews, companies add event-triggered journeys beside their batch campaign calendar rather than retiring it, and about two in five of those describing the move have an established triggered program running. What holds the rest back is less the journey tool than the data feeding it, which often arrives overnight.

Based on verified interviews with the CRM, lifecycle and marketing-technology leaders who run batch campaigns and triggered journeys, at DTC and enterprise brands. Buyers are anonymized before publication; vendor names and views are reported as given. No vendor paid to appear or could edit this page.

Are companies moving from batch campaigns to real-time journey orchestration? Gradually, toward triggered journeys, and without retiring batch campaigns. A batch campaign goes to a selected audience on a planned schedule; a triggered journey starts when a customer's action or a condition qualifies them; real time is how fast that happens, and many triggers still run on data refreshed hourly or overnight. Of the companies describing the move, about two in five have an established triggered program in their latest interview; the rest are evaluating, migrating or launching first journeys. None of the established ones says it has stopped batch sends. These are statuses within our interviews, not adoption across the market.

2 in 5
Companies describing the move that have an established triggered program (stage 3 below); the rest are evaluating, migrating or launching. Each counted once, by latest interview; not a market share.
None
Companies with an established triggered program that say they have stopped batch campaigns. The batch calendar runs beside the journeys.
6.2/10
Adobe Journey Optimizer's average buyer rating, the lowest in the table below. Several large companies launching event-triggered journeys in 2025 and 2026 name it, and describe the data work around it as the hard part.

How far have companies got in moving off batch campaigns?

Each company is placed in one stage by its latest interview. Stage 1 is a planned or evaluated move. Stage 2 is a migration or an initial launch with only some journeys live. Stage 3 is an established triggered program running as part of ongoing marketing, and it is the only stage the two-in-five figure counts. Stage 4 would be retiring batch campaigns. A planned completion stays a plan until a later interview confirms it.

Stage 1

Planned or being evaluated

The batch calendar runs the program, and moving to automated, behaviour-driven journeys is a stated goal or an open evaluation.

A health insurer, a parts distributor, a health system, a discount retailer
Stage 2

Migrating or launching

A migration or first launch is under way. Some journeys may already be live, but not yet an established program; batch still carries much of the work.

An airline, a hotel company, a subscription food brand, an insurer's B2B team
Stage 3

Established triggered program, beside batch

Welcome, abandonment, post-purchase and win-back journeys run as part of ongoing lifecycle marketing, beside scheduled sends. This is the stage the two-in-five figure counts.

Several apparel retailers, a global restaurant chain, a specialty retailer, a healthcare services company
Stage 4

Batch retired

No company in these interviews describes this stage.

Stages describe each company's latest interview. They are not a forecast, and stage 4 may exist at companies we did not interview.

The aim is old, and it reads the same every year. A hotel company's email director said in January 2024 that it still does "a lot of our brand initiatives through that batch and blast strategy" while trying to get off it. A DTC consumer brand's lifecycle director put the 2025 version as "moving out of just our batch and blast campaigns and moving more into an automated strategy that responds more intelligently to actions people are taking." A health insurer said in March 2026, "We want to begin to move from that old batch and blast type of marketing estate to the always-on next best action method of marketing." One bank's email lead has named the same goal, data clean enough to orchestrate across channels from, in interviews in 2024, 2025 and 2026.

Where the move has happened, it usually came with a platform change. The completed moves in these interviews mostly arrived with a new messaging platform: off an older marketing cloud or email tool and onto Braze, Bloomreach, Klaviyo, Iterable, Cordial or Bluecore, or onto Adobe Journey Optimizer inside an existing Adobe stack. A specialty apparel retailer's chief marketing officer credits its new email vendor with getting it "away from batch and blast to a much more behavioral triggered email program." A consumer brand "migrated all of our always on programs and just those journeys from Salesforce," replicating them and then enhancing them on the new platform. A specialty retailer chose its new platform partly so "our journeys consist of paid media and social and push" as well as email and SMS; it was warming its sending reputation in February 2026, said in May that it had transitioned earlier in the year, and in August was working on getting full use of it.

Migrations take longer than launches. A global restaurant chain ran cart-abandonment journeys on its newer journey tool while most sends still went through its older campaign engine. In August 2025 it planned to retire that engine the following year, and in February 2026 moving completely off it was still one of the year's initiatives. In October 2026 its marketing-technology product lead named the newer tool as the company's email platform and did not mention the older one; the move appears to have happened, though that interview does not say so directly. An airline's customer-experience head said in October 2026 that "journey orchestration was launched about two months ago" and that "we have yet to see the full impact," with the service use cases not yet built. The airline is an early launch, and it is written up here as one.

Do triggered journeys replace batch campaigns?

Not in these interviews. The triggered program is added to the batch calendar, and the two often run in different tools. Several apparel retailers send batch campaigns from one platform and behavioural triggers from another, and a children's apparel brand runs its batch and welcome emails in Klaviyo while a separate vendor builds and runs its abandonment triggers. A specialty retailer listens to web and app events in real time for its triggered messages, "So that's working really well. And then we have batch campaigns" built from a different part of the same stack.

Buyers describe the batch side as a choice rather than a leftover. A handbag brand's CRM director describes a limited-edition holiday launch sent to everyone engaged: "sure, I'll send that as a one-time thing as a marketing send, but it won't be part of my trigger journey." A healthcare services company whose program is now "overall triggered" still sends the occasional broad email for demand generation: "batch and blast is a number one no-no, but when you don't have another way, sometimes you just have no other choice."

"Because I'm sending batch and blast. You're sending triggers. And SMSs are going out potentially to the same customer." The retailer's CRM runs across three platforms, and the buyer expects to have to solve for how many times it reaches each customer, whether with one provider or another arrangement. Senior Director, Digital Marketing · apparel retailer · Mar 2024

That is the risk when batch, triggered and SMS programs run through different systems without shared contact rules: each platform may cap its own frequency without seeing what the others sent. The problem is not running both, but whether the systems share customer identity, suppression, send history and priorities. Journey orchestration, described on what is customer journey orchestration, can coordinate those decisions, but only for the systems and events it can see.

This is the average buyer's picture. What does your stack need?A free, peer-powered checkup returns a shortlist for your stack and your next steps.
Start my checkup →

What stops companies moving from batch campaigns to real-time journeys?

The journey tool is rarely the reason. Buyers who have bought one describe three things around it: data that arrives in batches, the content and people every triggered flow needs, and the work of connecting the journey tool to everything else.

Data arrives in batches, so the journey cannot be real time. The same retailer's marketing-technology engineer said in March 2025: "we do have a technology which supports real-time, but we really don't have a technology or a backbone to bring that data to the real-time system." A store registration, in its example, means "the data will be flowing overnight and not real-time to CDP." A telecom company's personalization manager describes the same split inside one stack in August 2026: warehouse data reaches its outbound campaign tool through federated access, close to real time, while the feed to its offer-decisioning platform "is a batch process, not a federated access, so it's not very real-time. This is a daily batch process." A furniture retailer's CRM director rates its data-enrichment partner lower for the same reason, because that data still arrives in batches and some of it lags.

The company's warehouse events reach its messaging platform on a schedule: "We use it to bring over our events hourly from Snowflake to Iterable." That was enough to stand up a triggered lifecycle program quickly, but not for everything: "We need real-time events for anything having to do with visits." Head of Marketing, Lifecycle and Customer Engagement · healthcare services company · Feb 2026

The data problem also shows up after launch. A health insurer's former marketing-operations lead says "one of the first omnichannel journeys that was launched had to be rebuilt. It just was not processing fast enough," and needed hours of watching to confirm each step ran.

Every triggered flow needs content and a person to build it. A children's apparel brand handed its abandonment triggers to a vendor because "To build out five different trigger flows and get them all done by our creative team, set up by our Email Marketing team, which is just me, was not really feasible." A handbag brand says right-message, right-time campaigns "are harder to maneuver because it requires a lot more dynamic content." A multi-brand apparel company's CRM director has put work with an analytics vendor on the back burner while training a new hire on the batch program: "We have a very extensive marketing calendar of batch emails and batch SMS that go out, and that seems to take priority over everything else."

Connecting the pieces takes skill the marketing team may not have. A software company's growth lead says "Building a sophisticated journey requires familiarity with data schemas, liquid logic, and event structures." That specialty retailer builds journeys in one tool and sends push and SMS through another, and has to define a new custom event for every campaign to pass between them. A bank's lifecycle director describes building "the real-time triggers and logic in a different place than Salesforce Marketing Cloud," and calls the result "more of an organizational gap" than a tool problem.

Do companies actually need real time?

Buyers disagree, and the disagreement is useful. A travel company's CDP director says "people expect that things are happening almost in real time when they do something," and is looking at fresher data for that reason. Months later, rating that vendor's new real-time segmentation, the same company's CDP director said "I think the jury's out on real time," because the feature was too new to judge.

The counter-current: real time with no use case

A global hotel group's data-product lead says that since joining, the instruction has been that whatever the team builds "it's got to be real-time and streaming, and there's no use case for it. No one is asking for it." The team is now putting it to more sophisticated uses. A bank's lifecycle director describes its own personalization the way several buyers do: "things are not real time, they're near real time, that's what we like to say, but they're not real time."

The healthcare services company shows why triggered and real time are separate requirements. Its hourly warehouse sync supports most of its automated lifecycle program, while visit-related messages need events delivered sooner. What matters is the delay from the customer's action to the message, through data capture, identity matching, audience qualification and sending, not whether the journey platform accepts events. A program can be automated without being real time; real time pays where a late message would be irrelevant or wrong.

What kinds of systems orchestrate cross-channel campaigns from a data warehouse?

Three warehouse-connected arrangements appear in these interviews. They differ in where the data sits, how it reaches the journey platform and how often it is refreshed. None is real time just because a warehouse is connected; freshness depends on the whole path from event to delivered message.

A sync from the warehouse into the messaging platform. Attributes, events or audience membership are copied from the warehouse into the platform on a schedule, by a reverse-ETL tool or the platform's own ingestion, as in the healthcare company's hourly feed. Braze's Cloud Data Ingestion documentation says the shortest interval set in the dashboard is 15 minutes by default, that syncs can run as often as every five minutes through Braze Support or a customer success manager, and that its Trigger a sync endpoint runs one on demand (checked November 2026). Those are sync settings, not end-to-end latency: the warehouse has to receive and prepare the data first. Schedules and lag are covered on what is reverse ETL.

A platform that queries warehouse data to build audiences. Federated access lets a journey or activation platform build audiences from data held in an external warehouse without first copying it into its own store. Adobe's Federated Audience Composition documentation describes building audiences from an enterprise data warehouse without persisting the underlying data, with the result saved in Experience Platform as an external audience for Real-Time CDP or Journey Optimizer; its FAQ lists Real-Time CDP and Journey Optimizer Prime or Ultimate packages, and a purchase of the feature itself, as requirements (checked November 2026). Audience refresh and journey-entry rules still decide when someone can receive a message. The specialty retailer above uses warehouse-built audiences for batch sends while separate event-triggered journeys run alongside, and the telecom company uses federated access for outbound campaigns.

A warehouse-native CDP or activation layer. The customer data platform builds audiences on data where it already sits in the warehouse. A consumer app company moving off a CDP that needed batch file uploads expects it to "activate different campaigns on real-time data, basically as soon as we can get the data into our data warehouse." That is an expectation from its trial, not a measured result: latency still depends on ingestion, transformation, audience evaluation and the messaging platform, which a warehouse-native CDP does not necessarily replace.

Which platforms are behind the moves?

These are the platforms buyers in these interviews name as the engine of their triggered journeys, with each platform's average rating from every buyer who rated it. How buyers expect orchestration to sit in the stack, and what they pair with it, is on the journey orchestration definition.

Average buyer ratings (1–10) across all Alium interviews that rate each platform, through November 2026. Each rating comes from that platform's own buyers, a different group for each row; a higher rating beside a move does not mean the move improved anything.
Platform Buyer rating Where it shows up in these moves
Klaviyo 7.7 Where several ecommerce brands moved for event-based flows their previous tool could not run, and where some keep their batch sends while another tool runs triggers.
Braze 7.5 The destination of a completed migration of always-on journeys, and the planned home for other companies' triggered messaging. Salesforce signed an agreement to acquire Braze on October 20, 2026; the deal had not closed.
Bloomreach 7.3 Chosen by retailers for multi-channel journeys and triggered campaigns, including paid media, social and push beside email and SMS.
Cordial 7.2 Where retailers run their journeys, triggers and audience selection, in some cases with SMS sent through a separate provider; the destination of a completed move for triggered sends.
Iterable 7.0 Runs a healthcare services company's mostly triggered lifecycle program, and is the destination of an enterprise migration under way in 2026.
Salesforce Marketing Cloud 6.8 Runs journeys at several enterprises, and is the platform several of the completed moves above left.
Bluecore 6.7 Sends behavioural triggers for several apparel retailers, beside a separate batch tool at some and with batch sends in the same platform at others.
Adobe Journey Optimizer 6.2 Named at several large companies launching event-triggered journeys in 2025 and 2026, in some cases while an older campaign tool still sent many of their messages.

Want this checked against your own stack?

Start my checkup →

What this means if you are planning the move

Should companies replace batch campaigns with real-time journeys? The companies here did not describe that as an end state. They added triggered journeys and kept scheduled sends for promotions, launches and broad communications, and some of those journeys run on hourly or overnight data. The decision is which messages benefit from triggered timing, how fresh their data must be, and how the two programs are coordinated.

Our recommendation, not a practice buyers describe: list each planned journey with the event that starts it, the data and consent it needs, its channels and the longest delay it can tolerate. A visit or abandonment message may lose its point within the hour, while a replenishment or win-back audience can wait for a daily refresh. Then test the whole path with real events, from the customer's action through the warehouse or CDP to qualification and send, including late, duplicate and unmatched events, and measure the delay end to end rather than trusting one component's refresh interval.

Before launching beside the batch calendar, name who owns each journey's content, setup, monitoring and failed triggers, and who owns contact frequency and priority across email, SMS and push, including what happens when a batch send and a trigger qualify the same customer at once. To judge whether a journey earns its keep, hold out a comparable group of eligible customers who do not receive it and compare outcomes over the same period, and report that separately from delivery metrics such as sends, trigger latency, completions and platform-attributed revenue.

What not to read into this

The shares on this page count companies in our interviews that describe their own batch campaigns or a move toward triggered journeys, each once by its latest interview. They are not adoption rates or market shares, and most companies interviewed did not discuss the subject. None has stopped batch means none of these buyers said so, not that no company anywhere has. Dates a buyer expected a migration to finish are reported as plans. And the ratings come from each platform's own buyers, so they do not show whether any move improved results.

Common questions

Are companies moving from batch campaigns to real-time journey orchestration platforms?

Gradually, and without retiring batch campaigns. In Alium's buyer interviews, about two in five of the companies describing a move from batch-led campaigns toward triggered journeys have an established triggered program running in their latest interview; the others are evaluating, migrating or launching first journeys, and some of those already have a few triggered messages live. None of the established ones says it has stopped batch sends. Triggered is not the same as real time: many of these journeys run on data refreshed hourly or overnight. These are statuses within our interviews, not adoption across the market.

What is the difference between batch campaigns and journey orchestration?

A batch campaign sends one message to a selected audience on a planned schedule, such as a weekly promotion or a product launch. A triggered journey starts or advances when a customer's action or a condition qualifies them, such as an abandoned cart, a sign-up or an unanswered email, often across email, SMS, push and other channels. Real time describes how quickly that happens, and a triggered journey can still run on data refreshed hourly or overnight. Buyers in these interviews run both: one handbag brand still sends its one-off collection launches as batch sends and keeps them out of its triggered journeys.

What stops companies moving from batch campaigns to real-time journeys?

Mostly data that arrives in batches. Buyers describe customer data reaching the journey tool overnight, once a day or once an hour, which a triggered journey cannot outrun. Content and team capacity come next: every triggered flow needs its own creative and setup, and a busy batch calendar takes priority. Integration work between the journey tool and the systems that send the messages, and the technical skill needed to build complex journeys, follow.

What kinds of systems are used to orchestrate cross-channel campaigns from a data warehouse?

Three arrangements appear in buyer interviews: a sync that copies warehouse data into the messaging platform on a schedule, through a reverse-ETL tool or the platform's own ingestion; a platform that queries the warehouse to build audiences without copying the underlying data, such as Adobe's Federated Audience Composition; and a warehouse-native customer data platform that builds audiences on data where it already sits. None is real time just because the warehouse is connected: freshness depends on the whole path from event to message, which buyers describe as anything from near real time to once a day.

Do companies need real-time journey orchestration?

Buyers disagree. Some say customers expect things to happen almost in real time, and a healthcare services company needs real-time events for anything to do with its visits while an hourly sync serves the rest of its program. Others are sceptical: a global hotel group's data lead says real time is being asked for with no use case behind it, and a bank's lifecycle director describes its own setup as near real time rather than real time. The useful measure is the delay each journey can tolerate between a customer's action and the message.

Related reading: what is customer journey orchestration; what is a customer engagement platform; what is reverse ETL; why companies switch email platforms; and how long an email platform migration takes.

Get a checkup on your tech stack

A checkup for your marketing stack, built from hundreds of verified buyer interviews: what matters most to you, a shortlist for your stack, and your next steps.

Start my checkup

Free · no password · your answers are anonymized before they inform research like this.

Want to come back to this?We'll email you a link to this page, so it's easy to find later or forward to your team.
Methodology. Alium conducts verified interviews with software buyers — the CRM, lifecycle, ecommerce and marketing-technology leaders who select and operate these platforms. This page draws on interviews from January 2024 through November 2026 in which a buyer describes their own company's batch campaigns, triggered or event-driven journeys, or a move from one toward the other, found by searching what buyers said for batch, trigger, journey and real-time language and then read answer by answer. Each company was counted once, by the stage its latest published interview supports: a planned or evaluated move; a migration or initial launch with only some journeys live; or an established triggered program running as part of ongoing marketing. Only the last counts toward the two-in-five figure. Companies that described batch campaigns without any move toward triggered journeys are not in the count. Where a company was interviewed more than once, the interviews are read in date order, and a date a buyer expected is reported as a plan. Interviewer questions that themselves named journey orchestration were set aside when judging whether the topic is growing, because that wording entered the interview script in 2026. Ratings are average buyer ratings across all interviews that rate each platform. Buyer identities are verified at interview time and anonymized before publication; vendor names are reported as given. No vendor paid to appear or was able to edit this page.