Skip to content
EN DE
Book a 30-min fit check

By platform

Marketing Cloud Next Account Engagement (Pardot) Marketing Agentforce & AI Data foundation & Data 360

By need

Lead scoring & sales handoff Email deliverability Sync & data quality Migration readiness Double opt-in & DSGVO Webinars, templates & more

Start here

All 30 packages & pricing Express Health Check — €900 FAQ

By sector

Manufacturing & Industrial Software & SaaS IT & Professional Services Financial Services & Insurance Healthcare & MedTech Energy & Utilities Education & Training

Start here

All industries Express Health Check — €900 Book a 30-min fit check

Platform decisions

Account Engagement vs Marketing Cloud Next Engagement vs Next Growth vs Advanced Account Engagement vs HubSpot

Decide faster

Product Finder — 3 min, no email 12-point AE health checklist

Read

All articles Release Radar: MC Next Name Decoder Is Pardot still worth it? Salesforce Cloud

Check yourself

Migration Size Estimator Lead Scoring Simulator Data Cloud Cost Estimator Database Cost Check AI Readiness Score Agentforce Pilot Readiness

Utilities

HTML → Text Converter Deliverability DNS Check Merge-Field Checker Import Pre-Flight Check All 13 free tools The 12-point Account Engagement health check

MWCS

About MWCS Contact

Legal

Imprint Privacy Terms of Use
Book a 30-min fit check

MWCS

Marketing Cloud Next Release Radar — MWCS

Marketing Cloud Next Release Radar

Release Radar · Marketing Cloud Next

Updated August 2026 · maintained page — bookmark it

Summer ’26: the release that changed the migration math

Salesforce went all-in on Marketing Cloud Next this release — and quietly crossed a line that changes real decisions: feature parity for Account Engagement users is now largely a solved problem, and the gap for Marketing Cloud Engagement users narrowed sharply. Here is every update that matters, what it actually means for your team, and what we would verify before relying on it. Sources: the official release notes and ecosystem coverage by Salesforce Ben.

The big one

AMPscript arrives in MC Next

Years of scripting know-how survives the move: AMPscript now works alongside Handlebars for CRM and profile data in email content — with in-editor validation, so syntax errors surface before send time, not after.

Who cares most: MCE/ExactTarget teams with AMPscript estates

AE users, look

Signup form campaigns & lists

The Account Engagement pattern — form, completion action, list, send — now exists natively in MC Next. CSV uploads and manual list membership included. Segmentation without Data 360 logic for the simple cases.

Who cares most: Pardot teams eyeing the move

New channel

RCS as a content type

Rich cards, carousels and suggested-reply buttons in the native messaging app — a genuine step past static SMS. After sender verification it becomes a reusable CMS content type.

Who cares most: high-volume B2C and event-driven senders

New agents

Account Nurturing + Distributed Marketing agents

Nurturing that adapts to what sales is actively working: buying-group identification and orchestrated touchpoints as opportunities progress, plus template surfacing for sales users.

Who cares most: RevOps-minded B2B teams

Sales alignment

Engagement history on opportunities

A unified engagement dashboard on the opportunity record: emails, forms and web activity for every contact tied to the deal. Reps see buyer intent without asking marketing for a report.

Who cares most: everyone with a sales team

Commerce-flavored

Marketing triggers & personalized offers

Abandoned cart, price drop, back-in-stock and order-lifecycle triggers with dynamic offers in email. Powerful — and mostly relevant to transaction-driven models, less so to long sales-led cycles.

Who cares most: e-commerce and hybrid models

Ops speed

Flow template library + Slack campaign channels

Preconfigured automation templates launchable from the campaign record, and campaigns that spin up their own Slack workspace with AI task assistance. Campaign ops keeps moving into Slack.

Who cares most: teams already living in Slack

Under the hood

Consent mapping rollout

Email consent mapping lands mid-July, SMS/WhatsApp mid-August — the unglamorous plumbing that decides whether your DSGVO story survives the platform transition intact.

Who cares most: every DACH org, full stop

The honest read

What this release actually signals

Compared to previous releases that spread updates across the whole portfolio, Summer ’26 concentrates almost everything on Marketing Cloud Next — while updates to the legacy products (ExactTarget, Pardot, Personalization, Intelligence) are visibly muted. Read the trajectory, not the press release:

●For Account Engagement teams: parity is no longer the blocker. The real questions are data foundation and consent migration — exactly the things no release note fixes for you.
●For MC Engagement teams: AMPscript support removes the biggest rebuild objection. The journey and data-model rebuild remains real work.
●For everyone: the platform is barely a year old and patterns are still settling. Verify each capability against your use case in a sandbox before building the business case on it.

Decide with the full picture

Release questions, answered honestly

Does AMPscript in MC Next mean our MCE code migrates as-is?

No — it means the language survives, not the estate. Scripts referencing data extensions and platform objects still need rework against the new data model. The win is that your team keeps its skill set and many patterns port with modest changes rather than full rewrites.

Is feature parity for Account Engagement really "done"?

For the core B2B automation patterns — forms, lists, completion-action-style flows, scoring-adjacent logic — the gap has closed substantially, and Summer ’26 addressed several of the last everyday friction points. Edge cases remain; inventory yours before deciding. Our free migration estimator turns that inventory into a size class in minutes.

Should we wait for more releases before moving?

Waiting is legitimate only with written trigger conditions — otherwise it is drift. The framework we use: document what would change your answer, review quarterly, and build the data foundation now, because it pays off regardless of the platform decision.

Do the new agents work without Data 360?

The useful ones lean on unified profiles and grounded content. Narrow record-based jobs work against CRM data, but nurturing and audience agents are only as good as the data model underneath — which is why readiness, not licensing, is the real gate.

Want the release read against YOUR org?

A readiness assessment turns release notes into a decision: what applies to you, what to verify, what to ignore. Analysis-only, fixed price, credited against any follow-on package.

Scroll to Top