Salesforce Is Acquiring Braze. What Does This Mean for Your CRM Strategy?

On 20 October 2026, Salesforce announced its agreement to acquire Braze in a transaction valued at approximately $5.66 billion. For the CRM and MarTech industry, it’s a significant development. Salesforce is bringing one of the leading customer engagement platforms into an ecosystem that already spans customer relationship management, data, analytics, marketing automation and AI.

For businesses using Braze, or currently considering it, the announcement naturally raises questions. What happens to existing CRM investments? How might Braze fit into Salesforce’s wider ecosystem? Will the acquisition change how companies approach customer data, personalisation and marketing automation? And perhaps most importantly, should any of this influence the decisions CRM teams are making today?

At Glassjaw, we see the acquisition as a potentially exciting development for customer engagement. Braze has established itself through its ability to turn customer behaviour into relevant, timely interactions across channels. Salesforce brings an extensive enterprise ecosystem, customer data capabilities and significant investment in AI.

The combination presents interesting possibilities. However, the value of any CRM platform ultimately depends on more than the technology itself. It depends on the quality of the underlying data, how effectively different systems work together, and whether businesses can translate those capabilities into meaningful customer experiences.

With that in mind, let’s look beyond the acquisition headlines and explore what this means in practice.

1. What Salesforce Is Actually Acquiring

To understand the potential implications, it’s worth looking at the role Braze plays within a modern MarTech architecture.

Salesforce has traditionally been associated with customer relationship management and enterprise business applications. Its portfolio now extends well beyond CRM, encompassing marketing, customer data, analytics and AI. Braze, meanwhile, specialises in customer engagement. Its platform enables brands to respond to customer behaviour, orchestrate journeys and deliver personalised experiences across channels including email, mobile push, in-app messaging, SMS and web.

These capabilities are particularly valuable for businesses that need to engage customers throughout their lifecycle, rather than relying primarily on scheduled campaigns.

Consider a customer browsing a product in a mobile application. Their behaviour might trigger a personalised recommendation, influence their eligibility for a particular offer or determine whether they receive a push notification later that day. To deliver that experience effectively, a business needs to connect customer events, profile information, decisioning logic and communication channels.

Braze provides much of the engagement and orchestration infrastructure required to make those interactions possible.

Salesforce’s acquisition therefore brings together two important parts of the customer technology landscape: enterprise customer data and business applications on one side, and real-time customer engagement on the other. Salesforce has also highlighted the potential relationship between Braze’s capabilities and products such as Data 360 and Agentforce.

This is particularly interesting as businesses move towards more sophisticated personalisation and AI-assisted customer engagement. However, it’s important to distinguish between the capabilities available today and the integrations that may emerge in the future.

The acquisition remains subject to the relevant approvals, with completion expected during Salesforce’s fiscal year 2028. Until the transaction closes, the companies continue to operate independently. For customers, this means that existing product capabilities and confirmed roadmaps should remain the basis for technology decisions.

2. Already Using Braze? The Bigger Opportunity May Be in Your Existing Investment

For organisations already running Braze, the acquisition provides an opportunity to reassess their customer engagement strategy. Not necessarily because something needs to change, but because it’s a useful moment to examine whether the business is getting the full value from its current platform.

Many companies invest in sophisticated engagement technology with ambitious plans for personalisation, automation and customer lifecycle management. Yet the reality of implementation often looks different. Initial priorities focus on getting the platform live, migrating existing campaigns, establishing integrations and ensuring business continuity.

Once those foundations are in place, day-to-day campaign delivery can take priority over longer-term optimisation. As a result, a business may have a powerful engagement platform but still be using only a portion of its capabilities.

From Campaign Execution to Lifecycle Orchestration

Consider a retailer using Braze primarily for promotional emails, newsletters and a handful of automated journeys. The platform may be working well operationally, but there could be opportunities to develop a more sophisticated lifecycle programme.

For example:

Behavioural triggers: Responding to meaningful customer actions rather than relying exclusively on scheduled campaigns.
Cross-channel orchestration: Coordinating messaging across email, push and in-app channels to create more consistent experiences.
Personalisation: Using purchase history, product preferences and engagement signals to improve message relevance.
Lifecycle optimisation: Developing journeys around onboarding, retention, repeat purchase and reactivation.
Experimentation: Testing different approaches to understand which interactions influence customer behaviour.

These are capabilities that businesses can explore with Braze today. They don’t require waiting for the Salesforce acquisition to close.

For more mature CRM teams, the opportunity may be different. A company already operating sophisticated cross-channel journeys might benefit more from improving its data architecture, strengthening measurement or introducing more advanced decisioning.

