Every Salesforce Marketing Cloud release ships another channel, another agent, another rebuilt builder. Winter '27 is doing something less obvious. Underneath the long feature list runs a single thread: Salesforce is finally fixing measurement. Bot-filtered clicks, tracking at the content-region level, B2B dashboards in Tableau Next, mobile push folded into unified reporting. If your team defends creative choices and budget with click rates, this release matters more than any new channel on the list. Here is what actually changes, and what you can do before it lands.
Note: Winter '27 is still in pre-release at the time of writing. The features described here, and their availability dates, are subject to change.
The real theme is engagement data you can trust
Open rates stopped being a management metric the day Apple Mail Privacy Protection shipped and corporate security scanners became universal. Click rate held out a little longer, until spam gateways started visiting every link before the recipient did. Every deliverability team knows the result: inflated click rates, and creative decisions made on noise.
Winter '27 goes after the problem from two directions. It cleans up the measurement you already have, by separating human clicks from automated ones. And it adds a level of detail that never existed, by tracking engagement at the content-region level. The first makes your numbers honest. The second makes them useful.
Impression Region Tracking: measuring the region, not just the email
This is the most consequential change in the release. Until now, a click in Marketing Cloud told you which link was clicked. Impression Region Tracking tells you which region of content was rendered and clicked: a specific sentence, a paragraph, the text inside a button, or two competing wordings on the same button.
You declare a named region inside a supported content block, and that name is written into send and click event data. From there you build custom reports across four metrics: impression regions per send, total clicks per region, unique clicks per region, and click rate per region.
Declaring a region in Handlebars
{{#impressionRegion "weekend-picks"}}
<a href="{{trackedLink offers.weekend.url}}">
See this weekend's picks
</a>
{{/impressionRegion}}The same idea in AMPscript
Winter '27 widens what AMPscript and Handlebars can do, and creating impression regions is on the list, alongside building rowsets, looking up and claiming rows in Marketing Objects, regular expressions, and MD5 and SHA512 hashes. That means you can instrument a block you already have rather than rebuilding it.
%%[
SET @tier = AttributeValue("LoyaltyTier")
SET @region = IIF(@tier == "Gold", "hero-cta-gold", "hero-cta-base")
SET @label = IIF(@tier == "Gold", "Shop early access", "Shop the edit")
]%%
<a href="%%=RedirectTo(@url)=%%">%%=v(@label)=%%</a>This is not an email-only feature. Winter '27 makes it available for email, SMS, RCS, WhatsApp and mobile app messages, which is what turns it into a genuine cross-channel optimisation tool rather than another email reporting tab.
The point of Impression Region Tracking is not better email reporting. It is making your creative tests comparable across channels, which only works if you enforce one naming convention from day one.
Agree the naming convention before the first send
The trap here is the same one that ruins Data Extension estates: without a convention, you have four hundred unmanageable region names within six months. A format that survives contact with a real production calendar:
<channel>-<placement>-<object>-<variant>
email-hero-cta-a
email-hero-cta-b
sms-body-offerlink-a
rcs-card1-button-aClick rates without the bots
On SMS, Winter '27 separates human activity from automated activity outright. Data Cloud now carries two distinct metrics: human-verified clicks and bot-generated clicks. You can also configure an SMS or MMS flow to continue only when a real recipient clicks the link.
That second capability is easy to underrate. A poorly filtered clicker journey chases people who never opened the message. You thought you were optimising; you were manufacturing message fatigue and opt-outs.
On email, the reliability work shows up elsewhere: the Email Deliverability Health Score rates your programme from 0 to 100 and fires automatic alerts when a key metric moves into a warning or critical range. The Recommendation Details panel then surfaces the root cause, the affected campaigns, and numbered remediation steps ordered by impact.
B2B Analytics for Marketers brings pipeline into Tableau Next
Available since 10 August 2026, B2B Analytics for Marketers pulls accounts, opportunities, campaigns, engagement and attribution into Tableau Next dashboards. The ready-made dashboards cover account-based marketing performance, pipeline influence, campaign return, deal velocity and attribution.
You switch it on in Setup, from Marketing Cloud Assistant Home. For teams who have spent years exporting Data Views into a third-party BI stack, this is the meaningful shift: the engagement-to-pipeline chain becomes native, with no intermediate ETL to maintain and no nightly job to babysit.
Mobile push joins the Content Performance dashboard
The Content Performance dashboard gains a Mobile Push tab. Email, SMS, WhatsApp and push notifications now sit in one screen, with KPI cards showing period-over-period movement. A Platform filter compares iOS against Android, and the Engagement table filters by date range and campaign. To get there, open a content record, select the Performance tab, then Mobile Push.
One operational caveat worth flagging early: access to the Content Performance dashboard requires either View All Reports or Dashboard Viewer. Review your permission sets before you promise these screens to stakeholders.
Flow Builder gets the same treatment. The Send SMS Message element now exposes an Analytics tab covering total runs, average duration and a success-versus-error breakdown, then SMS sends, delivery rate, click-through rate and opt-out rate, all without leaving the flow. The Send RCS Message element mirrors it with RCS reads, response rate, failed deliveries and opt-out rate.
What to do before the release lands
- Audit your current click rates and estimate how much of the volume is automated, before filtering drops your curves overnight.
- Draft your impression region naming convention and get creative teams to sign off on it.
- Map every journey that branches on a click and decide which ones should move to human-verified clicks.
- Check which profiles hold View All Reports or Dashboard Viewer.
- Record the cutover date in your recurring reports.
That last item is the one teams skip. A click rate that falls from 4.2% to 3.1% because the bots are gone is not a performance problem, but it will be read as one if nobody set expectations. A footnote in the monthly report is cheaper than an awkward steering committee.
Key takeaways
Measurement is the real Winter '27 story. Behind the channel announcements, Salesforce is repairing the reliability of engagement data, which shapes your budget decisions far more than any new builder.
Impression Region Tracking changes the unit of analysis. You move from click-per-link to click-per-content-region across email, SMS, RCS, WhatsApp and in-app, declared in either Handlebars or AMPscript.
Bot filtering will lower your numbers. Plan for the break in your historical series and communicate the cutover date before someone else notices it.
B2B Analytics for Marketers removes an ETL. Engagement-to-pipeline reporting becomes native in Tableau Next, enabled from Marketing Cloud Assistant Home.
Permissions are a prerequisite, not a detail. Without View All Reports or Dashboard Viewer, the dashboards you promised your stakeholders simply will not appear.
Planning your move to Marketing Cloud Next, or want an honest audit of how reliable your current engagement metrics really are? Talk to our SFMC consultants.
