What Is Braze? Features, Pricing & Alternatives

Braze is a customer engagement platform (CEP) that orchestrates and delivers personalized messages across email, push, SMS, in-app, and web channels — it is not a customer data platform. Salesforce’s $5.66 billion agreement to buy it, announced October 20, 2026, is the strongest evidence yet that the standalone engagement platform is becoming a feature of somebody else’s suite: the plan places Braze’s real-time engine inside Marketing Cloud while the customer data layer stays in Data 360. The deal is pending shareholder and regulatory approval and is not expected to close before February 2027, so Braze remains an independent company today.

Founded in 2011 as Appboy and public since November 2021, Braze built its reputation on Canvas, a visual journey-orchestration engine, and spent the past two years adding AI decisioning and data-ingestion features. This independent overview covers what Braze does, where it fits on the Customer Intelligence Loop, what it costs, and what the acquisition changes for buyers. For a side-by-side comparison of all CDP vendors, see the CDP Vendor Comparison Guide.

Braze at a Glance

The buyer-size row rests on Braze’s disclosed customer economics rather than a G2 company-size split: the company reports 361 customers above $500,000 in annual recurring revenue and a long tail of smaller accounts. The cross-vendor comparison and methodology are in CDP vendors.

Product Evolution

Braze’s evolution tracks a common pattern among engagement platforms: start with mobile messaging, expand channel coverage, then reach upstream toward the data layer as customers ask for more than execution. The final row is the one that changes the company’s ownership.

Each addition extends Braze further from its messaging core, but the underlying product still orchestrates and delivers campaigns rather than unifying customer records. The acquisition does not erase that distinction.

What Braze Does

• Canvas: Braze’s visual journey-orchestration engine — branching logic, wait steps, and multivariate testing across channels, triggered by user behavior or scheduled campaigns
• Multi-channel messaging: Native delivery across email, push, SMS, in-app messages, webhooks, and WhatsApp, all executed from a single campaign interface
• Intelligent Timing and Intelligent Selection: AI models that choose the optimal send time and channel per user, based on that user’s own engagement history within Braze
• BrazeAI: An agentic layer added in 2024 — a copilot for building campaigns, personalization for generating content variants, and data-science agents that surface engagement insights from Braze’s own event data
• BrazeAI Decisioning Studio: Reinforcement-learning-based testing and decisioning engine — acquired via OfferFit in 2025 — that optimizes offers, channels, and messages per user beyond static A/B tests. The self-service Go edition reached general availability in October 2026, limited to email and engagement optimization (Braze, October 2026)
• Braze Data Platform (BDP): Cloud Data Ingestion (Snowflake, BigQuery, Databricks, Redshift), Currents (streaming engagement events out to external systems), and Connected Content (a send-time HTTP lookup that pulls external data into a message — a templating feature, not a data pipeline)
• Operator Connect: Announced at Forge 2026 in beta — lets marketers analyze, plan, and build Braze campaigns from Claude, ChatGPT, Microsoft Copilot, and other MCP-compatible tools, running under each user’s existing Braze permissions

BDP is a genuine improvement to how data moves into and out of Braze — but it is an integration layer, not a CDP-grade data-unification layer. A customer data platform (CDP) is software that collects customer data from multiple sources, uses identity resolution to build persistent unified profiles, and makes those profiles available in real time for personalization, analytics, and AI-driven activation across channels. Braze does not meet the “persistent unified profiles” clause: its profile is scoped to identifiers its SDKs and ingestion jobs supply — external IDs and user aliases, merged deterministically — and it does not resolve identities across sources it does not own or perform probabilistic cross-source matching. Braze itself lists CDP vendors as technology partners rather than replacements. For the full breakdown of what BDP does and does not solve, see Do You Need a CDP with an Engagement Platform?.

Where Braze Sits on the Customer Intelligence Loop

Diagram from Braze’s AI marketing automation guide, showing how Braze positions its platform components.

The Customer Intelligence Loop maps the full cycle from raw data to delivered message and back. Braze’s product suite covers the back half of that cycle deeply and the front half only partially:

