2026 Field Notes on Customer Engagement Platforms — Part 5: Salesforce Marketing Cloud (Agentforce Marketing)

Andrea Veggiani Andrea Veggiani
field-notesmartechcepsalesforce
2026 Field Notes on Customer Engagement Platforms — Part 5: Salesforce Marketing Cloud (Agentforce Marketing)

Why Salesforce is Part 5 (and why “CRM gravity” is a different kind of gravity)

If Adobe Journey Optimizer is powered by suite gravity, Salesforce is powered by something even stronger in large enterprises: CRM gravity.

Salesforce doesn’t start from “marketing automation.” It starts from a platform where sales, service, commerce, and partners already live and then asks marketing to become a first-class citizen of that operating system.

That’s the fundamental positioning: Salesforce isn’t only trying to orchestrate campaigns.

It’s trying to orchestrate customer relationships, with marketing becoming a connected layer that can react to what happens in:

This is why Salesforce evaluations are rarely “Is it the best email tool?”

They’re usually: “Do we want marketing orchestration to be anchored to the same platform that runs our commercial engine?”

And increasingly, because of the Agentforce narrative, also: “Do we want AI agents to live in the same place as our customer truth?”

A practical way to phrase the trade-off is:

If your business believes the next advantage comes from joining these worlds, Salesforce becomes less of a product selection and more of a platform strategy.

A quick note on scope (because Salesforce marketing is not one product)

When people say “Salesforce Marketing Cloud,” they might mean one of three different realities:

  1. Marketing Cloud Engagement (the legacy-yet-powerful ExactTarget lineage)
    Email Studio, Mobile Studio, Journey Builder, Automation Studio, etc.
  2. Marketing Cloud on Core (Growth / Advanced)
    Newer editions built on the Salesforce core platform, designed to work natively with Data Cloud
  3. Next-Gen / Marketing Cloud Next (Agentic Marketing)
    The “agentic” layer Salesforce is building to turn journeys, personalization, and conversations into an AI-driven operating model

In this article, I’m treating Salesforce’s CEP proposition as the combination of these layers, because that’s how enterprise roadmaps increasingly evaluate it.

Why this portfolio reality matters

Most of the confusion I see in CEP evaluations comes from mixing these worlds as if they were the same architecture.

They’re not.

So the key is not to ask: “Is Salesforce Marketing Cloud good?”

Ask: “Which Salesforce marketing world are we in, and which one are we moving toward?”

Salesforce’s CEP proposition in one sentence

Salesforce’s marketing stack (often branded today under an “Agentforce Marketing / Next‑Gen Marketing Cloud” narrative) is an enterprise engagement system anchored to CRM + Data Cloud, designed to orchestrate cross-channel journeys while connecting marketing decisions to sales/service/commerce context — and progressively shifting from marketer-built automations to agent-assisted (and eventually agent-driven) execution.

If you want a shorter version:

Salesforce is turning marketing into an extension of the CRM operating system with Data Cloud as the context engine and Agentforce as the intelligence layer.

A brief history: from ExactTarget to “Agentforce Marketing”

Salesforce entered modern digital marketing in a serious way in 2013, when it acquired ExactTarget, the foundation that would become the core of what most practitioners still recognize as “SFMC Engagement.”

This matters because it explains a lot of what you see today:

In parallel, Salesforce’s strategy evolved toward a unified data layer.

And then, in 2025, Salesforce accelerated an explicit shift:

So the history arc is simple:

Execution (ExactTarget) → Context (Data Cloud) → Intelligence (Agentforce)

The key takeaway: Salesforce is not rebuilding marketing from scratch. It’s re-platforming marketing around a data + AI narrative consistent with the broader Salesforce platform strategy, and the FY26 financials confirm the investment is not slowing down.

The Salesforce mental model (how I explain it internally)

I frame Salesforce marketing as a layered system.

If you get these layers right, the stack behaves like a loop.

If you mix them without a plan, it behaves like a portfolio.

Layer 1 System of record and operational context

This is the CRM layer:

The core advantage is that marketing doesn’t need to guess what the business is doing. It can read it.

In practical terms, it enables patterns like:

Layer 2 System of truth for customer signals

This is Data Cloud:

The hidden power of Data Cloud isn’t segmentation. It’s semantic alignment.

Once the enterprise agrees on what a customer is, what consent means, and what events represent intent, the marketing layer can stop being a set of disconnected lists.

