On October 20, 2026, Salesforce signed a definitive agreement to acquire Braze for $47.50 per share in cash — roughly a $5.66 billion enterprise value and a 58% premium over Braze's prior close — with the deal expected to complete in Salesforce's fiscal 2028, which begins February 1, 2027. Braze is the customer-engagement platform behind 4.5 trillion messages and Canvas actions in 2025, reaching 8.5 billion monthly active users for about 2,770 customers, on $738 million of fiscal-2026 revenue growing 24%. Salesforce says Braze will complement and extend Marketing Cloud Next; Braze's own securities filing says no integration decisions have been made, and the companies operate separately until close. That gap — a year-plus of signed-but-not-decided — is the actionable part of this story. The analyst coverage is roadmap speculation; what it almost entirely skips is governance: who owns the consent record when two profile stores describe the same person, what happens to Braze's warehouse-native data flows inside Salesforce's architecture, and what customers of both products should put in writing while they still have negotiating leverage. Those questions have answers you can start building now.
The deal, in verifiable numbers
The terms come from Salesforce's 8-K on SEC EDGAR: $47.50 per Class A share, all cash, funded without new equity. Braze closed the announcement day up 51.7% at $45.57 — still below the offer, the market's usual discount for regulatory time — while Salesforce slipped about 2.6% premarket. Secondary reads of the merger agreement report a $191 million termination fee if Braze's board takes a superior offer and a $300 million reverse fee if regulators block the deal, with an outside date of one year plus two automatic 90-day extensions. Braze arrives as a four-time consecutive Leader in Gartner's Multichannel Marketing Hubs Magic Quadrant — a quadrant where Salesforce and Adobe are also Leaders, which is precisely why the overlap questions below are not hypothetical. And Braze is one of four October moves: Salesforce also announced acquiring Loops (agentic analytics folded into Tableau, October 12), Rune Technologies (defense logistics for its Missionforce unit, October 29), and a Washington, D.C. innovation center the same day. The spree reads as a company assembling its next platform while the Informatica acquisition — closed November 2025 for $8 billion — is still being digested.
Two of everything, until someone decides
Put the two stacks side by side and the duplication is structural. Data 360 stores customer profiles; Braze stores customer profiles. Journey Builder orchestrates engagement; Braze's Canvas orchestrates engagement. Salesforce's stated frame is that Braze will “complement and extend” Marketing Cloud Next, and Braze's CEO has said the product keeps building as Braze. Both statements are compatible with every possible outcome, from genuine parallel products to a slow-motion replacement. The precedent customers keep raising is Social Studio — acquired capability, years of coexistence, then a 2024 shutdown with a migration deadline. Analysts have been blunt that Marketing Cloud's legacy engagement stack aged poorly, which is a reason to believe Braze is the future of the line — and that is exactly what should worry two groups: Marketing Cloud Engagement customers whose platform now has a visibly newer sibling, and Braze customers who chose Braze specifically because it did not require Salesforce. The most load-bearing dependency at risk is Braze's warehouse-native posture — direct Snowflake, Databricks, BigQuery, Redshift, and Fabric connectors with near-real-time syncs. That architecture is the reason many data teams picked Braze. Whether it survives intact inside a company whose center of gravity is Data 360 is an open question no roadmap has answered.
Two profile stores describing the same person is a sync problem. Two consent records describing the same person is a compliance problem.
The governance questions nobody is writing about
We looked for published analysis of the deal's data-governance mechanics — consent-record migration, residency, integration security — and found essentially none as of November 1. So here is the list the coverage skipped. First, consent and suppression: when a person opts out in Braze but their Data 360 profile says otherwise, which record wins? Today the answer is whichever system sends the message; after integration, an unresolved merge is a regulatory exposure under any privacy regime that treats consent as a record, not a vibe. Second, identity resolution: both platforms resolve identities their own way, and profile merges across them will produce conflicts — the time to document which system is the source of truth for each attribute is before anyone migrates anything. Third, residency and processing: Braze data joining Salesforce's architecture changes where and under whose subprocessor list that data lives, which is a DPA conversation, not a product one. Fourth, the agent layer: Braze's own agentic features currently operate under per-user Braze permissions — the same inheritance pattern we examined in our Agentforce Coworker analysis, about to span two merging permission models at once.
What to do before close
- 01Inventory which system is the source of truth today for consent, suppression, and preference data — per channel, in a document, with an owner. If the answer is “both,” that is the finding.
- 02Document your Braze warehouse-native dependencies — every direct Snowflake/Databricks/BigQuery sync a downstream team relies on — so that if the architecture changes post-close, you know the blast radius before the deprecation notice.
- 03Negotiate now, while leverage exists. Renewals signed before close can carry contractual protections: data-portability commitments, consent-export formats, price locks. After close, the leverage inverts.
- 04Do not migrate preemptively. No integration decisions exist, close is a year-plus away, and Social Studio's lesson cuts both ways — early movers paid twice.
- 05Treat vendor roadmap statements as unsigned until they appear in a contract or an SEC filing. “Complement and extend” is a posture, not a commitment.
If you run Marketing Cloud, Braze, or both, the window between signing and close is when governance work is cheap: the systems are stable, the vendors are motivated, and nothing is on fire. Our fixed-scope reviews map exactly this — which system owns which customer record, where consent lives, what breaks if a connector goes away — and hand you the dependency inventory and the contract asks before the integration roadmap makes them urgent. The acquisition will be decided in San Francisco. Whether it becomes your compliance problem is decided in your org, now.