Braze’s own “4 D’s” framework — Data, Decisioning, Design, Distribution — describes this same territory. It is a linear pipeline that starts once data has already arrived and ends at delivery, with no mechanism for engagement outcomes to flow back into cross-channel identity resolution or predictive modeling. That maps primarily to stages 4 and 5 of the Customer Intelligence Loop, with partial coverage of stage 1 through BDP’s Cloud Data Ingestion, minimal coverage of stage 2, and limited coverage of stage 3 — enough to operate on its own event data, not enough to resolve identity or model across channels.

The acquisition does not move Braze up the loop. Salesforce’s Data 360 would supply stages 1 through 3 upstream — the same division of labor Braze has with any CDP today, except that after close both layers would share an owner.

For organizations relying on Braze as their only customer data system, this gap is the practical question: campaigns can only be as targeted as the data Braze itself collects and stores. The core decision: if a CDP is already feeding Braze clean, unified audiences, Braze is a strong execution layer. If Braze is the only customer data system in place, it is missing the identity resolution and cross-channel predictive modeling a CDP provides.

What the Salesforce Acquisition Changes for Buyers

The deal, and what is still undecided

Salesforce signed the merger agreement on October 19, 2026, and announced it the next morning. The terms: an enterprise value of about $5.66 billion, paid as $47.50 in cash per Braze Class A share, a 58% premium to Braze’s October 19 close of $30.04 and roughly 80% above its 30-day average price (CNBC; Evercore ISI, cited by MarketWatch, October 2026). Salesforce will fund the purchase with cash — about four months of its fiscal 2027 free cash flow — and does not expect to need debt financing (Salesforce investor call, October 20, 2026).

What is not decided matters more to buyers than the price:

• Closing. Salesforce expects the deal to close in its fiscal 2028, which runs from February 2027 to January 2028. The merger agreement’s outside date is October 19, 2027, extendable by up to two 90-day periods if only regulatory approvals remain (merger agreement, filed October 20, 2026).
• Approvals. The deal needs a majority of Braze’s outstanding Class A shares and the end of the Hart-Scott-Rodino waiting period, plus other antitrust and foreign-investment clearances. Braze must file a proxy statement, targeted within 35 days of signing, and the shareholder meeting follows the SEC’s review. The HSR filing is due within 20 business days, which puts it in mid-November 2026.
• Regulatory risk. Braze’s own annual report lists Salesforce as a competitor, and Marketing Cloud sells into the same engagement market. Salesforce negotiated a $300 million reverse termination fee if regulators block the deal or it misses the outside date; Braze would owe $191.4 million if its shareholders vote no or it accepts a better offer (Reuters, October 2026). There is no go-shop.
• Leadership and brand. Braze co-founders Bill Magnuson and Jon Hyman plan to join Salesforce after close, and Magnuson said the company will “continue building as Braze” (Salesforce and Braze, October 2026). Founders and five other holders, about 5.3% of shares, signed voting agreements in favor of the deal.
• Product and pricing. Salesforce has published no combined roadmap and no combined pricing plan. It says only that Braze would strengthen Marketing Cloud’s cross-channel personalization (CMSWire, October 2026).

Until the deal closes, Braze remains an independent public company, and both sides describe the period as business as usual.

Why Salesforce is paying 6.8 times trailing revenue for the engagement layer

The strategic logic is easier to see in Salesforce’s own numbers than in the press release. Agentforce Marketing and Commerce — the renamed Marketing Cloud and Commerce Cloud — declined 1% year over year in the fourth quarter of fiscal 2026, the only major product line that shrank, and KeyBanc’s read of the first quarter of fiscal 2027 put the decline at 2% (SalesforceBen, 2026; CRN, 2026). Salesforce stopped reporting the line separately that quarter and guided to “ongoing weakness in marketing and commerce.” Growth is coming from Agentforce and Data 360, which reached about $3.4 billion in combined annual recurring revenue, up roughly 200% year over year (MarTech, 2026).

