Salesforce Personalization vs. Marketing Cloud Personalization: The Guide to Web Campaigns

A few years ago, building a personalized homepage on Salesforce meant one thing: log into Marketing Cloud Personalization, wire up a content zone, split your audience into segments, and publish a campaign that swapped a banner based on which segment a visitor fell into. That playbook still works. It is also no longer the whole story.

Salesforce has spent the last two years rebuilding personalization from the ground up. The result, Salesforce Personalization, sits natively on Data 360 and runs on Agentforce, and it changes what “personalized” actually means, from picking the right segment to reacting to a single visitor’s intent in real time. If your team is still running campaigns the way we described them in our original 2023 post, here is what has moved, what has not, and how to plan your next build.

What Is Salesforce Personalization? From Evergage to Agentforce

Marketing Cloud Personalization did not start as a Salesforce product. It began life as Evergage, was rebranded Interaction Studio after Salesforce’s acquisition, and later became Marketing Cloud Personalization as the platform matured. Salesforce itself confirms these are the same underlying product across three names, with each rename tracking a wave of feature investment.

That product, now often shortened to MCP, is still a fully supported, standalone real-time interaction management platform. It personalizes web, email, and mobile experiences using rules-based campaigns, segments, and A/B testing, largely the same architecture behind the workflow in our earlier post.

What is new is Salesforce Personalization, the next-generation engine Salesforce built independently of MCP. Instead of running on its own island, it is built natively into Data 360 (Salesforce’s customer data platform, formerly Data Cloud) and powered by Agentforce. That single architectural choice is what separates the two products and what should drive your decision if you are starting fresh.

What’s the Difference Between Marketing Cloud Personalization and Salesforce Personalization?

Marketers often ask whether MCP is being retired. It is not. Salesforce actively supports both products, and the choice comes down to architecture and ambition rather than one replacing the other outright.

• Marketing Cloud Personalization operates independently of the rest of your Salesforce org. It uses segment-based targeting, meaning everyone who matches a rule sees the same treatment. Campaigns are built around content zones, segments, and manual rules, close to the workflow described in our 2023 walkthrough.
• Salesforce Personalization is built directly on Data 360 customer profiles and uses a real-time decisioning engine to adapt content for each individual visitor, not just their segment. It also plugs directly into Agentforce, so a conversation with an AI agent can inform what a visitor sees on your website minutes later.

The practical distinction: segmentation groups people who look alike. Adaptive personalization, Salesforce’s term for what the newer engine does, learns from an individual visitor’s own clicks and adjusts their experience without waiting for a human to define a new segment.

Existing MCP customers do not need to rip and replace anything. Salesforce offers an MCP+ SKU that lets current customers keep their existing MCP instance running while getting access to Salesforce Personalization’s newer capabilities at no additional license cost. New implementations, on the other hand, should default to Salesforce Personalization, since Salesforce has said as much directly in its own product FAQ.

How Do You Build a Personalized Web Campaign in Salesforce Today?

Our original post used a simple example: personalize the homepage hero banner by gender, sending men to a men’s category page and women to a women’s category page. That use case still holds up, but the two platforms solve it differently.

The Marketing Cloud Personalization Approach (Still Valid for Existing Instances)

If your org already runs MCP, the workflow has not changed structurally:

1. Define a content zone on your homepage through the Visual Editor’s sitemap tool, marking the hero banner as a target for personalized rendering.
2. Build a global template (for example, a banner-with-CTA layout) and set the personalized image, header, subheader, and destination URL for each variant.
3. Create your segments, in this case an affinity-male and an affinity-female segment.
4. Build the campaign, attach each segment to its matching template as a distinct experience, then save and publish.
5. Sync the segment to Marketing Cloud through Sync to Other Systems, so the same audience can be picked up by an outbound journey.

This is a segment-first model. It works well for straightforward rules and is worth keeping if your team already has MCP campaigns in production.

The Salesforce Personalization Approach (Recommended for New Builds)

On the newer engine, the same banner use case is handled through Adaptive Websites rather than a manually wired content zone. You still define an audience concept, but the decisioning engine can go further than a fixed rule: it can weigh a visitor’s real-time browsing behavior against their declared or inferred affinity and pick the highest-performing creative for that specific person, not just their segment. Recommenders (rule-based or objective-based) and built-in Experiments handle the layout and testing side, running A/B or multivariate tests across the experience with automatic winner detection.

The bigger shift is where the data comes from. Instead of a standalone MCP profile, the engine reads Data 360 customer profiles, so a purchase in Commerce Cloud, a case in Service Cloud, or an intent signal captured by an Agentforce agent can all shape what that same visitor sees on your homepage. Salesforce’s own “Get User Intent” Agentforce action is a direct example: it turns what a customer says in an AI conversation into structured signals that feed the decisioning engine within the same session.

Does Salesforce Personalization Work Across Email and Mobile, Not Just Web?

Our original post treated “sending a segment to Marketing Cloud for Journey Builder” as a separate, manual step. That is still possible, but Salesforce Personalization narrows the gap between web, email, and mobile considerably.

• Email now pulls from the same connected customer records the web decisioning engine uses, so a send can reflect what a customer did on your site an hour earlier without a separate export step.
• Mobile runs on a Unified SDK that shares the same adaptive logic across web and native iOS and Android apps, with Mobile App Personalization reaching general availability in July 2026 for teams that want business users, not just developers, activating it.
• Cross-department use extends past marketing. Because everything sits on Data 360, sales, service, and commerce teams can act on the same real-time profile instead of waiting on a marketing-only data pull.

If your use case still calls for classic Journey Builder automation, syncing a Data 360 or MCP segment into a journey remains a supported pattern, and it is the right call when you need scheduled, multi-step outbound sequences rather than in-the-moment web adaptation.

Which Salesforce Personalization SKU Do You Need: MCP, MCP+, or Base?

A few practical rules to plan a licensing conversation with your Salesforce account team:

• Already live on Marketing Cloud Personalization? You can stay put. The MCP+ SKU gives existing customers access to Salesforce Personalization’s newer features without disrupting the current setup, so this is a low-risk way to pilot the new engine.
• Starting from zero? Salesforce recommends the Salesforce Personalization Base SKU for teams that need web and mobile personalization, since it is the actively developed, natively integrated path.
• Full-stack ambitions (Agentforce decisioning, AI-based recommenders, cross-channel attribution)? That level of capability sits under Marketing Cloud Personalization+, aimed at customers who want both the legacy toolset and the newer AI-driven layer without abandoning either.

Pricing for these SKUs is credit- and org-based rather than per-user, so budget conversations should center on expected traffic and personalization volume, not headcount.

Frequently Asked Questions

.