Salesforce Marketing Cloud Next Winter Release '27: What Changes for Your Org?

Marketing Cloud Next Winter '27 is a long release, and the agent features take most of the attention. The smaller items matter as much to teams still on Marketing Cloud Engagement, because this release adds scripting outside email, link edits after a send, compliance archiving and flow version history. Below, the Winter '27 changes are grouped by the build decisions they affect, with Advanced Edition features and known limits marked.

Note: Winter '27 is still in pre-release. Features, editions and dates can change before general availability, so check the official release notes before you commit to a roadmap.

Winter Release Note '27: Key Highlights

1. Agentforce Now Decides Who Gets Which Campaign

In Winter '27, Agentforce in Marketing Cloud Next moves beyond drafting and flow decisions. Two agents cover the work from planning to send. The Marketing Goals Agent decides which campaign, channel, content and send time each customer gets, and the Content Agent writes the assets those decisions call for. Marketers set how much the agent can do without approval and can review every decision it makes.

I. Marketing Goals Agent (Advanced Edition only)

The agent picks the campaign, channel, content and timing for each person. It has three prerequisites that teams often find late in a project:

• A content source: the Agentforce Content Agent or a CMS.
• A set of enabled campaign goals. Each campaign uses one goal from that set.
• Adaptive Campaign Audiences (Beta), when a customer can qualify for more than one campaign. Without it, the agent cannot choose between overlapping campaigns.

II. Content Agent (Growth and Advanced)

The Content Agent writes and edits copy and images for email, SMS, MMS and RCS in a shared workspace. It works from your marketing brief, customer data and brand guidelines. You can refine drafts in conversation, edit layout and text by hand, or change the code directly. Approved content publishes to Salesforce CMS for use in standard campaigns and Goals Agent campaigns.

III. Set up Brand Center before either agent

Both agents write from the same source. Brand Center stores identity, voice, tone and visual style as one brand kit. Once it is activated, agents and human authors both work from it, and content syndication shares it across workspaces.

Our take: finish the brand kit before you switch on either agent. With an empty or half-built kit, the agents produce generic copy, and marketing teams tend to judge the feature on those first drafts.

2. One Personalization Setup Now Covers Every Channel

AMPscript and Handlebars reached Marketing Cloud Next email in Summer '26. Winter '27 extends them to SMS, WhatsApp, RCS, in-app messages, push notifications and landing pages. With the new Data Sources tab, a personalization setup built in Content Builder can be reused in other channels, and each token resolves to the same value for a given recipient wherever it appears.

In practice, four things change:

• One data model for personalization: The Data Sources tab sorts inputs, data and expressions (Salesforce records, data graphs, offers, Apex, events and activations) the same way in every channel builder.
• Landing pages without LWC rebuilds: Logic that used to need a Lightning Web Component can run as AMPscript or Handlebars on the page, including conditional logic and form capture.
• New functions: Building rowsets, looking up and claiming rows in Marketing Objects, regular expressions, MD5 and SHA512 hashing, and impression regions. Row claiming is what allows one coupon code per recipient.
• Testing with real recipient data: Preview and test accept lists, individuals and campaign recipients across email, SMS, WhatsApp, mobile app and RCS. The rendered JSON is editable, so merge errors show up before the send.

Our take: for teams moving off Marketing Cloud Engagement, this change has the biggest effect on migration cost. Existing AMPscript now carries over to more channels, so less of it has to be rebuilt, and rebuild work is usually the largest item in a migration estimate.

Our Marketing Cloud implementation blueprint explains how we scope that rebuild work.

3. Flows Can Now Pick a Path per Customer and Show What Changed

Personalization controls what a message says. Flow Builder controls who gets it and when, and Winter '27 adds two things marketing operations teams have asked for there: a model that chooses the path, and a view of what changed between flow versions.

I. Personalize Paths (Advanced Edition only)

Add the Personalize Paths element, pick a success metric (a standard Salesforce metric or a custom engagement signal), and define the paths to compare, such as different channels or content variants. Each person goes down the path predicted to convert best, and the model keeps learning from real outcomes. Any extra engagement signals it should consider must be set up in advance.

II. Flow operations that reduce risk

4. Consent and List Sends Now Run Straight from CRM

Flows also reach further into CRM in this release. Two changes remove workarounds between Salesforce records and Marketing Cloud Next.

I. Consent from record-triggered flows

The Consent Request action now runs in record-triggered flows, so opt-ins and opt-outs can follow CRM changes. A new Lead can be subscribed to a newsletter when it is created, for example, or a Contact opted out of a stream when an Opportunity closes.

List sends without a Data 360 segment: Promotional, transactional and relational email can go straight to a filtered Contact or Lead list through Actionable Lists. Segment processing could delay these sends and occasionally make them fail, so sales-led teams gain the most here. Lists can also be imported from a campaign record and cloned with their members.

II. Preference pages per channel

Each channel can have its own published preference page, with its own subscriptions, branding and button text, attached at message level. You can also reorder subscriptions and edit the header, body and button text. Grouping and nested layouts are still missing, so a long subscription catalogue shows as one flat list.

5. Deliverability and Compliance Gaps Close for Regulated Teams

These features get less attention than the agents. For regulated organisations, though, several of them answer objections that held back a move to Marketing Cloud Next.

1. Email Deliverability Health Score

A score from 0 to 100, with alerts when key metrics reach warning or critical ranges. A Recommendation Details panel lists the root cause, affected campaigns and fixes ordered by impact.