Braze is strongest exactly where Marketing Cloud is weakest: real-time mobile and in-app engagement. Its event-streaming architecture updates profiles and journeys as customers act, and the company says the platform powers trillions of messages and journey actions a year (Braze, 2026). It reported 2,789 customers as of July 31, 2026 — the figure used in the pricing math below; the announcement cites approximately 2,770 — including Canva, Instacart, Venmo, Dairy Queen, Equinox, and Urban Outfitters.

The price reflects that gap. Salesforce told investors the deal represents about 5x Braze’s expected fiscal 2028 revenue and 2.5% of Salesforce’s enterprise value (Salesforce investor call, October 2026). On trailing numbers, $5.66 billion is roughly 6.8x Braze’s $834 million in trailing-twelve-month revenue, or 6.2x its fiscal 2027 guidance of $910–913 million; Braze traded at about 3.7x before the bid, and HubSpot, Klaviyo, and Adobe traded between 3.1x and 3.8x (SaaStr, October 2026). Public investors were pricing marketing software as an AI-disruption risk. A strategic buyer priced the same asset on its customer base and cross-sell potential. Axios called it Salesforce’s fifth-largest acquisition.

The financial trade-off is explicit: Salesforce expects growth accretion alongside near-term profitability dilution. Braze’s non-GAAP operating margin was 9.7% in its most recent quarter, against Salesforce’s roughly 34%, and UBS flagged the dilution while calling the strategic rationale sound (Braze, September 2026; UBS commentary, October 2026).

The buyer-facing read cuts both ways. Salesforce is paying a premium for the one capability its own marketing cloud lacks, which lowers the risk that Braze is left to stagnate. But Salesforce would then own two overlapping engagement platforms, and its own history says acquired marketing products get consolidated rather than kept parallel: ExactTarget became the base of Marketing Cloud, and Krux and Datorama were absorbed into the same stack (CMSWire, October 2026). Treat capability continuity as likely and product independence as uncertain.

The composable promise gets a new test

Braze spent the past two years positioning itself as the open, composable engagement layer. It built direct ingestion from Snowflake, BigQuery, Databricks, and Redshift; a bidirectional integration with Databricks CustomerLake; and a three-year strategic collaboration agreement with AWS (Braze, September 2026). Salesforce’s announcement echoed that language, promising “an open, composable approach that gives customers flexibility across the data, tools, and partners they rely on.”

The test is whether that survives integration. Braze’s customer base skews toward brands that keep customer data outside Salesforce. If Salesforce bundles Braze with Data 360 and Agentforce, the buying decision shifts from a best-of-breed engagement purchase to a platform commitment, and pricing power moves to Salesforce. Mitch Ashley of The Futurum Group put the overlap plainly: “Once the deal closes, Salesforce will sell two engagement platforms with overlapping jobs” (Techstrong.ai, October 2026).

Four clauses belong in any renewal or new contract signed before closing:

1. A price cap at the first post-close renewal, or a CPI-linked cap, so repackaging cannot reset the contract on unknown terms.
2. A change-of-control termination right — check whether your existing master agreement already gives you one, since that is bargaining power you may not know you have.
3. A written roadmap commitment covering Snowflake-, Databricks-, and CustomerLake-based ingestion, which is exactly what a Data 360-first Salesforce would be tempted to deprioritize.
4. A statement of whether Data 360 or Agentforce becomes a prerequisite for any new Braze capability.

None of these has a published answer yet. That is the point: the acquisition introduces commercial uncertainty before it introduces product change.

The timing decision splits by buyer. If you are net-new and your go-live can slip past the expected close — not before February 2027, possibly as late as the October 2027 outside date — evaluate now but sign after close, when packaging is known. If you must launch before then, sign short — 24 months or less — with a change-of-control exit. If you are an existing customer renewing before close, do not sign multi-year without a price cap. And if regulators block the deal or it runs past the outside date, Braze collects the $300 million reverse termination fee and remains independent: the status quo holds, which is why the contract protections cost little to ask for.

What does not change

