Baseline deliverability before Winter '27 adds the health score
Winter '27 adds a 0-100 Email Deliverability Health Score with alerts. Baseline now with the deliverability dashboard filters so the score means something.
The Winter '27 release, generally available on 12 October 2026, adds Email Deliverability Health to Marketing Cloud Next: monitoring across mailbox providers, a 0 to 100 Email Deliverability Health Score, and automated alerts when a critical threshold is reached. It builds on the Winter '26 deliverability dashboard, which already filters by domain type (Gmail, Hotmail and so on) and by message type (promotional versus transactional) and shows failure reasons per provider.
- Product
- Marketing Cloud Next
- Edition
- edition not stated in the source
- Topic
- Deliverability
- Confidence
- Medium - shown in a credible source
- Last verified
Who this applies to
- Anyone responsible for email sending reputation in Marketing Cloud Next
- Edition: not stated in the release note summaries we checked
- Winter '27 orgs from 12 October 2026. Preview sandboxes had the release from late August
Why it matters
A single number with an alert is only useful if you know what normal looks like. Teams that start watching deliverability the day the score appears will not be able to tell a seasonal dip from a reputation problem. The dashboard you already have gives you the baseline; the score then tells you when to act.
Try it
- Now, before 12 October: open the deliverability dashboard and record failure reasons and volumes by provider (Gmail, Microsoft, others) for the last two or three campaigns. Split promotional from transactional.
- Write down what you would treat as a problem for each provider, for example a jump in a specific failure reason, so the alert threshold means something to your team.
- After the release lands: note the initial Health Score and keep the weekly value alongside your send volumes for the first month before you react to it.
- Enable the automated alerts and decide who receives them. An alert nobody owns is noise; put it in the channel your send approvals already live in.
- When an alert fires, go back to the provider and message-type filters to find which combination moved. The score tells you that something changed; the filters tell you what.
Example use case
A retailer's promotional sends to Gmail addresses start bouncing at a higher rate after a list import. Because the team recorded a baseline per provider in September, the drop in the Health Score in November is traced to Gmail promotional traffic within an hour rather than being blamed on the Black Friday creative. The imported segment is suppressed and the score recovers before the main campaign.
Prerequisites, limitations and risks
- Winter '27 in your org. The GA date is 12 October 2026 per Salesforce; your upgrade weekend is on Trust status
- Edition and any permission requirements are not stated in the summaries we used. Confirm in your org after upgrade
- The score is a signal about your sending, not a fix. Authentication (DKIM, SPF, DMARC) and list hygiene still have to be right
- A score threshold and its alert behaviour are Salesforce-defined; the source does not say whether the threshold is configurable
Documented behaviour above comes from the sources listed below. Availability varies by edition, SKU and region - confirm entitlements in your own org before you rely on a feature.
Sources
- Monitor Email Deliverability Health (Winter '27 release notes)
- Salesforce Winter '27 release announcement (newsroom)
- Winter '26 release notes (deliverability dashboard filters)
Stuck on this in your own org?
Blueport is a Sydney-based Certified Salesforce Consulting Partner with 100+ implementations since 2018. If a step above does not match what you see in Marketing Cloud Next, tell us - it is either an edition difference or a change worth knowing about, and we will find out which.
Talk to our team