2. Post-send link fixes

A tracked link's destination can be changed after sending, through a Salesforce Support request. Links with merge fields all redirect to a single static URL.

3. Compliance BCC

One org-level BCC address copies every sent email, set up under Unified Messaging in Setup, with an optional per-send override.

1. Your own mail relay (Advanced)

Route outbound mail through organisation-managed servers, with bounces, replies and complaints still handled.

2. High-volume archiving (Advanced)

Copies of sent email go to your own cloud storage via Data 360, bypassing the 100,000-emails-per-day limit of the Summer '26 archiving feature. At the time of writing, only Microsoft Azure is supported; Amazon S3 was dropped from the plan.

3. View as web page

A secure, per-recipient link to a hosted version of the email on your branded domain.

4. Multilingual variants

Language variants managed inside one email in Content Builder, with Content Agent translation and edits in Component, Code or Text view.

5. Image Recommenders

A pool of candidate images, with the image chosen per recipient at send time from profile and engagement history.

6. Impression Region Tracking

Click metrics for a specific sentence, button or button-text variant across email, SMS, RCS, WhatsApp and mobile app messages.

Two smaller fixes arrive too: plain-text preview (you still can't send a plain-text test) and bulk deletion of content and folders, including published content.

6. Developers Can Send and Manage Content Without Building Flows

Until now, every programmatic send needed an on-demand flow. Two APIs remove that step.

• Direct Email Send API: Create an email send definition (content, sender profile, email settings), then call the API to identify recipients, preview and send. This is the simpler route for transactional email from external systems.
• CMS REST API: Create, modify and search Marketing Cloud Next content: email, SMS, WhatsApp and mobile app messages, plus video, content blocks, tracked links and forms.

Teams integrating order or account systems can pair these with the order-event REST trigger in the flows table above.

7. RCS and WhatsApp Get the Largest Channel Updates

• RCS gains carousels of up to 10 cards, location and calendar actions, business-unit-level preference pages and subscriptions on a shared RCS agent, Campaign-tab management, in-flow analytics, REST-triggered sends for OTPs and order updates, and 17 additional countries including Canada, Singapore, Spain and the Netherlands.
• Flash Sending (Advanced) sends up to 5 million mobile app messages in 90 seconds, targeted by custom attributes set at device registration.
• WhatsApp Business-Scoped User ID (Advanced) lets you message and track users who hide their phone numbers behind usernames.
• Unmatched inbound replies send a default response (or none) when an SMS or WhatsApp message matches no consent request, conversation or keyword.

8. Retail and B2B Teams Get Prebuilt Triggers and Dashboards

Retail: Unique coupon codes per recipient via a Coupons tab and CSV upload; prebuilt triggers and flow templates for birthday, anniversary, visitor conversion, re-engagement and replenishment; a trigger for new products in a customer's high-engagement category; and finer targeting through custom inactivity rules, excluding recent purchasers from stock and price alerts, minimum product-page visits, and Contact Point DMO mapping for channel selection.

B2B and analytics: B2B Analytics for Marketers brings accounts, opportunities, campaigns, engagement and attribution into Tableau Next dashboards, configured from Marketing Cloud Assistant Home (available from 10 August 2026). SMS analytics move into Flow Builder, SMS clicks are split into human and bot activity (and flows can continue only on human clicks), and the Content Performance dashboard adds a Mobile Push tab with an iOS/Android filter. A new campaign overview shows KPIs and content status from the campaign record.

Winter '27 Admin Changes That Need a Decision

Most of the release is opt-in. The items below need a decision or a task from your admin team:

• Republish stale landing pages: A release update scheduled for October 2026 moves landing pages to current hosting infrastructure. Check the Publication Calendar and republish any page last published more than six months ago.
• Decide on the Sales Data Kit: It is now deployed on demand from Marketing Cloud Basic Settings. If you skip it, you must map Email Latest Bounce Date Time and Email Latest Bounce Reason Text on the Contact Point Email DMO yourself.

• Review licences: Existing Platform Plus users can now run Marketing Cloud Next workflows with the Marketing Cloud Manager or Admin permission set plus Data 360 permission sets. No new licences come with this. It widens the set of existing users you can assign.
• Consolidate setup: Initial setup, web tracking and the consent banner now live in Salesforce Go, and site-level landing page settings move to a Marketing Sites tab outside Experience Builder.

• Distributed Marketing: Required phrases and character limits on templates, a prebuilt flow template to deliver templates to sales users, bulk sends of up to 2,000 recipients, and keyword template search through the Distributed Marketing Agent.

Fields and single records can also now be added to Marketing Objects directly from Data Explorer, including objects that already hold data.

Which Winter '27 Features Need Advanced Edition?

If your business case for Marketing Cloud Next depends on any row marked "No" under Growth, settle the edition question before scoping.

Where to Start with Winter '27

For orgs still on Marketing Cloud Engagement, Winter '27 fills several feature gaps: script portability, post-send link edits, Compliance BCC, flow version comparison and API sends without flows.

The migration discussion can now focus on data model and process design. For orgs already on Marketing Cloud Next, start with the inputs the new agent and ML features depend on: a finished brand kit, consent logic in CRM and defined engagement signals.

New to the platform? Start with our complete guide to Marketing Cloud Next, or see how it compares in Marketing Cloud vs other automation tools.

If you're deciding which Winter '27 features belong in your next quarter, or whether to move off Marketing Cloud Engagement, our Marketing Cloud Next consultants can map the release against your current org in a working session.