Braze is still not a CDP. Salesforce’s CDP is Data 360; Braze is the engagement layer that would sit on top of it. The identity resolution, governance, consent propagation, and cross-channel predictive modeling that Braze lacks today would still come from Data 360 or another CDP — the acquisition changes who owns that upstream layer, not whether Braze has one.

That matters for two buyer profiles. A brand already running Salesforce CRM and Data 360 would get a more coherent suite: unified profiles in Data 360, real-time execution in Braze, agents in Agentforce. A brand that chose Braze to avoid suite lock-in gets the opposite trade: a stronger integrated stack, at the cost of a second vendor boundary disappearing into one. The integration surface itself — APIs, SDKs, and the Currents schema — is not scheduled to change at close. Data-residency posture is a separate item to confirm in writing; the other open questions are commercial and roadmap, not technical.

Braze Pricing

Braze does not publish list pricing. Contracts are quote-based and driven primarily by monthly active users (MAU) or tracked users, plus which modules are licensed. Braze’s pricing page describes the contract as Platform Edition plus MAU or profiles, Action Credits, and CX Services (October 2026); Currents, BrazeAI, and Decisioning Studio are the modules most often quoted as separate line items, while Canvas and multi-channel messaging sit inside the platform edition.

Based on publicly reported Vendr and G2 contract data, mid-market consumer brands commonly land in the $50,000–$200,000 per year range, consistent with other CEPs. Large-scale MAU volumes, combined with BrazeAI, Decisioning Studio, and Currents add-ons, can push enterprise contracts past $500,000 annually — and for the largest consumer brands with hundreds of millions of monthly active users, seven-figure annual contracts are common. Braze’s Q2 FY2027 results report 2,789 customers and fiscal 2027 revenue guidance of $910–913 million, implying roughly $326,000 of annual revenue per customer on a simple division — guidance divided by customer count, not contracted ARR per account, and a rough figure that a long tail of smaller accounts pulls down and large enterprise accounts pull up. The concentration is visible in the disclosed cohort: 361 customers spending $500,000 or more a year contribute 65% of annual recurring revenue (Braze, September 2026).

Because Braze does not unify or store data outside its own channels, the true cost of a complete customer-intelligence stack should also include whatever CDP, warehouse, or identity-resolution tooling feeds Braze accurate, unified audiences — see CDP Pricing: Models, Ranges, and Hidden Costs for a full TCO comparison across architectures.

Two cost lines sit outside the license and belong in any business case. SMS and WhatsApp delivery carry carrier and Meta pass-through fees on top of Braze’s platform charges, and at consumer scale those fees are frequently the largest single line in a messaging budget. Implementation and professional services are also separate: a multi-channel Canvas, CDI, and Decisioning Studio rollout typically involves a services engagement, and Braze’s professional-services revenue more than doubled year over year to $19.6 million in its most recent quarter (Braze, September 2026).

One pricing caveat is new. Salesforce has not published how Braze will be packaged after the deal closes. If Braze becomes part of a Salesforce bundle, list economics could improve for customers already buying Data 360 or Agentforce and worsen for those buying Braze standalone. Procurement teams should treat any multi-year Braze renewal signed before closing as a pricing decision made under uncertainty, and ask for the four protections above.

Strengths

• Best-in-class journey orchestration: Canvas’s branching logic and multivariate testing are consistently cited as among the strongest in the engagement-platform category
• Deep channel coverage: Native delivery across email, push, SMS, in-app, webhooks, and WhatsApp reduces the number of point tools needed for execution
• Real-time engagement at consumer scale: Braze’s event-streaming architecture updates profiles and journeys as behavior happens, and the company says the platform powers trillions of messages and journey actions a year (Braze, 2026)
• AI-driven send-time and channel optimization: Intelligent Timing and Intelligent Selection improve engagement without manual rule-building
• Real investment in AI decisioning: BrazeAI, Decisioning Studio, and the Forge 2026 launches — Decisioning Studio Go, Agentic Standards, Operator Connect, and Conversational Agents — show Braze moving beyond static rules toward agentic execution
• BDP narrows the data gap: Cloud Data Ingestion and Currents make it meaningfully easier to connect Braze to a warehouse or CDP than pure messaging-only platforms offer
• Distribution upside if the deal closes: Salesforce’s global go-to-market could widen Braze’s reach to customers it could not reach alone (Salesforce, 2026) — a benefit Braze cannot buy for itself

