What MC-Con-201 assumes you already know
The Marketing Cloud Next Consultant exam went live in August 2026: sixty scored questions, 105 minutes, 72% to pass, no prerequisite certification. Salesforce pitches it at six to twelve months of hands-on Next work, and the largest section — Campaign Design, Flow Orchestration and Content — is thirty per cent of the paper on its own.
What the exam does not do is teach you the platform. It assumes you already know where Next sits, what the editions divide, and how the meters work. This e-book is that groundwork. It is not a question bank, and anything selling you one is a braindump that will cost you the credential.
Next is a toggle in your org, not a system you integrate
Marketing Cloud Next is not a separate instance. It is a set of capabilities switched on inside the Salesforce org you already run, stacked on Data 360, with Flow as the automation engine.
That one fact collapses most of the Engagement operating model. No connector to configure, because marketing reads the same Lead and Contact records Sales and Service write. No nightly sync, so no drift between two copies of the customer. No suppression file, because consent is a platform object checked on every send. No export to report, because engagement lands on the record the rep is already looking at.
The vocabulary survives. The mechanics do not.
Journey Builder becomes Salesforce Flow. Data Extensions become CRM records and Data 360 objects. Email Studio and Content Builder become a content workspace inside the org. Automation Studio and SQL become plain-language segments on scheduled or triggered flows.
The words carry over, which is what makes this dangerous. Journeys are not importable — every one is rebuilt. There is no AMPscript runtime on Next, so scripted personalisation is redesigned rather than ported. Data extensions are not lifted and shifted; they are modelled into Data 360 and CRM objects.
The meter that decides your bill is not the one you expect
Next is not priced per contact. It runs on consumption credits across four meters — email, Einstein requests, Data 360 Service, and segment and activation — and Growth and Advanced include different allocations of each.
Email and AI credits are predictable: one per send, one per request. Data 360 is the variable one, metered per million rows processed rather than per contact messaged. For a two-million-contact base with messy identity and always-on streaming, it can out-cost the entire email programme sitting on top of it. The worked example shows the same job built two ways, and the six levers that decide which bill you get.
What’s inside
- Where Next sits: Agentforce on Marketing Cloud Next on Data 360 on your CRM — and why every implementation starts with the data layer
- The six moves of a campaign run, and the four Engagement steps that disappear: connector, import, suppression file, export
- The full Marketing Cloud Engagement → Next translation table, and the list of what never carries over
- Growth vs Advanced line by line — which capabilities are edition-gated, and the add-ons that extend either
- All four credit meters with Growth and Advanced allocations, and how each one is actually metered
- A worked bill for a mid-market sender: the same job built two ways, and the six levers between them
- The “+” editions — Engagement+, Intelligence+, Personalization+ — what you keep and what switches on
- The six setup steps in order, who owns each, and a 90-day path from four different starting points
