Salesforce’s Winter ’27 release brings a considerable number of updates to Marketing Cloud Next, also known as Agentforce Marketing. And unlike some Salesforce releases where the changes feel concentrated around a handful of features, this one touches almost every part of the marketing process.

We’re seeing developments in AI-powered campaign planning, lead engagement, personalization, messaging, reporting, data management, and marketing operations.

Some of these capabilities are genuinely interesting.

But as someone who has worked across marketing technology, CRM implementations, and Revenue Operations, I’m more interested in whether they can solve the problems marketing teams have struggled with for years.

Campaigns that take too long to launch. Customer information scattered across different systems. Marketing and sales teams that disagree on lead quality. Reports that measure engagement without showing how marketing contributes to revenue.

These problems don’t disappear simply because an organization introduces another AI capability.

What makes the Salesforce Winter ’27 release worth reviewing is how Marketing Cloud Next is bringing more of these activities into a connected operating environment.

Here are 12 updates I think marketing and RevOps leaders should pay attention to.

1. Agentforce Marketing Campaigns

A bigger Winter ’27 development is the growing role of Agentforce in campaign creation and execution.

Salesforce introduces new marketing agents to help with campaign planning, content creation and orchestration. These capabilities can help marketers move from a campaign objective to executable activities with less manual coordination.

I can see the appeal.

Building a campaign often involves several disconnected steps. Someone defines the audience, another person creates the content, a marketing operations specialist configures the automation, and someone else reviews the results.

Each handoff introduces delays and opportunities for miscommunication.

Agentforce could help coordinate some of that work.

But I’d want to know how the organization defines success before allowing an agent to make recommendations.

If the objective is lead generation, what qualifies as a useful lead? If the campaign is aimed at current customers, how does the agent decide which accounts are good cross-sell opportunities and which should not be sent another promotion?

These decisions require a business context.

I would also like to see marketers retain control over approvals, audience selection, messaging and campaign activation.

As we wrote in our article about what organizations should consider before implementing Agentforce, AI readiness is more than simply the technology. Teams need to have well-defined responsibilities, measurable data and sound processes before deploying agents into production workflows.

The value of Agentforce Marketing shouldn’t come from launching more campaigns. It should come from helping teams launch better campaigns with less operational friction.

2. Marketing Planning and Management

One of the Winter ’27 updates I think needs more eyes on it.

Salesforce offers Marketing Planning and Operations capabilities that link marketing strategies, programs, campaigns and business objectives through a structured planning hierarchy.

Teams can set goals, link campaigns to larger programs, coordinate approvals and tasks, and track how results contribute to broader objectives.

Salesforce lists Marketing Planning and Operations as part of the Marketing Cloud Next Advanced offering.

For RevOps leaders, this addresses a familiar problem.

Marketing teams often plan activities in one application, manage budgets in another, execute campaigns in a third, and prepare performance reports somewhere else.

By the time leadership reviews the results, someone has already spent hours consolidating information.

A connected planning environment could reduce that administrative effort.

But the more interesting opportunity is accountability.

If a campaign supports a particular revenue objective, marketing should be able to explain how that activity contributes to the goal.

That requires more than connecting campaign records.

Organizations need consistent definitions for pipeline contribution, attribution, campaign costs, and performance targets.

These considerations are also relevant to the bigger challenge of constructing a modern RevOps technology stack, which seeks to make systems work together, rather than adding more platforms working in silos.

I would start by looking at those definitions before putting in a new planning structure.

Otherwise, teams risk creating a more sophisticated version of the same reporting problems.

3. Buyer’s Engagement Agent

The company is also upgrading the Buyer Engagement Agent to assist Agentforce with lead generation and nurturing.

The capability is designed to engage prospective customers and help push the right leads toward sales qualification.

It makes sense for sure, particularly for groups that get a lot of inbound queries.

Not every prospect needs to be contacted immediately by a salesperson. Some might need more information. Some might not meet the organization’s criteria.

An agent could help manage those initial interactions and identify when a human should become involved.

But this is where marketing and sales alignment becomes particularly important.

I’ve seen organizations celebrate the number of leads they generate while sales teams complain that those leads aren’t worth pursuing.