Limitations

• No cross-source identity resolution: Braze merges the identifiers it holds deterministically — external IDs and user aliases, including anonymous-to-known stitching inside its own SDKs. It does not perform probabilistic matching across devices, or reach sources outside its own pipelines, the way a dedicated identity resolution system does
• No governed system of record: Profiles in Braze exist to serve messaging, not to act as a source other teams query. Braze will execute a deletion or consent change once it is told, and can emit it through Currents, but it does not originate the policy or enforce it in other systems — that has to live in a CDP or consent platform upstream
• Cross-channel understanding is thin: BrazeAI’s data-science agents work on Braze’s own engagement data. Predictive scoring that spans channels outside Braze — in-store purchases, support tickets, website behavior captured elsewhere — requires external modeling
• The feedback loop never returns upstream: Engagement outcomes feed Braze’s own optimization models, but they do not flow back into cross-channel identity resolution or predictive modeling. Anything happening outside Braze’s SDKs never reaches those models unless it is piped in through BDP or a separate CDP
• Add-on pricing adds up: BrazeAI, Currents, and BrazeAI Decisioning Studio are typically priced as adjacent modules rather than included by default, so the full Braze stack often costs meaningfully more than a base Canvas license suggests
• Ownership uncertainty until close: Salesforce has published no combined roadmap or pricing plan, Braze and Marketing Cloud overlap directly, and there is no answer yet on whether Data 360 or Agentforce becomes a prerequisite for new Braze capabilities. Buyers negotiating before February 2027 are committing to a vendor whose product packaging is about to be decided by someone else

Who Should Consider Braze

Braze is a strong fit for organizations that meet most of these criteria:

• Consumer-facing, mobile- or app-led brands with high message volume and a need for channel diversity
• Marketing teams that want sophisticated journey orchestration and experimentation without heavy data-engineering investment
• Organizations that already have a CDP or warehouse feeding Braze clean, unified audiences and just need best-in-class execution
• Teams prioritizing AI-driven send-time and channel optimization now, with data unification planned as a separate workstream
• Salesforce CRM and Data 360 customers who want mobile-depth engagement from a vendor Salesforce is about to own

Braze is a weaker fit for organizations that:

• Need a single platform for data collection, identity resolution, and messaging rather than assembling one from multiple tools
• Have customer data scattered across five or more non-messaging sources — POS, support, offline — that require real identity resolution
• Operate under compliance regimes that need centralized consent and deletion propagation across every system, not just messaging channels
• Want an AI feedback loop that spans every customer touchpoint, not only the channels flowing through Braze’s own SDKs
• Chose Braze specifically to avoid suite lock-in and run a Snowflake- or Databricks-first data stack

The Warehouse-to-Braze Stack: Is the Middle Layer Necessary?

A common enterprise pattern runs: Cloud Data Warehouse (Snowflake, BigQuery, Databricks) → Reverse ETL (Hightouch, Census) → Braze. The warehouse models customer data with dbt, reverse ETL syncs segments to Braze, and Braze handles messaging. This stack has been the de facto standard for data-mature organizations that want warehouse-native modeling paired with best-in-class engagement.

Two shifts are making the middle layer look increasingly optional — and a third, the acquisition, changes who owns the top of the stack.

Shift 1: Braze Cloud Data Ingestion Cuts Out Reverse ETL

Braze Cloud Data Ingestion (CDI) now connects directly to Snowflake, BigQuery, Databricks, and Redshift — syncing profiles, attributes, and computed fields into Braze without a reverse ETL tool in between. Combined with CDI Segments (audience membership built from warehouse data) and Canvas triggers that fire on warehouse segment changes (April 2026), Braze can now activate warehouse data without Hightouch or Census sitting in the middle. CDI Segments syncs membership rather than the underlying attributes — the zero-copy claim applies to audience computation, not to activation writes, so profile attributes still copy into Braze. For teams whose only use case is “push warehouse audiences to Braze,” CDI makes the reverse ETL layer redundant — one fewer vendor to pay for, one fewer sync to debug at 2 a.m.

