Salesforce is buying Braze. What changes for Marketing Cloud and Braze customers

Salesforce will pay $47.50 a share in cash, a 58 percent premium on the previous close, and expects to close in its fiscal 2028, February 2027 to January 2028 (Salesforce press release). Marketing Cloud Engagement came from the ExactTarget acquisition in 2013, Marketing Cloud Next launched in Spring 2024, and Braze would be the third engagement engine under one owner.

One owner for three engines raises the customer's question: does it make the stack simpler, and which commercial capital do you build yourself?

What did Salesforce announce, and what changes now?

The announcement describes no customer migration. It is an agreement, subject to a Braze shareholder vote and regulatory approvals (Braze 8-K). Salesforce says Braze will keep its name and its founders inside Marketing Cloud, and plans to connect it to Data 360, Customer 360 and Agentforce. Both companies promise an "open, composable" approach with cloud data warehouses as an input.

No combined roadmap and no pricing or packaging change has been announced. The absence of an announcement is no promise. Products and terms can change before a close, and your contract is governed by its own terms.

Where does Braze sit next to Marketing Cloud Engagement and Marketing Cloud Next?

After a close, Salesforce would own three engagement engines with three person records. Its help centre already carries an article titled "Which Marketing Cloud Product Do I Have?" (Salesforce Help, 31 July 2026). The table shows the products as documented today. Integration is an announced plan without published detail.

Sources: Salesforce Help above, Marketing Cloud Engagement API imports and file imports in Automation Studio, Braze data ingestion options, Braze GDPR FAQ, Salesforce Hyperforce security, privacy and architecture. The "Editorial reading" row is my judgment rather than documentation.

Marketing Cloud Next requires Sales or Service Cloud, so it is sold as part of a Salesforce estate. Braze requires neither, which helps explain why Braze can add reach that Next does not. Gartner's September 2026 Magic Quadrant for Multichannel Marketing Hubs names Braze, Salesforce and Adobe as Leaders, with Braze positioned highest on Ability to Execute and furthest on Completeness of Vision (Braze).

Which decisions stay with the customer?

Integration does not settle who decides. Whatever Salesforce builds, you still choose where identity and consent live, which journey wins when two builders want the same person in the same hour, and where decisions and outcomes land so an auditor can read them.

Take one scenario. A customer buys, withdraws consent for profiling and opens a service complaint before lunch. Three systems may hold a version of that person, and the value of the combination depends on how reliably those events reach every running journey. A withdrawal of profiling consent affects the actions that depend on it. One documented route shows the kind of setting involved. Braze's recurring warehouse syncs through Cloud Data Ingestion can be configured down to 15 minutes, or 5 minutes via support, and a sync can also be started by API; the SDK and API route is near real time (Braze documentation). If the withdrawal reaches Braze only through a scheduled warehouse sync, the next profiling-based decision can run before it lands. The interval is a configuration choice with a legal consequence.

Four tests show where you stand: how fast new information changes the next action, how fast an action stops after a withdrawal, what happens when two journeys hold conflicting offers for one person, and whether decisions and outcomes return to one history you could show a regulator.

What should European customers check in addition?

Hosting first. Braze documents EU hosting on AWS in Frankfurt with backups in Ireland, with transfers under the Data Privacy Framework and the EU and UK standard clauses (Braze GDPR FAQ). Salesforce offers the Hyperforce Operating Zone, formerly the EU Operating Zone, whose coverage depends on the services in your contract (Salesforce). No change to Braze's hosting has been announced. If hosting or sub-processors change after a close, what follows depends on your data processing addendum and master agreement: notice and objection rights, a change-of-control clause, or neither. Read yours now.

Then consent. Decisioning Studio Go, Braze's self-serve decisioning agent, is email-only in its current tier, optimises the number of unique customers who click, and learns from the audience's email engagement (Braze FAQ). Click tracking is not the same as pixel tracking: the CNIL says tracking links are not directly covered by its pixel recommendation. The practical question remains whether the collection and subsequent use of those signals are covered by the relevant purposes and permissions. For pixels, the CNIL's recommendation published on 14 April 2026 requires purpose-specific and evidenced consent, and allows one consent to cover sending and tracking when the purposes are connected, such as a personalised newsletter (CNIL FAQ, questions 1 and 20). Italy's Garante set 29 October 2026 as the date by which notices, consents and revocation must be adapted (Garante, 5 October 2026). The rules per platform are in the pixel consent guide. For the decisioning engine the question is whether the engagement it learns from was collected under a purpose that covers per-recipient optimisation, and whether you can show it.

Where does the value build up?

My reading of the deal is that Salesforce is buying capacity to turn customer context into action. In the Value Gravity™ model that capacity sits in the orchestration layer, between the governed foundation and the experience the customer sees. The layer assignment is my interpretation.

Value builds up on both sides of a contract. For the vendor, every journey, decision rule and identity match that lives only inside its tool is retention. For the customer, those journeys and rules can create value inside the platform. The question is how much of that value survives a change of platform or ownership. Readable history, transferable logic and clear responsibility make it easier to retain. Consolidation can lower integration cost and increase dependency at the same time.

In a recent carve-out, we found records of people who had asked to be reminded the following year. Those requests represented potential future business. But when we mapped the data for reuse, the original opt-in wording had not been retained, or the records had arrived through third parties without enough supporting evidence. There was no clear owner who could resolve the uncertainty. We decided to leave those people alone rather than risk using their details beyond what they had agreed to. The data had survived. Our ability to act confidently on it had not.

Commercial value travels with the context, the evidence and the responsibility that come with the data. Braze's own documentation shows what portable can look like. Decisioning Studio Go writes an agent ID, a regime flag (AI-driven or random control) and a decision ID to every send event, and Braze tells customers to confirm that their Currents or data export carries those fields, then join them in their own warehouse (Braze, measuring Decisioning Studio Go). These identifiers can link exported sends to decisions and outcomes. They do not, by themselves, reconstruct the full decision context or logic. Whether the export is switched on, and whether enough context is kept to read it in three years, is the customer's question.

The same pages show a measurement gap. The built-in comparison is the agent against a random control group; a comparison with your existing programme you assemble yourself. The agent optimises clicks. Margin and retention are a separate measurement that you own.

The question for whoever signs: if we had to separate or sell this business, could we transfer the customer decision history and keep operating, or would we have to rebuild the logic before the business could stand on its own?

What should you ask before a renewal or a migration decision?

Ask in writing, and ask before the first joint roadmap.

1. Braze customers: your renewal date against the expected closing window, what the change-of-control and sub-processor clauses say, and whether the composable commitment (warehouse-native data, no CRM requirement) is in the contract or only in the press release.
2. Marketing Cloud Engagement customers: what continued use and support of Engagement looks like, and, if a migration is proposed, whether it leads to Next or to Braze, with the data model of the destination before any signature.
3. Marketing Cloud Next customers: what the dependency on the core clouds costs at renewal.
4. Everyone: run the four tests from section three on your own consent withdrawal scenario, confirm that decision IDs reach your warehouse, and sort your switching costs into capital and dependency.

The deal timetable and the product roadmap are not your renewal timetable.

---

Deal terms as announced by Salesforce and Braze on 20 October 2026; product capabilities as documented by the vendors on the linked pages, which can change. This is analysis for marketing and technology leaders; confirm contract terms with your vendor and your own counsel.