Layer 3 System of action (journeys and activation)

This is where Marketing Cloud Engagement, Growth/Advanced, and Next‑Gen capabilities come into play:

In this layer, success is often less about features and more about pressure strategy:

Layer 4 — System of intelligence (Agentforce)

This is the layer that is now shipping, not just announced:

With Winter ’26 and Spring ’26 releases, the layer is expanding further: in-app messaging for mobile, sandbox testing for Marketing Cloud Next, improved campaign record unification between Engagement and Next, and new Agentforce Campaign Experience capabilities.

A Salesforce-centric CEP strategy is basically the attempt to make these layers feel like one loop:

signals → context → decision → activation → measurement → learning

What Salesforce Marketing is (and isn’t)

It is

It isn’t

Product posture today: two worlds, one roadmap

If you’ve worked with Salesforce Marketing Cloud for years, you’ve seen the split:

The key question for enterprises becomes:

Are we optimizing what we have (Engagement), or are we building toward the next-gen model (on-core + agents)?

In many programs, the real answer is: both.

And that’s where complexity shows up.

The real enterprise pattern: coexistence, not replacement

Most large organizations can’t “flip a switch.” They end up with a transition phase where:

That requires an explicit coexistence architecture, otherwise you get:

Salesforce has anticipated this with the Engagement+ upgrade path: existing Engagement customers keep their journeys, content, and data, while gaining access to smarter journey orchestration in Flow, unified campaign dashboards, and Marketing Cloud Next add-ons. The coexistence is now a product reality, not just a service engagement pattern.

A practical implementation pattern I’ve seen work

If I strip the marketing narrative away, Salesforce programs succeed when teams stage adoption like this:

1) Foundation: identity, data, permissions

Define what “customer truth” means and where it lives. Decide what Data Cloud unifies vs what stays operational. Align consent and preference enforcement across channels. Create a small event taxonomy with strong semantics.

It’s not glamorous, but it’s what enables the agentic layer later.

2) First activation loop: pick a narrow set of journeys

Connect 2–3 systems cleanly (don’t connect 12 badly). Measure with discipline (KPIs, and holdout mindset where possible). Formalize a basic pressure strategy.

This is where organizations learn the real bottleneck:
 It’s not that we can’t build journeys, it’s that we can’t keep journeys consistent.

3) Scale: governance and portfolio management

Prevent journey sprawl. Define ownership, lifecycle, QA and release processes. Implement templates and reusable patterns. Build a journey catalog.

At scale, governance becomes a product feature. If you don’t build it, you’ll relive the same incidents every month.

4) Agent layer: only after the system is reliable

Agents should optimize a stable system. If your baseline is inconsistent, AI just accelerates inconsistency.

Start with narrower agent use cases:
 documentation, anomaly detection, content operations, and conflict detection. Expand toward deeper decisioning only when you trust governance and constraints.

Recent financial context (why it matters for CEP decisions)

Salesforce’s story in FY26 has been defined by AI and data momentum translating into financial results.

A few waypoints that matter for the marketing portfolio:

Q1 FY26: Data Cloud crossed $1B ARR, up 120% year-over-year. Nearly half of the Fortune 100 became both AI and Data Cloud customers.

Q3 FY26 (Oct 31, 2025): Agentforce and Data Cloud combined ARR reached nearly $1.4B. Paid Agentforce deals were up 50% quarter-over-quarter. Salesforce raised full-year revenue guidance to $41.45B–$41.55B.

Q4 FY26 and full year (Jan 31, 2026, reported Feb 25, 2026):

As a practitioner, I interpret this less as “marketing is huge” and more as:

Salesforce is now financially obligated to push an agentic, platform-led marketing future. The roadmap is not a side quest, it’s the corporate growth narrative for FY27 and beyond.

In plain language, the Marketing Cloud Next direction is not experimental. It’s strategic, it’s funded, and it’s already shipping.

AI direction: “agentic marketing” is the product strategy

Salesforce is clearly betting that the next wave of marketing differentiation is not “better journeys,” but:

I’m not interested in the label.

I’m interested in the operational test.

The Agentforce test

If the system can’t pass those questions, the “agentic” layer stays a demo.

If it can, it becomes a durable differentiator.

Where I see immediate value (before “full autonomy”)

In real organizations, the first agent wins are usually pragmatic:

The last thing to automate is the thing with the highest blast radius: decisioning without constraints.

Competitive landscape: who Salesforce is really competing with

Salesforce competes on two axes at the same time.

1) The “enterprise execution suite” axis

Here, Salesforce is compared to other big-suite options:

Differentiators are usually: where identity and decisioning live, enterprise governance model, how tightly marketing connects to sales/service, and how mature the content supply chain and analytics integration become.

2) The “independent CEP” axis

Here, Salesforce gets compared to:

Differentiators are usually: speed and usability, mobile-first execution, experimentation maturity, developer friendliness vs admin complexity.

Salesforce’s core advantage across both axes

Salesforce is one of the few vendors that can credibly say:

“Your marketing engine can be native to the same platform as your commercial operations and your AI agents.”

That’s not always what a company should do, but it’s a compelling proposition when the business’s next advantage is expected to come from joining marketing, sales, service, and commerce into a single context loop.

Where Salesforce is strongest (a delivery-centric view)

Watch-outs I put in writing

The questions I ask early in Salesforce CEP evaluations

  1. Which marketing “world” are we in today (Engagement vs on-core/Next vs both)?
  2. What is the Data Cloud strategy (what data, what latency, what ownership)?
  3. How do we enforce consent and preferences across channels?
  4. How do we handle journey conflicts and prioritization?
  5. What is the release and QA model (dev/test/prod, approvals, rollback)?
  6. What is the measurement discipline (incrementality mindset, attribution expectations)?
  7. How will we prevent “journey sprawl” (catalog, templates, guardrails)?
  8. What is our coexistence plan: which capabilities stay in Engagement and which move to Next — and on what timeline?

What’s next

In the next parts, I’ll apply the same lens to other platforms (suite and independent) so the comparison stays consistent and practical.

Each article will go deeper into:

References & sources

  1. Salesforce FY26 Q3 Earnings (Dec 3, 2025): https://investor.salesforce.com/news/news-details/2025/Salesforce-Delivers-Record-Third-Quarter-Fiscal-2026-Results-Driven-by-Agentforce—Data-360/default.aspx
  2. Reuters on FY26 guidance and AI momentum (Dec 3, 2025): https://www.reuters.com/business/media-telecom/salesforce-raises-annual-revenue-forecast-2025-12-03/
  3. ExactTarget acquisition completed (2013 press release): https://www.salesforce.com/news/press-releases/2013/07/12/salesforce-com-completes-acquisition-of-exacttarget/
  4. Salesforce Genie announcement (Sep 20, 2022): https://www.salesforce.com/news/press-releases/2022/09/20/genie-news/
  5. Journeys and Automations in Marketing Cloud Engagement (Help docs): https://help.salesforce.com/s/articleView?id=mktg.mc_journeys_and_automations.htm&language=en_US&type=5
  6. Marketing Cloud Next announcement — End of ‘Do-Not-Reply’ Marketing (Jun 11, 2025):
    https://www.salesforce.com/news/stories/marketing-cloud-next-announcement/
  7. Next-Gen Marketing Cloud product details (Sep 10, 2025): https://www.salesforce.com/blog/next-gen-marketing-cloud-details/
  8. Next-Gen Marketing Cloud / Agentic Marketing page: https://www.salesforce.com/marketing/agentic-marketing/
  9. Marketing Cloud Growth & Advanced expansion (Jun 26, 2025): https://www.salesforce.com/blog/expanded-marketing-cloud-growth-advanced/
  10. Agentforce 360 partner expansion (Dec 2025): https://www.itpro.com/business/business-strategy/salesforce-announces-huge-partner-program-revamp-with-agentforce-360-launch
  11. Data Cloud Breaks $1B ARR Milestone in Q1 FY26 (SalesforceBen, Jun 2025): 
    https://www.salesforceben.com/data-cloud-breaks-1b-arr-milestone-in-q1-fy26-what-salesforce-leaders-need-to-know/
  12. Winter 2026 Salesforce release — Agentforce for Marketers (Martech.org, Aug 2025):
    https://martech.org/winter-2026-salesforce-release-will-be-heavy-on-agentforce-for-marketers/
  13. Top 10 Spring ’26 Updates for Salesforce Marketers (SalesforceBen, Jan 2026): 
    https://www.salesforceben.com/top-10-spring-26-updates-for-salesforce-marketers/