The important question is therefore not simply whether Braze will become more powerful under Salesforce. It’s whether the organisation has the data, processes and strategy required to make effective use of the capabilities already available.

Technology Maturity and CRM Maturity Are Not the Same Thing

A company can have a technically sophisticated MarTech stack and still struggle to deliver relevant customer experiences. It might have an enterprise data warehouse, a customer engagement platform and several analytics tools, yet lack a consistent understanding of customer identity or a clear approach to lifecycle measurement.

Similarly, an organisation might execute hundreds of campaigns every year without knowing which activities generate incremental revenue.

These challenges are rarely solved by adding another platform. They require a combination of technical improvements, strategic prioritisation and operational discipline.

For existing Braze customers, this is where we see some of the most immediate opportunities. The acquisition may create exciting possibilities for the future, but improving how customer data and engagement programmes work today can generate value much sooner.

3. Your Customer Data Architecture Matters More Than Ever

One of the most interesting questions surrounding the acquisition concerns customer data. Salesforce already offers Data 360, while Braze integrates with a range of data warehouses, CDPs and other customer technology platforms.

For businesses using Snowflake, Databricks or an existing CDP alongside Braze, it’s reasonable to wonder how the wider ecosystem might evolve. Will Salesforce encourage customers to adopt Data 360? Could native integrations simplify existing architectures? Will businesses need to reconsider where customer profiles and segmentation logic are managed?

These are relevant questions, but the acquisition itself doesn’t create an immediate need to redesign an existing data architecture. The starting point should remain the business’s requirements.

The Difference Between Storing Data and Activating It

Imagine a subscription business using Snowflake as its central data warehouse and Braze for customer engagement. Snowflake contains subscription information, transaction history, product usage and other customer attributes. Braze uses selected data to personalise communications and orchestrate customer journeys.

At first glance, this might appear to be a straightforward integration. In practice, several architectural decisions determine how effectively it works.

Data freshness

How quickly does relevant information become available for engagement?

A subscription cancellation event that reaches Braze several hours late may result in inappropriate renewal messages. A purchase event that arrives after an abandoned-cart journey has already triggered can create a similarly poor customer experience.

Not every use case requires real-time processing. Some segments can be refreshed daily without affecting the customer experience. The important part is understanding which signals are time-sensitive and designing the data flows accordingly.

Identity resolution

Can the business reliably connect activity across different customer touchpoints?

A customer might browse anonymously, create an account, make a purchase and later interact through a mobile application. If these activities aren’t connected to the appropriate customer profile, segmentation and personalisation become less reliable.

Identity resolution is therefore a foundational consideration, regardless of which engagement platform is used.

Segmentation and decisioning

Where should audience definitions and business logic live?

Some segmentation can be managed directly within Braze. Other use cases may depend on complex calculations involving transaction history, product usage or predictive models maintained in a data warehouse.

For example, a retailer might calculate customer lifetime value or purchase propensity in Snowflake and make those attributes available to Braze for campaign orchestration.

There isn’t a universal answer to where every decision should happen. The right approach depends on data complexity, latency requirements, operational ownership and the capabilities of the existing stack.

Measurement

How does the business connect engagement activity to commercial outcomes?

Sending a personalised message is one part of the process. Understanding whether that message influenced a purchase, improved retention or generated incremental revenue is another.

This often requires connecting engagement data with transactional and analytical systems.

Does Every Braze Customer Need Salesforce Data 360?

No.

For a company with a well-established data warehouse and effective integrations into Braze, there may be no immediate business case for introducing another customer data platform.

On the other hand, a company already using Salesforce extensively may find opportunities to simplify its architecture as the two ecosystems evolve.

The decision should be based on practical considerations:

Which systems currently hold the most reliable customer data?
Where are customer identities resolved?
Which use cases require real-time data activation?
How much duplication exists between platforms?
What are the integration, maintenance and operating costs?
How easily can the business adapt its architecture as requirements change?

These questions are more useful than assuming that every component of a MarTech stack should eventually sit within one vendor’s ecosystem.

Designing for Flexibility

A well-designed customer data architecture should support the business’s engagement strategy while allowing technology choices to evolve.

That might mean maintaining a central customer data model in Snowflake or Databricks. It might mean using a CDP to unify identities and activate audiences across multiple destinations. Or it might involve making greater use of Salesforce’s existing data capabilities.

The right architecture depends on the organisation. What matters is that customer data remains accessible, reliable and usable across the systems that need it.

For businesses evaluating their next technical investment, the Salesforce–Braze acquisition makes this an especially worthwhile conversation.

4. What Could the Acquisition Mean for AI-Driven Customer Engagement?

