The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Salesforce's Braze acquisition raises questions for Marketing Cloud teams (opens in a new tab)

You will learn what the announced Braze acquisition means for Marketing Cloud Engagement and Marketing Cloud Next, and which skills and architectural decisions it may affect.

Why read this

The article also makes clear that no combined roadmap exists yet.

Marketing Cloud Engagement

  • Relies on Journey Builder
  • Established automation offering

Marketing Cloud Next

  • Emphasises Data 360 and AI
  • Automation through Flow Builder
The two Marketing Cloud platforms the Braze deal must fit alongside, as the article describes them

Salesforce has agreed to acquire Braze, an engagement platform that reacts to customer behaviour in real time across email, push, in-app messaging, SMS and WhatsApp, in a deal valued at around $5.66B. Salesforce expects to close during fiscal 2028, subject to shareholder and regulatory approval. Braze says in an SEC filing that its integration with Data 360, Customer 360 and Agentforce remains a possibility and that no decisions have been made.

The article notes that Salesforce has not published a combined roadmap showing how Braze’s capabilities will overlap with Marketing Cloud Engagement, which relies on Journey Builder, and Marketing Cloud Next, which centres on Data 360, AI and Flow. Salesforce’s president of applications and marketing suggested Braze would extend Marketing Cloud Next with real-time, mobile-first engagement rather than replace Marketing Cloud.

For practitioners, the piece argues that the greatest risk is over-specialising in one orchestration tool, and that event tracking, identity, API integration and data architecture skills will grow in value. It also expects consulting work around integration, migration and platform rationalisation, while warning that pricing, packaging and third-party integration openness remain unknown.

Read the original at Salesforce Ben (opens in a new tab)

Worth reading?

Architecting Salesforce Marketing Cloud requires a data foundation before campaign configuration (opens in a new tab)

Readers will learn how to structure data, identity, and consent architectures before configuring journeys in Marketing Cloud.

Why read this

The piece outlines practical questions to answer during implementation planning to prevent scaling failures.

The article argues that Salesforce Marketing Cloud implementations often fail when treated as simple campaign setups rather than comprehensive data projects. It emphasizes that reliable personalization depends on a foundational layer that handles data trust, identity mapping, consent tracking, and system integration before any journeys are built.

It outlines key architectural decisions that must be made prior to configuration, such as identifying authoritative data sources, selecting shared attributes for decisioning, and determining refresh frequencies. The author warns against indiscriminately loading every available field into Data Extensions, recommending instead a focused dataset that supports cross-journey personalization.

Identity resolution and consent management are highlighted as critical components that require business-led decisions rather than pure platform configuration. While tools like Data 360 can consolidate records, organizations must define trusted identifiers, handle duplicates, and map household relationships. Consent must be modeled across channels, geographies, and purposes to ensure accurate suppression and compliance.

Finally, the piece advises designing integrations around business journeys rather than creating point-to-point connections between systems. It recommends evaluating implementation partners based on their ability to establish governance rules, reusable journey patterns, and clear data ownership, ensuring the platform remains sustainable as campaign volume grows.

Read the original at dev.to (opens in a new tab)

Worth reading?