Agentforce for Marketing: what Marketing Cloud Next actually automates, and what it doesn't

A marketer types “launch a win-back campaign for lapsed premium customers before the end of the quarter” into a prompt box, and a few minutes later there’s a campaign brief, a proposed audience, draft email and SMS copy that sounds like the brand, and a journey wired up in Flow — all sitting there waiting for a human to approve. That’s the demo Salesforce has been running all year for Marketing Cloud Next, and unlike a lot of agentic marketing theater, the core of it is genuinely shipping.

But the demo is also where the honest conversation ends and the hard questions begin. Is this the same Marketing Cloud you already own, or a different product you have to migrate to? Which of these agents are actually generally available versus in pilot? Does the agent that writes your emails cost you per email? And what happens to the ten years of AMPscript your team wrote? This post is the practitioner’s read on Agentforce for Marketing — what it is after the Connections 2026 rebrand, what the Campaign Creation Agent really does, and the migration, licensing, and credit realities that decide whether it’s worth moving.

The naming, untangled

Start here, because Salesforce has renamed this product enough times to confuse everyone. As of the Connections 2026 keynote (June 2026), the hierarchy settled into three layers: Agentforce Marketing is the umbrella brand, Marketing Cloud Next is the product, and Growth and Advanced are its two editions. When someone says “Agentforce for Marketing,” they mean Marketing Cloud Next with its agents turned on.

The structurally important fact underneath the branding is that Marketing Cloud Next is “Marketing Cloud on Core.” Legacy Marketing Cloud Engagement — the product most people still call SFMC — runs on the separate ExactTarget infrastructure Salesforce acquired years ago, with its own data model, its own APIs, and its own scripting language. Marketing Cloud Next is built on the core Salesforce platform and Data 360, using the same metadata and data model as the rest of your org, with orchestration handled by Salesforce Flow rather than the old Journey Builder. That single architectural decision is what makes the agents possible: an agent can reason over a unified customer profile and build a journey in Flow because the customer data and the automation engine finally live in the same place. It’s also what makes the migration non-trivial, which we’ll get to.

What the Campaign Creation Agent actually does

The marquee capability, and the one that’s already released rather than in pilot, is the Campaign Creation Agent. It runs a marketer through campaign build as a guided, conversational flow, and it’s worth being precise about the four things it produces:

• A campaign brief. You describe the goal in natural language — the audience you’re after, the offer, the timing, the outcome — and the agent drafts a structured brief you edit rather than author from scratch.
• An audience. You describe the target in plain language (“customers who bought in the last year but not the last quarter, premium tier”), and the agent translates that into segment attributes across your unified Data 360 data. No SQL, no hand-built segment query. Because the segment sits on Data 360, it can refresh dynamically as the underlying signals change.
• On-brand content. Draft email, SMS, and WhatsApp copy generated against your brand identity and tone — pulled from Brand Center, not invented — so the output reads like your brand rather than generic model prose.
• A journey. The campaign flow itself, assembled in Flow, ready to review and activate.

Underneath, this is the same machinery we’ve written about elsewhere, pointed at marketing. The Atlas reasoning engine runs the plan-retrieve-execute loop; the on-brand copy leans on grounded Prompt Builder templates so the generation stays anchored to real brand guidelines instead of drifting into fiction; and the whole thing is only as good as the Data 360 grounding beneath it. The audience-building step in particular is segmentation and activation with a natural-language front end — the agent isn’t inventing a new segmentation engine, it’s writing to the one Data 360 already has.

The honest framing: the Campaign Creation Agent compresses the assembly work — brief, first-draft audience, first-draft copy, journey scaffold — from a multi-day cross-functional exercise into a guided session. It does not remove the marketer. Every artifact it produces is a draft that a human reviews, corrects, and approves before anything sends. Treat it as a very fast junior teammate, not an autonomous campaign manager.

The agents still in pilot — don’t build a plan on them yet

This is where a lot of the Connections 2026 excitement gets ahead of what you can actually deploy. Two of the headline marketing agents were, as of mid-2026, in pilot, not GA:

• The Content Agent generates omni-channel content from a campaign description — email, mobile, SMS, RCS conversations, personalized promotions — with localization handled inside the same workflow, one of several marketing agents Salesforce unveiled at Connections 2026. Powerful, and clearly where content operations are heading, but a pilot feature is not something to put on a Q3 roadmap as a dependency.
• The Marketing Goals Agent (also referred to as a Marketing Expert Agent) is the genuinely autonomous one: you set goals, budgets, guardrails, and autonomy limits, and it creates, executes, and continuously optimizes campaigns toward a business outcome. The pitch is “manage agents, not workflows.” The reality in mid-2026 is a pilot with a small set of design partners.

The distinction matters for planning. The Campaign Creation Agent is something you can pilot in your own org today; the Content Agent and Marketing Goals Agent are capabilities to design toward, verifying their status against current release notes before you commit. Salesforce’s release cadence moves fast enough that “pilot” and “GA” can flip between seasons — but building a rollout on a feature that’s still gated is how marketing-ops timelines slip. And if your roadmap also touches sales prospecting, note that the SDR-style agents announced alongside these (the inbound and outbound prospecting agents from the Qualified acquisition) are a separate product family with separate licensing — not part of Marketing Cloud Next.

A pilot feature is a promise, not a capability. Design your architecture so the released agent carries the workload today and the pilots slot in when they ship — never the reverse.

The pricing has two meters, and the boundary between them is fuzzy

Here’s where you need to read carefully, because Agentforce for Marketing bills on two different meters at once, and Salesforce’s own materials don’t draw the line between them as cleanly as a budget owner needs.

Meter one is the edition license. Marketing Cloud Next is reported to start at roughly $1,500 per org per month for Growth and $3,250 per org per month for Advanced, both billed annually, with Advanced adding path experimentation, predictive scoring, and two-way SMS/WhatsApp. Treat those as widely-reported figures, not gospel — pull the current pricing page before you build a business case, because Salesforce revises marketing SKUs frequently and edition contents shift between releases.

Meter two is Flex Credits, the consumption model that governs Agentforce actions across the platform. As we break down in the Agentforce pricing guide, a pack of 100,000 Flex Credits lists at $500 (half a cent each), a standard agent action runs about 20 credits — roughly $0.10 — and interactions that trigger no action generally incur no charge.

The fuzzy part is the seam. Salesforce says every edition “includes Agentforce Campaign Creation,” yet Agentforce broadly meters actions on Flex Credits. The most likely reconciliation — the in-builder Campaign Creation Agent comes with the license while higher-volume or autonomous agent actions draw down Flex Credits — is not cleanly documented anywhere I could verify. So the practical guidance is: do not assume the agents are free because they’re “included,” and do not assume every generation is metered either. Turn on consumption visibility, run a realistic pilot, and watch what the agents actually cost against a real campaign calendar before you extrapolate to the whole marketing team. An agent that drafts a hundred content variants a week has a very different credit profile from one that builds a campaign a fortnight, and only your own usage tells you which you’ve got.

The migration reality: convergence, not a cutover

The question every existing Marketing Cloud customer asks first: do I have to move? The reassuring-but-complicating answer is that this is a convergence, not a forced migration. As of mid-2026, legacy Marketing Cloud Engagement has no announced sunset date, and Salesforce fully expects customers to run MCE and Marketing Cloud Next in parallel for an extended period.

The complicating half is that there is no automated migration path, and the two products are architecturally different enough that “migration” means “rebuild.” Journeys, email templates, automations, data extension schemas, and API integrations all have to be re-created on the new platform — you are not lifting-and-shifting, you are re-implementing on a different data model with a different orchestration engine. For an org with years of SFMC investment, that is a real project, not a settings toggle.

And there’s a specific gotcha that has kept plenty of teams on the legacy engine: AMPscript. Marketing Cloud Next launched without AMPscript support at all, which for AMPscript-heavy senders effectively required an “MCE+ Bridge” pattern — build in Next, send through the legacy engine — to preserve dynamic content logic. The Summer ‘26 release added partial AMPscript support, but reported as only around 30% of functions, read-only (no updates), with no API calls and no SMS AMPscript functions. If your personalization depends on AMPscript doing real work at send time, verify function-by-function that your templates survive the move before you commit a migration date. This is exactly the kind of source-by-source audit that belongs in a data and AI strategy engagement rather than a go-live checklist discovered the week before launch.