AI is another important dimension of the announcement. Salesforce has invested heavily in Agentforce and its broader AI ecosystem, while Braze already offers capabilities designed to support personalised customer engagement and decisioning.

Bringing these technologies closer together could create opportunities for more connected, intelligent customer experiences. But what might that look like in practice?

Moving Beyond Predefined Customer Journeys

Traditional marketing automation often relies on predefined rules. A customer performs an action, enters a journey and receives a sequence of communications based on conditions established by the marketing team.

This approach remains valuable, particularly for well-understood lifecycle moments such as onboarding, abandoned carts and renewal reminders. However, customer behaviour is rarely linear.

Two customers entering the same journey may have very different needs, preferences and likelihoods of responding. More advanced decisioning approaches can help businesses determine which action is most appropriate for an individual customer, rather than treating everyone within a segment identically.

Consider a travel brand. One customer regularly books weekend city breaks and responds well to mobile notifications. Another books one major holiday each year, prefers email and typically researches destinations over several weeks.

A more sophisticated engagement programme could use those differences to influence which content, channel and timing are selected. AI-driven decisioning has the potential to make these interactions increasingly adaptive.

The Technology Is Only Part of the Equation

For these experiences to work, several components need to operate together:

Reliable customer data: Accurate, timely information about customer behaviour, preferences and interactions.
Clearly defined objectives: An understanding of whether the goal is to increase bookings, improve retention, reduce churn or encourage adoption.
Decisioning capabilities: The ability to evaluate customer signals and determine appropriate actions.
Engagement execution: A platform capable of delivering those actions through the relevant channels.
Measurement: A way to determine whether the chosen approach produces better outcomes.

Without these foundations, more sophisticated AI capabilities may simply introduce additional complexity.

This is why we believe the most interesting implication of the acquisition isn’t the possibility of adding AI to more marketing workflows. It’s the potential to connect customer intelligence, decisioning and engagement more effectively.

What Should Businesses Do Now?

For organisations interested in AI-driven CRM, the immediate priority should be assessing readiness. That includes understanding which customer signals are available, how reliable they are, where decisions are made and how outcomes are measured.

A company with fragmented customer identities and inconsistent event tracking will struggle to deliver sophisticated personalisation, regardless of how advanced its AI tools become.

By contrast, a business with strong data foundations and well-structured lifecycle programmes will be better positioned to take advantage of future capabilities as they become available.

5. What If You’re Currently Implementing or Evaluating Braze?

For companies in the middle of a Braze implementation or platform evaluation, the timing of the announcement may introduce additional questions.

Should the project continue? Is it worth waiting for more clarity? Could Salesforce eventually change how Braze is positioned within its product portfolio?

These are reasonable considerations. However, it’s useful to separate immediate implementation requirements from longer-term product developments.

If You’re Already Implementing Braze

An ongoing implementation should continue to be evaluated against its agreed objectives, technical requirements and delivery milestones.

For example, a business migrating from another engagement platform may be working towards:

Establishing customer profiles and event tracking.
Integrating web or mobile SDKs.
Connecting existing data sources.
Migrating campaigns and automated journeys.
Configuring consent and subscription management.
Validating data quality and campaign performance.
Preparing internal teams to operate the platform.

These requirements remain relevant regardless of the acquisition.

Unless a confirmed product or contractual change directly affects the implementation, there may be little benefit in delaying work that is already delivering progress.

That said, it’s sensible to maintain visibility into the product roadmap and discuss any relevant developments with Braze.

If You’re Currently Evaluating Braze

The acquisition introduces an additional consideration, but it shouldn’t replace the existing evaluation criteria.

A platform decision should still be based on five key questions:

Can the platform support your customer engagement requirements? Consider the channels, journeys, personalisation capabilities and customer experiences the business wants to deliver.
How will it integrate with your existing technology? Evaluate data ingestion, SDK requirements, APIs, identity management, event tracking and connections to your warehouse or CDP.
What will it take to operate successfully? Consider the internal team, processes and technical support needed to use the platform effectively.
How will you measure success? Define the commercial and operational outcomes the platform is expected to support.
How flexible is the architecture? Consider how easily customer data can move between systems and how the platform fits into the organisation’s longer-term technology strategy.

The Salesforce acquisition may strengthen Braze’s long-term proposition, particularly as potential integrations and new capabilities emerge. However, those possibilities should be considered alongside the functionality available today.

A strong technology decision should make sense based on current requirements, while leaving room for future developments.

6. What CRM Teams Should Prioritise Over the Next 90 Days