Shift 2: Agentic CDPs Combine the Data and Messaging Layers

The larger strategic question is whether the three-layer stack itself — warehouse, activation middleware, engagement platform — is the right architecture. Agentic CDPs that include native messaging collapse the stack into one platform: data unification, identity resolution, AI decisioning, and cross-channel delivery all operate within a single system boundary. There is no warehouse-to-Braze sync to maintain because the CDP handles both the data layer and the messaging layer. There is no reverse ETL to pay for because activation is native, not bolted on.

Shift 3: Salesforce Is Buying the Top of the Stack

For Salesforce customers, the acquisition adds a fourth pattern, not a replacement for the first three: sources → Data 360 (identity, governance) → Braze, with the warehouse as either an upstream source or a zero-copy federated store. That is a suite, not a composable stack. Data 360 handles identity and governance; Braze handles real-time engagement; Agentforce supplies the agents. The appeal is one throat to choke and one commercial relationship. The cost is the same suite tax that applies to any integrated platform: less portability, more bundled pricing, and a roadmap set by the vendor rather than the buyer.

What All Three Approaches Still Miss

Whether you connect your warehouse to Braze directly (CDI), through reverse ETL (Hightouch), or through Data 360 after the acquisition closes, the same structural gaps remain:

• No cross-source identity resolution inside Braze: Every approach depends on identities already being resolved upstream — in the warehouse, Data 360, or a separate CDP. Braze matches known IDs within its own SDKs but does not do the probabilistic cross-device, cross-channel matching a dedicated identity resolution system provides
• PII still moves: Every CDI sync, reverse ETL job, or Data 360 activation copies customer data into Braze. If you activate to five other destinations, that is five more copies at five more vendor boundaries — the same PII sprawl problem composable stacks face, just one layer downstream
• The feedback loop never closes: Engagement outcomes (opens, clicks, conversions) flow back to Braze’s optimization models, but anything outside Braze’s SDKs — in-store purchases, support tickets, ad interactions — never reaches those models unless separately piped in, and outcomes do not return to identity resolution or modeling upstream. The Customer Intelligence Loop never completes its ENGAGE-to-COLLECT return edge

The practical question for most teams is not “do I need reverse ETL between my warehouse and Braze?” — CDI already answers that for simple syncs. The real question is whether a multi-vendor stack is structurally sound for AI-driven marketing, or whether a single agentic CDP with native messaging closes the loop more effectively at lower total complexity. The acquisition adds a third answer — a suite that owns the data layer and the engagement layer — and buyers should price that option against both alternatives. For a full comparison of the costs and trade-offs between these stack patterns, see CDP Pricing: Models, Ranges, and Hidden Costs.

Alternatives to Braze

Organizations evaluating Braze alongside broader customer-data needs generally choose one of two paths: pairing Braze with a dedicated CDP that owns collection, identity resolution, and cross-channel modeling — or replacing the combination with a single agentic CDP that includes native messaging and closes the Customer Intelligence Loop inside one platform boundary. Direct engagement-platform competitors include Iterable (more approachable journey builder, lower cost at mid-market scale) and MoEngage (deeper mobile-app and APAC penetration, Aampe per-user AI decisioning).

The acquisition narrows the independent shortlist. Iterable and MoEngage remain private and independent; Klaviyo remains public and independent; Adobe and Salesforce both sell engagement inside a suite. Buyers who want a best-of-breed engagement layer with no suite owner are choosing from a smaller set than they were a year ago. For a side-by-side comparison of vendors across both approaches, see the CDP Vendor Comparison Guide. Teams building an AI-era RFP should also read How to Evaluate a CDP in the AI Era before comparing Braze against pure-play CDPs.

→ Compare all CDP vendors side-by-side in the CDP Vendor Comparison Guide

