Braze brings Salesforce its hidden real-time edge

Salesforce is buying Braze.

On 20 October, Salesforce announced it had signed an agreement to acquire Braze for roughly $5.66 billion in enterprise value, or $47.50 in cash per share.

Cool, right?

The first reaction I saw in most feeds was a version of the same thing:

“Another marketing platform? Salesforce already has Marketing Cloud.”

Fair question. But it’s not the most useful one.

The better question about the Braze Salesforce deal is this: what does Braze do well that most of us find hard to do in the Salesforce stack today, and where would it plug in?

Salesforce’s press release gives us a surprising amount of detail on that. And Braze’s own documentation fills in the rest.

So, let’s have a look.

The Braze Salesforce deal in a nutshell

• The acquisition: ~$5.66bn enterprise value, $47.50 cash per Braze Class A share.
• Timing: expected to close in Salesforce’s fiscal year 2028, subject to Braze shareholder and regulatory approval.
• Specialities
  1. Real-time, event-streaming engagement
  2. Deep mobile and in-app channels
  3. AI decisioning across content, offers, channels and timing
  4. composable data plumbing, in from the warehouse and back out again
• The pitch: Braze is expected to complement all four layers of Salesforce’s architecture, not just Marketing Cloud.

First, what is Braze, and how is it different?

If you’ve spent your career in Marketing Cloud Engagement, Braze can look familiar at first glance. Journeys, segments, email, SMS, push.

But the design underneath is different. A few terms help:

• Event streaming — customer behaviour (an app open, a basket update, a payment) flows in continuously and can change a profile or a journey within moments, rather than waiting for the next scheduled import.
• Canvas — Braze’s journey builder. Roughly the equivalent of Journey Builder, but designed around those live events.
• BrazeAI — the umbrella for Braze’s AI features, including Operator, agents, Intelligent Timing, Intelligent Channel and Decisioning Studio.
• Currents — Braze’s outbound stream of engagement events (sends, opens, clicks and so on) to warehouses and other tools.

Salesforce describes Braze’s architecture as “cloud-native, event-streaming… optimized for high-volume, real-time B2C engagement”, powering “trillions of messages and journey actions each year”.

That’s the key distinction, and it’s the lens I’d use for the whole Braze Salesforce story. Some platforms are built around the campaign. Some are built around the moment.

1. Real-time, event-streaming engagement

This is the headline speciality in the Braze Salesforce deal, and the one Salesforce leads with.

What it is: Braze takes live signals from apps, websites and back-end systems, updates the profile continuously, and lets a Canvas react while the customer is still in the session.

Today in Salesforce: most of us build engagement around data extensions, scheduled automations and journey entry events. It works, but “real time” usually involves some engineering.

What Braze adds: behaviour-led journeys as the default, not the exception. Salesforce says the event-streaming architecture turns “live customer signals and data from cloud data warehouses and other platforms” into messages and journeys.

Where it’s expected to plug in: Data 360 for the customer context, Marketing Cloud for orchestration.

Watch-out: Futurum’s Keith Kirkpatrick puts it bluntly: “Salesforce will now run two engagement engines”. Which one owns a given journey is still an open question.

Example scenarios

• A food delivery app sees a basket abandoned at checkout and nudges in-app within the same session, not the next morning.
• A fitness brand notices a member hasn’t booked a class in 10 days and triggers a personalised push, with the email as fallback.

2. Mobile and in-app depth

If Braze has a reputation for anything, it’s this. And it’s the gap many of us feel most when a client’s app team joins the room.

What it is: channels that live inside the product, not just the inbox. Braze’s channel documentation lists in-app messages, Content Cards, Banners, push, plus email, SMS/MMS/RCS, WhatsApp, LINE, KakaoTalk and webhooks.

What Braze adds:

• Content Cards — “a highly targeted, dynamic stream of rich content”, embedded in apps and websites.
• Live Activities — iOS lock-screen updates (think delivery trackers), which Braze can start and update remotely via its Live Activities API.
• In-app messages and Banners — shown in context while the customer is using the product.

Where it’s expected to plug in: Salesforce says Braze’s “deep mobile and app capabilities, including in-app messages, personalized content feeds, and live updates” will work alongside email, web and messaging channels.

Watch-out: these channels need the Braze SDK in the app. So the mobile team, not just the marketing team, becomes part of the conversation.

Example scenarios