Adding an AI agent won’t resolve that disagreement.

Before implementing the Buyer Engagement Agent, I’d want marketing and sales to agree on qualification criteria, routing rules, ownership, and the circumstances that require human intervention.

I’d also review how the organization records conversations and makes that context available to sales representatives.

A lead shouldn’t have to repeat the same information simply because the interaction moved from an agent to a person.

For RevOps, the measures that matter include sales acceptance rates, lead-to-opportunity conversion, response times, and the quality of information transferred during the handoff.

An agent that is engaging thousands of prospects may seem productive. But if those interactions don’t lead to better sales opportunities, the organization has to re-evaluate how it’s using the technology.

4. Campaigns & Flow in Salesforce

Winter ’27 also improves campaign workflows with completion actions, better visibility into campaign status and performance, and easier access to custom Flow templates.

I think this is especially true for marketing ops teams.

Much of the campaign’s administration, surprisingly, is just repetitive.

someone completes a form. The system updates a record . A contact arrives in a segment. Sales is notified and marketing triggers a follow-up activity.

When these activities span across disconnected tools, teams spend more time managing the process and less time improving the customer experience.

Salesforce Flow provides a way to standardize those activities.

Create defined workflows to respond to customer behavior and events with completion actions.

But I wouldn’t just necessarily throw AI at the process.”

If a customer fills out a form and the next step is defined by a well understood business rule then traditional automation is probably the best choice.

So AI is more useful when the process involves understanding context or choosing between multiple possible actions.

Why this matters: Once organizations have these workflows in place, they need to maintain them.

I’d rather have a marketing team run a few well-designed automations than build out dozens of overlapping flows that nobody understands.

5. Brand Center and Customizing Content

Marketing Cloud Next is building content management and personalization capabilities for Salesforce.

Winter ’27 includes Brand Center, reusable brand assets, scripting support, and personalized content blocks for teams across channels.

Salesforce also rolls out reusable agentic content blocks for email, SMS, MMS and RCS.

These updates could help organizations reduce the amount of repetitive content work associated with managing multiple campaigns.

Suppose a company exists in a number of regions.

The messaging for each market is slightly different, but the organization still wants to maintain consistent branding, product information, and campaign standards.

Reusable content means teams can handle those variations without reinventing the wheel each time.

But I’d be careful about treating personalization as a goal in itself.

Just because a platform can insert customer attributes into a message doesn’t mean those attributes improve the experience.

Organizations need to know what information is accurate, relevant, and appropriate to use.

I’d also like marketing teams to create approval processes for content produced by AI.

Brand consistency is more than simply colors and logos. It covers tone, product claims, legal requirements and the promises an organization makes to its customers.

“Agentforce can help create content but the marketing team still owns what the company says.

6. Email Testing & Deliverability

Email is still a big part of many marketing programs, so I welcome the attention Salesforce is giving it in Winter ’27.

This release provides enhancements that allow marketers to preview personalized content as a specific recipient, find deliverability problems, and fix tracked-link problems.

It adds more language support, as well as image personalization choices.

These may seem like relatively small improvements compared to AI-powered campaign orchestration,

But anyone who has managed email campaigns knows how much trouble a broken link or incorrect personalization rule can cause.

An email might perform perfectly during internal testing but display the wrong content when a recipient’s data differs from the test record.

Giving marketers better ways to preview personalized content can help identify those problems before launch.

I would also focus on deliverability monitoring.

You can’t generate meaningful results from a campaign if the messages aren’t reaching the right audience.

Email delivery is a technical issue, but marketing teams should also look at engagement metrics and deliverability trends.

For RevOps, these improvements underscore the value of trusted customer data, consistent testing, and clear ownership of campaign quality.

7. RCS and WhatsApp Messaging

Also, Marketing Cloud Next is improving its messaging capabilities.

Winter ’27 adds Rich Communication Services (RCS) support, report enhancements, mobile flash messaging and WhatsApp engagement using usernames where supported.

The updates give marketers more ways to reach customers via mobile channels.

But with another channel come new operational considerations.

Customers can connect with an organization through email, SMS, WhatsApp, and other messaging channels.