See how independent analysts evaluate CDP vendors — download the Forrester Wave or IDC MarketScape reports for a side-by-side comparison.

Related Articles

• Do You Need a CDP with an Engagement Platform? — Full breakdown of what Braze Data Platform does and does not solve
• CDP vs Customer Engagement Platform — The full framework comparison and convergence thesis
• What Is Salesforce Data Cloud? — The CDP layer Salesforce would pair with Braze after the acquisition
• CDP Pricing: Models, Ranges, and Hidden Costs to Budget For — How CDP and CEP total cost of ownership compares across architectures
• What Is Hightouch? — Another vendor repositioning around the “agentic CDP” label
• What Is Iterable? Features, Pricing & Alternatives — Growth-focused engagement platform with AI-driven personalization
• What Is MoEngage? Features, Pricing & Alternatives — The same self-branded-data-layer pattern at a mobile-first engagement platform
• CDP Alternatives: 7 Options Compared and When You Need Each — Where Braze fits among broader CDP alternatives

FAQ

Is Braze a CDP?

No — Braze is a customer engagement platform, not a CDP. A CDP builds persistent unified profiles from multiple sources; Braze’s is scoped to identifiers its own SDKs and ingestion jobs supply, with no probabilistic cross-source matching. Consent and deletion propagation is a separate gap: Braze executes a change once told and can emit it through Currents, but does not originate it. Data 360, not Braze, is the CDP. See Do You Need a CDP with an Engagement Platform?.

Is Salesforce acquiring Braze?

Yes — Salesforce announced a definitive agreement on October 20, 2026 to acquire Braze for about $5.66 billion, but the deal has not closed. Braze shareholders will receive $47.50 per Class A share in cash, a 58% premium to the prior close. The transaction needs a majority shareholder vote and antitrust clearance, and Salesforce expects it to close in its fiscal 2028, between February 2027 and January 2028. Until then, Braze operates as an independent public company.

What happens to Braze customers during the acquisition?

Nothing changes contractually until the deal closes, but the commercial questions are unresolved. Salesforce has published no combined product roadmap or pricing plan, and Braze overlaps directly with Marketing Cloud. Customers should use the pre-close window to secure written answers on pricing protection, roadmap continuity, and data-processing terms before signing a multi-year renewal. Both companies say it is business as usual until closing.

How much does Braze cost?

Braze pricing is quote-based and not published — cost is driven by monthly active users (MAU) plus licensed modules. Currents, BrazeAI, and Decisioning Studio are typically quoted as separate line items, while Canvas and multi-channel messaging sit inside the platform edition. Based on publicly reported Vendr and G2 contract data, mid-market contracts commonly fall in the $50,000–$200,000 per year range; large MAU volumes can push enterprise deals past $500,000, with the largest brands spending $1M or more annually.

What is Braze Data Platform?

Braze Data Platform (BDP) is a 2024 addition that pipes data into Braze and streams engagement events out — it does not turn Braze into a CDP. Cloud Data Ingestion and Currents move data in and out; Connected Content is a send-time lookup, not a pipeline. They improve data flow into and out of Braze’s messaging layer, but Braze lists CDP vendors as technology partners rather than replacements. See Do You Need a CDP with an Engagement Platform?

Is Braze the right CDP for my organization?

Braze is the right engagement platform when you have unified customer data upstream and need real-time, mobile-heavy engagement at scale — and the wrong fit when you need one platform to own identity resolution, governance, and cross-channel predictive modeling. Choose it if your data layer is settled in a warehouse, Data 360, or another CDP and execution speed is the bottleneck. Skip it if you want a single system of record or want to avoid a suite-owned engagement layer.

What are alternatives to Braze?

Organizations typically move in one of two directions: adding a dedicated CDP for data unification alongside Braze, or replacing the combination with a single agentic CDP that includes native messaging. Agentic CDPs close the Customer Intelligence Loop within one platform boundary instead of splitting collection, identity, and messaging across systems. Independent engagement alternatives include Iterable and MoEngage; suite alternatives include Adobe and Salesforce. See the CDP Vendor Comparison Guide for a full comparison.