The skepticism worth taking seriously

Two critiques of agentic marketing are worth internalizing before you buy the vision wholesale.

The first is agent proliferation. Salesforce keeps adding agents — a campaign agent, a content agent, a goals agent, prospecting agents — and thoughtful voices in the community have started asking how many agents is too many, warning about the operational fatigue of managing an agent per workflow. The antidote is the same fleet-governance discipline that applies to service and IT agents: every marketing agent needs a named owner, a scoped purpose, and a reason to exist beyond “it was in the keynote.” Adding an agent because it demos well is how you end up with a swarm nobody governs.

The second is autonomy calibration. Marketing is a domain where a confidently wrong action — a mistargeted send, an off-brand promotion, a discount to the wrong segment — reaches customers and can’t be recalled. The Marketing Goals Agent’s premise of setting budgets and guardrails and letting it optimize is genuinely appealing, but it’s also precisely the place to insist on a human-in-the-loop approval gate for anything that spends money or hits a customer inbox. The right pattern for the near term is agent-drafts, human-approves, especially while the autonomous agents are still maturing out of pilot. You can widen the autonomy as the agent earns trust; you cannot un-send a campaign.

What to actually do this quarter

If you’re on legacy Marketing Cloud and being pushed toward Agentforce for Marketing, resist treating it as an upgrade and treat it as a platform decision. Stand up Marketing Cloud Next alongside your existing MCE — the convergence model expects exactly that — and pilot the Campaign Creation Agent on a real, low-stakes campaign to feel the assembly speed-up first-hand. Before you plan any broader migration, run the two audits that actually determine feasibility: an AMPscript function audit against your real templates, and a credit-consumption read from the pilot so you know which of the two meters your usage lands on. Ground the agents properly on Data 360 and Brand Center, because the campaign-from-a-sentence magic is entirely a function of the data and brand definitions underneath it — thin grounding produces confident, generic, wrong campaigns just as reliably as it produces bad service answers.

And keep the pilots in their lane. The Campaign Creation Agent can carry real work today; the Content Agent and Marketing Goals Agent are things to design toward and verify against current release notes, not dependencies to bet a launch on. Do that, and Agentforce for Marketing is a legitimate acceleration of the grinding assembly work that eats marketing teams’ weeks. Skip the audits and buy the autonomous vision before it’s GA, and you’ve bought a rebuild you didn’t scope and a credit bill you didn’t forecast. The demo is real. The discipline is what makes it pay.

Understanding the basics

What is Agentforce for Marketing?

Agentforce for Marketing is Salesforce’s agentic marketing offering, delivered through Marketing Cloud Next — a rebuild of Marketing Cloud on the core Salesforce platform and Data 360, with orchestration in Flow. Its headline capability is the Campaign Creation Agent, which turns a natural-language goal into a campaign brief, a Data 360 audience, on-brand email/SMS/WhatsApp content, and a journey, all as drafts a marketer reviews and approves. Additional agents for content generation and autonomous goal-based optimization were in pilot as of mid-2026.

Is Marketing Cloud Next the same as Marketing Cloud Engagement?

No. Marketing Cloud Engagement (legacy SFMC) runs on separate ExactTarget infrastructure with its own data model and AMPscript scripting. Marketing Cloud Next is built on the core Salesforce platform and Data 360 with Flow-based orchestration. As of mid-2026 they coexist — there’s no announced sunset for Engagement and no automated migration path — so moving between them means rebuilding journeys, templates, automations, and integrations rather than lifting and shifting.

How much does Agentforce for Marketing cost?

There are two meters. The Marketing Cloud Next edition license was reported to start around $1,500 per org per month for Growth and $3,250 for Advanced, billed annually. Separately, Agentforce actions are metered on Flex Credits — about $0.10 per standard action at $500 per 100,000 credits. The boundary between what the edition includes and what draws down credits isn’t cleanly documented, so verify current pricing on Salesforce’s site and measure real consumption in a pilot before budgeting.

---

Weighing a move to Marketing Cloud Next, or trying to figure out whether the Campaign Creation Agent earns its place against your real campaigns and AMPscript investment? Talk to us — grounding agents on Data 360 and drawing the migration line honestly is exactly the work we do.