When each channel works in a silo, the business can quickly lose sight of what the customer has already been given.

So imagine this: Someone receives a promotional email, replies to it on WhatsApp and then gets another message promoting the same offer.

While each campaign may deliver as expected, creating a seamless customer experience is difficult.

That is why I believe channel expansion should be combined with improving audience management and customer data.

Organizations should set out contact preferences, consent requirements, message frequency rules and clear reporting definitions.

I would also examine the price and effectiveness of each channel, not assume that more messaging options automatically mean better engagement.

The aim is to be able to communicate in a coordinated way, not just to increase the number of messages a customer receives.

8. Landing Pages and Forms

Winter ’27 On-site personalization of landing pages and forms using custom HTML, Handlebars and AMPscript. It also helps simplify site configuration management and supports a wider range of data sources to tailor visitor experiences.

For marketing operations teams, these capabilities could make it easier to build experiences that respond to customer information and behavior.

But I’d start by looking at the quality of information those forms collect.

If your lead-capture process is not well designed, then a nicely personalized landing page won’t help.

If a form gathers information that sales doesn’t need, or lacks the details needed for qualification, the organization still has a process problem.

I would review form design including Salesforce field mapping, lead routing, consent collection and duplicate management.

Marketing and sales should agree on what information is important and when the organization needs to gather it.

Asking for too much information can cause unnecessary friction. If you ask for too little, you may end up with extra work after you turn it in.

Getting the right mix depends on the business process.

For me, better landing pages should mean a better customer experience and better quality information flowing into Salesforce.

9. Consent & Audience Management

Winter ’27: Better audience management

You can now have actionable campaign lists, record-triggered consent updates, and better preference page personalization.

I think these updates are important because as organizations grow, managing the audience becomes more and more complicated.

A company can store client preferences in Salesforce, marketing consent elsewhere, and regional communication rules elsewhere.

“If those systems are out of alignment, teams may be contacting the wrong people or using outdated information.”

Although flexible audience management can help, organizations still need a credible source.

Who owns consent information? Which system determines whether a contact can receive a particular message? How quickly should preference changes take effect across channels?

Those are governance questions.

I’d also distinguish between whether an organization can contact someone and whether it should.

A customer may technically qualify for a campaign while having little interest in the offer.

Better segmentation will help marketing teams make more relevant decisions, not just increase the number of people they can reach.

10. Analytics in B2B Marketing

Reporting is another major piece of the Winter ’27 release.

Salesforce is launching B2B Analytics for Marketers, as well as better SMS performance reporting and click-rate measurement with bot detection.

I really like the focus on bot activity.

“Marketing teams often measure campaign performance by engagement metrics, but with automated interactions those numbers can be skewed.

When a security scanner clicks on an email link, that’s not a genuine customer showing interest.

Better bot detection could help with a more accurate engagement interpretation.

But I still think the larger reporting challenge is the same.

Marketing teams need to link campaign activity to business outcomes.

A campaign may have a high click-through rate but not create meaningful pipeline. One might get less interaction, but influence a handful of valuable opportunities.

If leadership only looks at engagement, they might come to the wrong conclusion about which campaign did better.

I’d want Marketing Cloud Next reporting to give a consistent measurement framework around marketing and sales.

This requires consensus on lead stages, campaign attribution, opportunity relationships, and the metrics that are important to the business.

As we noted in our article on measuring CRM ROI , organizations need to connect system activity to measurable business outcomes, not simply look at adoption and engagement statistics.

For RevOps leaders, I’d focus on lead-to-opportunity conversion, campaign-influenced pipeline, sales acceptance rates, and revenue contribution alongside traditional engagement measures.

Better dashboards are useful. Better decisions are the real objective.

11. Marketing Objects and Data 360

One of the less flashy but potentially more consequential areas of Winter ’27 involves marketing data management.

Salesforce is expanding how organizations create, manage, test, and integrate marketing objects.

The release includes support for building marketing object schemas, importing data extensions from Marketing Cloud Engagement, managing records through Bulk API, testing schema changes in sandboxes, and synchronizing marketing object data with Data 360.

