Spring '26 for Marketing Cloud: business units, Handlebars, and the limits nobody mentions
Spring '26 made Marketing Cloud Next viable for multi-brand teams. The caveats — 50 business units, add-on credits — matter more than the headlines.
Spring '26 was the release where Marketing Cloud Next stopped being a single-brand product. Business units arrived, content tooling matured, and the channel list grew. It is also a release where the published limits deserve more attention than the features.
Business units: the unlock for multi-brand teams
Next can now partition data and marketing assets into separate business units with isolated campaigns and audiences. For any organisation running multiple brands, regions or franchise entities, this was the blocker.
Handlebars, extensions and reusable blocks
Content creation got a serious lift: extensions, reusable blocks, templates with locking, PDF attachments from Salesforce CMS, and Handlebars templating for conditional logic and data references, with syntax validation and inline assistance in Code View.
Template locking is the underrated one. It lets you hand a template to a wider group without handing them the ability to break it — the thing that historically kept email production bottlenecked through two or three people.
Channels: useful, and metered
Spring '26 added in-app messages, SMS with UTM tracking, WhatsApp interactive templates and two-way email in Next. On the Engagement side, multi-channel messaging gained CTA URLs, catalog messages, MM Lite, VCF support and bot-click detection.
| Worth knowing | Detail |
|---|---|
| Catalog messages | Capped at 30 products per message |
| WhatsApp payments | Availability is region-specific — check yours before designing a flow around it |
| SMS and WhatsApp | Consume add-on credits on both Next and Engagement |
| Several features | Require a paid add-on or a "Plus" SKU upgrade |
None of these are hidden — they are in the notes. They are just easy to miss when a release is presented as a list of capabilities, and expensive to discover after you have designed a campaign around them.
Sandbox email testing finally behaves
The blackhole feature discards outbound email in full and partial sandboxes, with configurable domain exceptions.
Small feature, disproportionate relief. Every consultancy has a story about a sandbox refresh that mailed real customers. This removes the whole category of accident — and the domain exceptions mean your own team can still receive test sends.
Reporting and the Engagement bridge
Reporting picked up mobile app metrics, delivery status filtering and 30-day conversion analytics with iOS/Android platform filtering. Engagement gained "Marketing Cloud Next for Engagement" — lockable templates, unified campaign records and legacy data compatibility, with admin setup required.
That bridge is the more strategically interesting item. It is Salesforce reducing the distance between the two products, which makes a phased move more realistic than the all-or-nothing cutover most teams have been quietly dreading.
What we would do with this release
- Turn on sandbox blackhole today. No downside, removes a real risk.
- Count your business units. If you are near 50, that shapes your migration architecture, not just your timeline.
- Standardise on Handlebars for anything new.
- Audit your add-on credits before designing multi-channel campaigns. Check the entitlement, not the feature list.
- Look at the Engagement bridge if a full migration is not fundable this year. A phased path is now a genuine option.
A note on what is in your org
Everything above shipped, but availability varies by edition, SKU and region, and several items need add-ons. Confirm in Setup before you plan around any of it.
Sources
Planning your Marketing Cloud roadmap?
Blueport is a Sydney-based Certified Salesforce Consulting Partner with 100+ implementations since 2018. If you are weighing up a move to Marketing Cloud Next, or getting more out of Engagement while you wait, we are happy to talk it through.
Talk to our team