• A retailer’s app shows a Content Card with a member-only offer that disappears the moment it’s redeemed in store.
• A travel brand runs a Live Activity on the lock screen showing gate changes and boarding status.

3. AI decisioning with BrazeAI

Now this one is particularly interesting.

What it is: AI that chooses what to send, where and when for each customer. Braze lists Intelligent Channel, Intelligent Timing, Item Recommendations, Operator, agents and Decisioning Studio under BrazeAI.

What Braze adds: BrazeAI Decisioning Studio, which started life as OfferFit (acquired by Braze in 2025). Braze describes it as using reinforcement learning and contextual bandits to choose the message, channel, timing and incentive for each customer, continuously experimenting rather than relying on one-off A/B tests.

Where it’s expected to plug in: Salesforce says that bringing Braze’s AI decisioning together with “Salesforce’s customer context and Agentforce” would connect marketing to commerce, sales and service.

Watch-out: more automated decisions raise governance questions. Who approves the offer rules? Who owns the decision when the model picks something odd?

Example scenarios

• A subscription business lets the model choose between a discount, a free month or no offer at all for each at-risk customer.
• A bank tests which of five onboarding nudges, on which channel, gets new customers to set up a direct debit.

4. Composable data plumbing

This one is quieter, but for architects it might be the most useful.

What it is: Braze is built to work with data where it already lives. Its data ingestion guide describes two flavours:

• Persistent — Cloud Data Ingestion (CDI) syncs warehouse tables onto Braze profiles, as often as every 5 minutes.
• Zero-copy — CDI Segments and CDI Canvas triggers query the warehouse without writing to the profile.

And on the way out, Currents is “a real-time data stream of your engagement events” to warehouses, analytics tools and CDPs.

Where it’s expected to plug in: Data 360. According to the press release, Salesforce and Braze “share a commitment to an open, composable approach”, and Data 360 already leans heavily on zero-copy.

Watch-out: I couldn’t find an official native Braze ↔ Data 360 connector today. Current Salesforce links are mostly webhooks, APIs and third-party connectors.

Example scenarios

• Loyalty tiers stay in Snowflake and trigger a Canvas directly, without copying every attribute into Braze.
• Every send, open and click streams back via Currents so the service team sees the full message history.

Where Braze fits in the Salesforce ecosystem

Here’s the part of the Braze Salesforce announcement I found most telling.

Salesforce doesn’t frame this as “Braze joins Marketing Cloud”. It says Braze is expected to complement all four layers of its architecture: Data 360, Customer 360, Agentforce and SIForce.

Kirkpatrick at Futurum summarises the split neatly: “Data 360 supplies the customer data; Braze supplies the decisioning and the channels that deliver the message.”

The press release names SIForce but doesn’t explain it, so I’d wait for more detail before reading too much into that layer.

Here’s how the four specialities line up in a combined Braze Salesforce stack:

So what should we take away from the Braze Salesforce deal?

A few questions I’d keep handy for the next client conversation.

1. Which engine owns the journey?

For now, both do. Until Salesforce publishes a roadmap, decide per use case, not per platform. MarTech’s Constantine von Hoffman makes the same point: teams need to know “which system owns journey orchestration”.

2. Where does the profile live?

Data 360, Braze, the warehouse, or all three? The answer drives identity, consent and reporting, and it’s worth writing down before anyone builds anything.

3. Is the use case batch or behaviour-led?

A monthly newsletter doesn’t need event streaming. A basket-abandon nudge inside the app does. Sorting use cases this way is useful whatever happens next.

4. What changes before close?

Nothing, officially. The acquisition is expected to close in FY2028 and needs approvals. Braze’s CEO says they’ll “continue building as Braze”. So existing contracts and roadmaps stand for now.

The bigger picture

The Braze Salesforce deal is less about adding another tool and more about adding a speed.

Salesforce has the data layer, the CRM and the agents. What Braze brings is a mature, battle-tested way to act on behaviour in the moment, especially inside apps.

Will it be smooth? Well… that’s still the open question. West Monroe’s Alex Torgerson told TechTarget: “The strategic logic is sound, but the value hinges entirely on integration…and customer migration.”

So instead of asking:

“Should we move to Braze?”

I’d ask:

“Which of our journeys actually need to react in seconds?”

Because that’s the question the Braze Salesforce deal really puts on the table.

And that’s exactly where the real-time edge earns its place.

Want more on where Salesforce is taking marketing? Read my breakdown of smart features in the new Marketing Cloud Next.