For organizations who have complex marketing technology stacks, these changes are worth paying attention to.

Marketing data is usually scattered across a variety of platforms, each with its own unique identifiers, field definitions and rules for how it can be combined.

Linking APIs together isn’t enough to bring all that information together.

Teams need to know how the records connect to each other, which fields are most important, and how the company will ensure data quality.

I also think the additional sandbox features are valuable.

Testing processes are not always clear or are limited, which forces marketing teams to make changes to live environments.

That adds unnecessary risk, particularly when a change to the schema impacts campaigns that are currently running or automated workflows.

If teams can test changes before deploying them, they may reduce this risk.

But the technology still needs a governance model.

I’d want RevOps, marketing operations, and Salesforce administrators to agree on naming conventions, data ownership, integration responsibilities, and change-management procedures.

As we’ve discussed in why your Salesforce admin shouldn’t own your revenue strategy, technical administration and business process ownership need to work together without becoming the same responsibility.

Data 360 can help surface customer information, but organizations still need to interpret what that information means and how teams should act on it.

12. Next APIs for Marketing Cloud

Marketing Cloud Next integration may get easier with Winter ‘27 developer-friendly updates.

Salesforce Adds Content-Management and Direct Email Send APIs for Programmatic Email

It offers a Bulk API for high-volume marketing object operations and a Metadata API for programmatic schema management.

These capabilities can certainly be a difference maker for mature marketing technology stacks, but you don’t hear marketing leaders talking about them like Agentforce.

Many companies use multiple systems to manage content, customer data, campaigns and reporting.

Developers build custom integrations to fill information gaps between systems.

More complete APIs can help teams standardize work.”

I’d watch for new integrations.

Before connecting another app, organizations must know which system owns the data, how often it needs to sync, and what happens if an integration fails.

I want teams to document dependencies and monitor data quality.

An integration that works during implementation can become a maintenance problem if nobody understands how it operates six months later.

The objective should be to make the marketing technology stack easier to manage, not simply more connected.

Which Marketing Cloud Next Updates Matter Most?

With so many Winter ’27 updates, I would not recommend that organizations try to do everything.

So I would start with the business issues that are most friction-filled and figure out what capabilities might address them.

I’d also involve marketing operations, sales operations, Salesforce administrators, and the teams responsible for customer data before deciding what to implement.

Each group sees a different part of the process.

Marketing might want to accelerate campaigns. Sales might be wanting higher quality leads. It may concentrate on stability of integration. RevOps needs to know how those priorities play into the revenue process as a whole.

The idea is to pull those points of view together and create a plausible implementation plan.

My Take on Marketing Cloud Next Winter ’27

My excitement about this release goes beyond the number of new Marketing Cloud Next features.

Salesforce is going that way.

Marketing planning, campaign execution, AI agents, customer data, messaging, and analytics are integrating.

That could help companies integrate marketing into their revenue process rather than as a separate activity.

I like that.

But I also think organizations need to be careful about introducing complexity while trying to eliminate it.

An AI agent that creates campaigns faster won’t solve unclear campaign objectives. Better personalization won’t fix inaccurate customer records. More sophisticated reporting won’t help if marketing and sales disagree on what the numbers mean.

And adding another communication channel won’t automatically improve the customer experience.

I’ve always believed that technology delivers the most value when organizations understand the processes they’re trying to improve.

Some companies may find Agentforce Marketing their biggest Winter ’27 opportunity. Better data management, campaign reporting, or Flow automation are examples.

Companies shouldn’t judge Marketing Cloud Next on the number of new features they can turn on. How can marketing teams improve execution, collaborate with sales and demonstrate revenue contribution?

Maximizing Your Salesforce Marketing Operations

Marketing Cloud Next promises to connect customer data, automate campaigns, improve personalization and strengthen marketing performance measurement.

But unlocking value is about more than just enabling new features.

Revenue Ops LLC helps companies assess their Salesforce environments, align marketing and sales processes, improve data quality, and identify opportunities for automation that can deliver real results.

Whether you are looking at Agentforce Marketing, reviewing your existing marketing automation architecture or planning a larger Salesforce optimization initiative, we can help you find out where to focus.