For most organisations, the acquisition doesn’t require an immediate strategic overhaul. However, it creates a useful opportunity to review existing CRM investments and identify where improvements could deliver the greatest value.

We’d suggest focusing on four areas.

1. Review Your Current Braze Utilisation

Start by understanding how effectively the platform is being used. Which lifecycle stages are covered by automated journeys? Are communications coordinated across channels? How much personalisation is based on meaningful customer behaviour?

Are teams experimenting with different approaches, or primarily repeating established campaign formats?

The goal is to identify opportunities to extract more value from existing capabilities.

2. Assess Your Data Foundations

Review the systems and integrations supporting customer engagement. Pay particular attention to customer identity, event tracking, data freshness and the availability of relevant attributes.

Identify where data limitations are preventing the business from delivering the experiences it wants to create.

For example, if purchase events aren’t consistently available in Braze, improving that integration may be more valuable than introducing additional campaign complexity.

3. Revisit Your CRM Roadmap

Consider whether your existing roadmap reflects current business priorities.

Are upcoming projects focused on measurable customer outcomes? Do you have the technical foundations required to support more advanced personalisation? Are there opportunities to improve retention, conversion or customer lifetime value through better lifecycle orchestration?

The acquisition shouldn’t necessarily change these priorities, but it provides a good reason to revisit them.

4. Stay Informed Without Putting Progress on Hold

Continue discussions with Braze about relevant product developments, particularly where future integrations could affect your architecture or investment plans.

For existing customers, upcoming renewals and major technical projects are natural opportunities to review commercial arrangements and product dependencies.

For prospective customers, vendor due diligence should include questions about roadmap commitments, interoperability and implementation support.

The key is to distinguish between developments that require action today and possibilities that may become relevant later.

A Practical Decision Framework

Your situation	What to focus on now
You’re already using Braze	Review platform utilisation, lifecycle coverage and opportunities for optimisation.
You have Braze connected to Snowflake or another data platform	Assess data freshness, identity resolution, integration reliability and measurement.
You’re planning more advanced personalisation or AI-driven CRM	Evaluate data readiness, decisioning requirements and experimentation capabilities.
You’re currently implementing Braze	Continue validating technical requirements, delivery milestones and business objectives.
You’re evaluating Braze for the first time	Assess current capabilities, architecture, operating requirements and long-term flexibility.
You’re heavily invested in Salesforce	Explore how Braze could complement your existing ecosystem while monitoring confirmed integration developments.

7. Looking Ahead: A Potentially Important Moment for Customer Engagement

The Salesforce–Braze acquisition is significant because it brings together capabilities that are becoming increasingly important to modern customer engagement.

Businesses want to understand their customers more effectively, respond to behaviour in real time and deliver personalised experiences across multiple channels. They also want to reduce fragmentation across their technology stacks and make better use of the data they already collect.

The combination of Salesforce’s enterprise ecosystem and Braze’s customer engagement capabilities creates interesting opportunities to address these challenges.

Exactly how the products, integrations and broader ecosystem will evolve remains to be seen. But for businesses already using Braze, there is a strong case for continuing to develop their customer engagement programmes.

The platform’s existing capabilities remain relevant, and the acquisition introduces the possibility of further innovation over time.

For companies considering Braze, the announcement adds a new dimension to the evaluation process, but the fundamentals of choosing the right technology remain unchanged.

The most effective CRM strategies are built around customer needs, business objectives and reliable data. Technology enables those strategies, but doesn’t replace them.

Ultimately, the businesses best positioned to benefit from future developments will be those that continue investing in the foundations of effective customer engagement today.

Not Sure What the Salesforce–Braze Acquisition Means for Your CRM Plans?

Whether you’re already using Braze, planning an implementation or reviewing your wider MarTech architecture, it’s worth understanding how your current technology supports your longer-term customer engagement goals.

At Glassjaw, we help brands make better use of their CRM and customer data, from Braze implementation and lifecycle optimisation to marketing automation, integrations and data strategy.

If you’re reviewing your current setup, exploring new opportunities or simply want an expert perspective on your next steps, we’d be happy to have a conversation.

Let’s talk about your CRM strategy.

Get in touch with the Glassjaw team.

Sources and Further Reading

Salesforce, Salesforce Signs Definitive Agreement to Acquire Braze, 20 October 2026.
Braze, Salesforce Signs Definitive Agreement to Acquire Braze, 20 October 2026.
Official Braze product documentation covering customer engagement, integrations, Cloud Data Ingestion and Currents.
Salesforce product information covering Data 360 and Agentforce.

Published October 2026. This article reflects information available at the time of publication. Future product integrations, commercial arrangements and roadmap developments remain subject to change.