N00 — Start Here: Marketing Cloud Next, Zero → Hero

🎯 Why this course exists: Salesforce's future marketing stack is Marketing Cloud Next — the Growth/Advanced editions built on Core + Data Cloud (Data 360), in the Agentforce era. Almost nobody interviewing today knows it. Your 4 years of classic Engagement plus genuine MC-Next fluency is a rare, hireable combination. This course takes you from never touched Core to can build and talk through a full campaign — zero to hero.

---

⚠️ The currency rule (read first)

MC Next is new and changes every release (Data Cloud was renamed Data 360 in Oct 2025; AMPscript arrived only as a limited subset in Summer '26; Agentforce branding is fluid). So:

• Every module ends with a currency note — trust it.
• Re-verify against current Salesforce release notes before any interview.
• Say "Data 360," "Flow-based journeys," "Handlebars-first personalization" — you'll sound current, not dated.
• Don't abandon classic. Most roles you interview for today still run Engagement — keep the other courses sharp. MC Next is your differentiator, not a replacement.

---

🧠 The 3 shifts that change everything

   CLASSIC ENGAGEMENT                     MARKETING CLOUD NEXT
   ------------------                     --------------------
   Data Extensions + SQL      ─────▶      Data Cloud (Data 360): DLO→DMO,
   (you build the tables)                 Identity Resolution, Segments

   Journey Builder            ─────▶      Salesforce FLOW (on Core)
   (drag-drop canvas)                     (Flow Builder + Data Cloud segments)

   AMPscript everywhere       ─────▶      Handlebars {{merge}} + limited AMPscript
   (%%= =%% scripting)                    subset + Einstein generative content

Internalise these three swaps and most of MC Next clicks into place. N12 is the full bridge.

---

🗺️ The zero-to-hero ladder (17 modules)

---

🎓 The naming cheat (memorize — interviewers test currency)

• Marketing Cloud Engagement (MCE) — classic ExactTarget-derived B2C (what you know).
• Marketing Cloud Growth / Advanced — the new editions on Core + Data Cloud ("Marketing Cloud Next"). Advanced adds Path Experiments, engagement scoring/frequency, more channels.
• Data 360 — the new name for Data Cloud (the data engine).
• Marketing Cloud Personalization — ex-Interaction Studio. Marketing Cloud Intelligence — ex-Datorama. Account Engagement — ex-Pardot (B2B).
• Agentforce Marketing — the umbrella AI/agent branding across the suite.

---

🕒 Suggested plan (zero → hero in ~8 weeks)

• Weeks 1–2 (Foundations + Data): N01→N04, plus N13 labs L1–L4 in a free Trailhead Playground.
• Weeks 3–5 (Build): N05→N08, labs L5–L9 — this is where practical fluency comes from.
• Weeks 6–8 (AI + Run + Pivot): N09→N12, labs L10–L12, start the N14 cert path.
• Ongoing: N15 rapid-fire out loud weekly; N16 before any conversation about the new stack.

---

🎤 The one answer to have ready today

"Have you worked with Marketing Cloud Next?"

"My production depth is classic Engagement — four years of AMPscript, SSJS, and Journey Builder at GAP. I'm actively building on the new stack: I understand the architecture shift — Data 360's DLO-to-DMO pipeline with identity resolution replacing Data Extensions and SQL, Flow replacing Journey Builder, Handlebars-first personalization with the new limited AMPscript subset — and I'm working through Data Cloud and Agentforce hands-on labs. That combination means I can run today's platform and help migrate to tomorrow's."

Honest, current, and better than what 95% of candidates say. The rest of this course makes every clause of it true.

📖 How to use this reader

Dark by default. One section at a time; ← / → or Prev/Next. / searches. ⏱ paces (set the goal to ~10h for the full ladder). ☆ / M marks for review. Bold = key term, green bold = "say this", cyan italic = nuance.

➡️ Next: N01_Landscape_and_Naming_Map.md

N01 — The Marketing Cloud Next Landscape

🎯 Why this matters: Salesforce has three overlapping "Marketing Cloud" naming waves stacked on top of each other — get the map straight once and every interview question about "the new stack vs. what you know" becomes easy.

---

🧠 One-screen mental model

There are two engines (classic vs. native-on-core) living side by side, plus a shared data + AI layer underneath, plus a wrapping brand name on top. Hold that shape and the rest is detail.

                    ┌──────────────────────────────────────────────┐
                    │   BRAND WRAPPER (Dreamforce '25):            │
                    │   "Agentforce Marketing"  = the whole suite  │
                    └──────────────────────────────────────────────┘
                                        │
        ┌───────────────────────────────┴───────────────────────────────┐
        │                                                                 │
  ┌─────────────────────────┐                     ┌──────────────────────────────────────┐
  │  CLASSIC ENGINE          │                     │  NATIVE-ON-CORE ENGINE               │
  │  (ExactTarget-derived)   │                     │  = "Marketing Cloud Next" (MCN)       │
  │                          │                     │    the vision/platform name            │
  │  • Marketing Cloud       │                     │                                        │
  │    ENGAGEMENT (MCE)      │  ← what Akash knows │   Editions you actually BUY:           │
  │    (email/SMS/Journey    │                     │   • Marketing Cloud GROWTH   (SMB)     │
  │     Builder/AMPscript/   │                     │   • Marketing Cloud ADVANCED (Ent.)    │
  │     SSJS on its own      │                     │                                        │
  │     Stack 1..n infra)    │                     │   Runs INSIDE core Salesforce +        │
  │                          │                     │   Flow, no separate SFMC login         │
  │  • Account Engagement    │                     │                                        │
  │    (ex-Pardot, B2B)      │                     │                                        │
  └─────────────────────────┘                     └──────────────────────────────────────┘
        │                                                                 │
        └───────────────────────────────┬───────────────────────────────┘
                                         │
              ┌──────────────────────────────────────────────────┐
              │  SHARED DATA + AI LAYER                            │
              │  • Data Cloud  (now "Data 360")  — the data engine │
              │  • Personalization (ex-Interaction Studio)         │
              │  • Intelligence    (ex-Datorama)                   │
              │  • Agentforce agents (Campaign Creation, etc.)     │
              └──────────────────────────────────────────────────┘

---

🔑 Core in 60 seconds

• Marketing Cloud Engagement (MCE) = the classic, ExactTarget-derived B2C stack you already know — Email/Mobile Studio, Journey Builder, AMPscript, SSJS, Contact Builder — running on its own dedicated SFMC infrastructure with its own login (not core Salesforce).
• "Marketing Cloud Next" (MCN) is the vision / platform name for the newer, ground-up rebuild that runs natively on the core Salesforce platform + Flow, with Data Cloud as its data foundation. You don't buy a SKU literally called "Next."
• The editions you actually license under that line are Marketing Cloud Growth (SMB / entry) and Marketing Cloud Advanced (enterprise). Both sit on the same Data Cloud + Core + Flow foundation; Advanced just unlocks more.
• Advanced adds over Growth: Path Experiments (structured A/B testing), account scoring (rollups for ABM, on top of Growth's people scoring), broader cross-channel (two-way SMS, push, ads in one flow), more advanced segmentation/analytics, and a larger native credit allotment. (Verify exact feature lines per current release — see currency note.)
• Data Cloud is the data engine underneath everything — recently rebranded "Data 360." MCN requires it (provision Data 360 + credits).
• Marketing Cloud Personalization = ex-Interaction Studio (real-time 1:1 web/app personalization). Marketing Cloud Intelligence = ex-Datorama (cross-channel marketing analytics). Account Engagement = ex-Pardot (B2B).
• "Agentforce Marketing" is the umbrella brand (Dreamforce '25) over the whole marketing suite — it wraps MCE, Account Engagement, and MCN; it is not a separate product replacing them.
• No MCE sunset / end-of-life has been announced. Salesforce positions MCN as available alongside MCE ("convergence," not forced migration), and Data 360 + Agentforce + MCN are offered to existing MCE/MCAE customers at no extra license cost.

---

🧩 Mnemonics & memory hooks

• "Next is a vision, Growth & Advanced are the invoices." — MCN is the platform name; the two editions are what appears on the contract.
• "E for Engagement = ExactTarget = Existing." All three start with E — the classic B2C stack you already run.
• G < A — Growth is the smaller/simpler edition; Advanced is the bigger one. Alphabetical order = feature order.
• Rename decoder — "I⁴ became boring": Interaction Studio → Personalization; Datorama (Intelligence-ish) → Intelligence; Pardot → Account Engagement; Data Cloud → Data 360. New names describe the job, not a codename.
• "Agentforce is the coat, not the body." Agentforce Marketing is the branded coat draped over the whole suite — under it, the actual products are still MCE / Account Engagement / MCN.
• "Old stack = own house; new stack = spare room in Salesforce's house." MCE has its own infrastructure/login; Growth/Advanced live inside core Salesforce.

---

🔁 Coming from classic Engagement

Key mental shift: in classic MCE, you are the automation engine (write the SQL, the AMPscript, the journey). In MCN, Data Cloud is the source of truth and Agentforce agents draft the work — you supervise and approve.

---

🎤 Rapid-fire

1. Q: Is "Marketing Cloud Next" a product you buy? A: No — it's the vision/platform name. You buy the Growth or Advanced edition.

2. Q: What's the classic stack you already know officially called now? A: Marketing Cloud Engagement (MCE) — the ExactTarget-derived B2C platform.

3. Q: What do Growth and Advanced both run on? A: The same foundation: Data Cloud + core Salesforce + Flow (not the old SFMC infrastructure).

4. Q: Name three things Advanced adds over Growth. A: Path Experiments (A/B testing), account scoring (ABM), and broader cross-channel (two-way SMS, push, ads) + larger credit package. (Verify per current release.)

5. Q: What were Personalization and Intelligence called before? A: Personalization = Interaction Studio; Intelligence = Datorama.

6. Q: What is "Agentforce Marketing"? A: The umbrella brand (Dreamforce '25) over the entire marketing suite — MCE, Account Engagement, and MCN. Not a standalone replacement product.

7. Q: Has Salesforce announced an end-of-life for MCE? A: No. MCN runs alongside MCE; Salesforce frames it as convergence, not forced migration.

8. Q: What's the data engine under the new stack, and what's its current name? A: Data Cloud, recently rebranded Data 360 — and MCN requires it.

---

⚠️ Gotchas / currency note

• Naming is layered and still shifting. "Marketing Cloud Next" (platform vision), "Growth / Advanced" (editions), and "Agentforce Marketing" (brand) all point at overlapping things. Interviewers may use them loosely — clarify which layer they mean.
• Growth vs. Advanced feature boundaries move release-to-release. Items like WhatsApp, specific AI/experimentation features, and credit allotments were still landing/announced through 2025. Re-verify the exact split for Advanced vs. Growth against the current Salesforce release notes before an interview — do not quote a fixed feature list as permanent.
• "Agentforce Marketing" as a blanket rebrand is recent (Dreamforce, Oct 2025) and messaging is still settling; some docs say "not a rebrand, an umbrella." Say "umbrella brand over the suite" and you're safe.
• Data Cloud → "Data 360" rename is also recent (part of "Agentforce 360" positioning). Both names appear in the wild; mention it's the same engine.
• No MCE sunset is announced — but investment is visibly shifting. Community reads recent MCE release notes as light. Frame it as "no announced EOL; strategic focus is moving to the Data-Cloud-native line" — accurate and defensible.
• MCN is genuinely new and fast-changing. When unsure of a detail, say so and cite the release notes rather than inventing a capability.

---

Sources

• Salesforce Ben — Salesforce Reveal Marketing Cloud Next: Agentic Marketing
• Salesforce Ben — Marketing Cloud Growth vs. Advanced Editions: Comparing Key Features
• Salesforce Ben — Salesforce Renames 6 Marketing Cloud Products (Interaction Studio → Personalization, Datorama → Intelligence)
• Salesforce Ben — Salesforce Data Cloud Renamed to 'Data 360' as Part of 'Agentforce 360'
• Salesforce Ben — Will Marketing Cloud Growth Retire ExactTarget? (no MCE EOL announced)
• Salesforce Ben — How Salesforce Is Rebuilding Marketing Cloud for the Age of AI
• Salesforce Blog — Next-Gen Marketing Cloud: Product Details, Availability and Pricing
• Salesforce — Agentic Marketing Platform: Marketing Cloud Next
• Clevertouch — What is Agentforce Marketing?
• Marcloud Consulting — Pardot Renamed Marketing Cloud Account Engagement
• The Spot for Pardot — Getting Started with Marketing Cloud Growth and Advanced
• The Agentic Marketer — Growth vs. Advanced: Key Differences and Field Insights (2025)

---

➡️ Next: N02_Core_Platform_Foundations.md

N02 — Core Salesforce Platform Foundations (for the MC-Next marketer)

🎯 Why this matters: This is your true "zero" rung. Marketing Cloud Next is not a separate product with its own login — it's an app running inside a core Salesforce org, and every screen you'll touch (Campaigns, Flows, Segments, Setup) is a core-platform screen. You've spent 4+ years in ExactTarget infrastructure and never once clicked around core Salesforce; an interviewer will notice if you can't say "App Launcher", "Object Manager", or "permission set" fluently. Nail this module and every later module stops feeling foreign.

---

🧠 One-screen mental model

Core Salesforce is a stack: Org → App → Tab → Object → Record → Field, with Setup as the control plane hanging off the side.

 YOUR ORG = one tenant of Salesforce (production login: login.salesforce.com)
 ┌────────────────────────────────────────────────────────────────────┐
 │  LIGHTNING EXPERIENCE  (the standard UI)                            │
 │                                                                      │
 │   APP LAUNCHER (9-dot "waffle" icon, top-left)                       │
 │        │   pick an APP = a branded bundle of tabs                    │
 │        ▼                                                             │
 │   ┌─────────┬─────────┬────────────────────────────────┐            │
 │   │  Sales  │ Service │  MARKETING CLOUD ◀ MC Next     │            │
 │   └─────────┴─────────┴──lives here as an app──────────┘            │
 │        │   each TAB usually opens an OBJECT                          │
 │        ▼                                                             │
 │   OBJECT (e.g. Contact) ≈ a Data Extension with superpowers          │
 │    ├─ FIELDS       = columns  (standard, or custom ending __c)       │
 │    ├─ RECORDS      = rows     (every row has a unique Id)            │
 │    └─ PAGE LAYOUT / LIGHTNING RECORD PAGE = how one row is shown     │
 │                                                                      │
 │   ⚙️ SETUP (gear icon, top-right) = the CONTROL PLANE:               │
 │      Object Manager · Users · Profiles & Permission Sets ·           │
 │      Flows · Sandboxes · nearly everything an admin configures       │
 └────────────────────────────────────────────────────────────────────┘
   Safe copies of the org for testing  = SANDBOXES (test.salesforce.com)
   The plug-in marketplace             = APPEXCHANGE

---

🔑 Core in 60 seconds

• Org = your tenant. One org holds all your data, config, code, and users. Production lives at login.salesforce.com; sandboxes at test.salesforce.com. Roughly the analog of your whole MC account (parent + BUs), not one BU.
• Lightning Experience = the standard UI. Tab bar on top, gear ⚙️ icon (top-right) for Setup, 9-dot App Launcher (top-left) to jump anywhere. You can search any app, tab, or item from the App Launcher search box.
• App = a bundle of tabs. Sales, Service, Marketing Cloud — same org, different tab sets. Marketing Cloud Next is just an app here, with tabs like Campaigns, Flows, Content, Segments, Analytics/Marketing Performance, Consent (Marketing Cloud Next — Salesforce Help). Missing tabs usually means they're not set to Default On for your profile (Missing tabs KB).
• Objects & records = your new tables. Standard objects (Contact, Lead, Account, Campaign, Opportunity) ship with the platform; custom objects (API name ends __c) you build yourself. Fields = columns, records = rows, Object Manager (inside Setup) is where you inspect/extend them. Page layouts / Lightning record pages control how one record is displayed.
• Users → Profiles → Permission Sets. Every human is a User with exactly one profile (baseline) plus any number of permission sets (additive grants), bundled into permission set groups ("personas"). 2026 best practice: Minimum Access profile + permission sets for everything — but note the planned Spring '26 retirement of permissions on profiles was officially cancelled (Retirement cancelled — Salesforce KB).
• Reports & dashboards are built-in. A report = saved query over a report type (object + its relationships) with filters, groupings, charts. A dashboard = grid of widgets, each fed by a report. No more exporting DEs to prove campaign results.
• Sandboxes = org copies for safe testing. Four types by data volume: Developer → Developer Pro → Partial Copy → Full. Since Winter '26, Marketing Cloud Next itself works in sandboxes (all types; Mobile App Messaging excluded at launch) (SFMC Tips #196).
• AppExchange = the app store. Managed packages install features into your org (like MC Marketplace/HubExchange once did, but vastly bigger).
• Flow Builder = the automation engine — and effectively your new Journey Builder. Campaigns in MC Next generate flows; you must be fluent in the canvas, elements, and debugging.
• SOQL = the platform's query language. Read-only awareness for now: it queries one object at a time with relationship traversal instead of JOINs. Your Automation Studio SQL instincts mostly transfer, with sharp edges (below).

---

🧩 Mnemonics & memory hooks

• The stack: "Only Apps Take Objects' Records' Fields" → O-A-T-O-R-F — Org → App → Tab → Object → Record → Field. Say it once whenever you're lost: "where am I in OATORF?"
• Security triangle: "Roles SEE, Profiles DO, Permission sets ADD." Roles control which records you see; profiles are the baseline of what you can do; permission sets add extra powers on top (DESelect 2026 guide).
• Object = "DE with superpowers." A DE was a dumb table; an object also carries security, relationships, page layouts, and automation triggers for free.
• __c = "custom carries a suffix." See Loyalty_Tier__c? Custom field. See Email? Standard. Two underscores, one letter — instant classification in any interview screenshot.
• Flow element families: "I Love Data (and I Wait)" → Interaction (Screen, Action) · Logic (Decision, Assignment, Loop, Collection) · Data (Get/Create/Update/Delete Records) · Wait (Wait/Pause). Four drawers on the canvas palette.
• Sandbox sizes: "Dev, Dev Pro, Partial, Full — data grows as you go." Config copies first, then samples of data, then everything.
• SOQL: "No star, no JOIN, one FROM." You must list fields, you traverse relationships with dots/subqueries, and you query exactly one base object.

---

🔁 Coming from classic Engagement

---

🛠️ In practice (what you would actually click)

A. Get your bearings (first 5 minutes in any org) 1. Log in at login.salesforce.com (or test.salesforce.com for a sandbox). 2. Top-left: click the 9-dot App Launcher icon → a search box + app grid opens. 3. Type Marketing → click the Marketing Cloud app → tab bar changes to Campaigns · Flows · Content · Segments · Analytics… (exact tabs are profile-dependent; edition: Growth/Advanced only). 4. Top-right: click the gear ⚙️ icon → Setup. Setup opens in a new tab with a Quick Find box (top-left) — this box is how admins navigate; almost never the menu tree.

B. Explore an object (your "SELECT TOP 10" instinct) 1. In Setup, click Object Manager (tab at the top, next to Home). 2. Click Contact → left nav shows Fields & Relationships, Page Layouts, Lightning Record Pages, etc. 3. Click Fields & Relationships → every column, its API name, and data type. Custom fields end in __c. 4. To add a field: New → choose type (Text, Picklist, Checkbox, Lookup…) → set label/name → set field-level security → add to layouts → Save. 5. To see actual rows: App Launcher → search Contacts → open the tab → pick a list view — this is the record browser, your "DE data view".

C. Create a report (do this once and you can talk about it forever) 1. App Launcher → search Reports → open the Reports tab. 2. Click New Report → pick a report type (e.g. Contacts & Accounts) → Start Report. 3. Left panel: Outline = columns/groupings; Filters = your WHERE clause (e.g. Created Date = THIS MONTH). 4. Click Save & Run → name it, pick a folder. 5. Dashboard: App Launcher → Dashboards → New Dashboard → + Widget → point it at your report → choose chart type → Save.

D. Open Flow Builder (the skill, not just the tour) 1. Setup → Quick Find Flows → click Flows → New Flow. 2. Pick a type: Screen Flow (has UI), Record-Triggered (fires on create/update — like an entry event), Schedule-Triggered, Platform Event-Triggered, or Autolaunched (callable subflow). In the Marketing Cloud app, campaign flows come in marketing-specific types — Segment-Triggered (most common: publishes a segment into the flow), Automation Event-Triggered (form fills, engagement events), Data Cloud Record-Triggered, Broadcast, On-Demand (API), Activation-Triggered (The 8 marketing flow types; Flow elements for marketing flows — Help). 3. On the canvas, click + between nodes → the element palette opens in its families: Screen/Action (interaction), Decision/Assignment/Loop (logic), Get/Create/Update/Delete Records (data), Wait (time/events). 4. Build the toy everyone builds: Record-Triggered on Contact → Decision (Email not blank?) → Update Records. Click Save (flows are versioned) → Debug (top-right) → inspect the yellow debug log path → then Activate. 5. Debug tip: for record-triggered flows you pick a sample record; check rollback mode if you don't want debug runs to commit real changes.

E. Users, permissions, sandboxes, AppExchange 1. Setup → Quick Find Users → Users → any user → see their Profile (one) and Permission Set Assignments (many). 2. Setup → Quick Find Permission Sets → open one → Manage Assignments → Add Assignment → pick users. Groups: Quick Find Permission Set Groups. 3. Setup → Quick Find Sandboxes (under Environments) → New Sandbox → choose type (Developer/Dev Pro/Partial/Full — how many you get is edition- and license-gated) → after copy completes, log in at test.salesforce.com as yourusername.sandboxname. 4. AppExchange: appexchange.salesforce.com → find a package → Get It Now → choose prod or sandbox → it installs into the org (visible in Setup → Installed Packages).

F. Taste SOQL (read-only awareness) 1. Gear ⚙️ → Developer Console → Query Editor tab (bottom pane). 2. Run: SELECT Id, Name, Email FROM Contact WHERE CreatedDate = LAST_N_DAYS:30 LIMIT 10. 3. Note what's not there: no SELECT *, no JOIN — parent fields come via dots (Account.Name), children via subquery (SELECT Id, (SELECT Email FROM Contacts) FROM Account).

---

🎤 Rapid-fire

1. Q: What's a Salesforce org, in one line? A: One customer's isolated tenant — all data, config, users, and code in a single instance. …and in practice: prod = login.salesforce.com, sandboxes = test.salesforce.com.

2. Q: How do you tell a custom object or field from a standard one? A: Custom API names end in __c (e.g. Loyalty_Tier__c); standard ones don't. …and in practice: check Setup → Object Manager → Fields & Relationships → API Name column.

3. Q: Object vs Data Extension? A: Both are tables, but an object also carries security (FLS/sharing), relationships, page layouts, and can trigger automation. …and in practice: you don't "create a DE per campaign" anymore — you extend Contact/Lead or model in Data Cloud (N03).

4. Q: Profile vs permission set? A: One profile per user = baseline; permission sets = additive grants stacked on top; permission set groups = personas. …and in practice: modern orgs use the Minimum Access profile + permission set groups; the Spring '26 "permissions on profiles" retirement was cancelled, but permission-set-led is still the recommended model.

5. Q: Where does Marketing Cloud Next physically live? A: As the Marketing Cloud app inside the core org — no separate login. …and in practice: App Launcher → "Marketing Cloud" → tabs like Campaigns, Flows, Content, Segments, Analytics.

6. Q: Why should a marketer care about Flow Builder? A: Because in MC Next every campaign is a flow — Flow is the new Journey Builder. …and in practice: the most common campaign flow type is Segment-Triggered; you debug with the Debug button before Activate.

7. Q: Name the sandbox types, smallest to largest. A: Developer, Developer Pro, Partial Copy, Full. …and in practice: Setup → Quick Find "Sandboxes" → New Sandbox; MC Next features work in sandboxes since Winter '26.

8. Q: Two ways SOQL differs from the SQL you wrote in Automation Studio? A: No SELECT * (fields must be listed) and no JOIN (dot-notation to parents, subqueries to children); also read-only — no writing results into a table. …and in practice: Developer Console → Query Editor to try one.

9. Q: Where do reports get their available fields from? A: The report type, which fixes the base object and joined relationships. …and in practice: Reports tab → New Report → the report-type picker is the first screen; pick wrong and your field is simply absent.

10. Q: What's AppExchange in one line? A: Salesforce's app marketplace — managed packages that install features into your org. …and in practice: Get It Now → install in sandbox first → verify in Setup → Installed Packages.

---

⚠️ Gotchas / currency notes

• Don't repeat the "profiles are dying in Spring '26" myth. Salesforce announced that EOL, then officially cancelled the enforcement date — profiles still hold permissions today; the recommendation (not mandate) is permission-set-led (KB: Retirement Cancelled; Salesforce Ben update). Saying it right signals currency; saying it wrong signals stale blog reading.
• Naming is mid-rebrand (again). The product Help still calls it Marketing Cloud Next; the buyable editions are Marketing Cloud Growth/Advanced; since Dreamforce '25 the marketing site brands the suite "Agentforce Marketing (formerly Salesforce Marketing Cloud)" (salesforce.com/marketing). Match your interviewer's vocabulary; all three refer to the same on-core product family (see N01).
• Tabs vanish per profile. If Segments or Analytics is "missing" in the Marketing Cloud app, it's almost always tab visibility not set to Default On for your profile — not a licensing bug (KB).
• Labels lie; API names don't. Admins can relabel anything ("Companies" might be Account). In debug logs, flows, and SOQL you'll always see API names — trust those.
• Flows are versioned and only one version is Active. Every edit of an active flow creates a new version; forgetting to Activate the new version is the classic rookie miss. Debug can commit real DML — tick rollback mode when poking around production-like data.
• Your SQL muscle mostly transfers, but the write path doesn't. There is no "query activity writes into a DE" pattern anywhere on core. Aggregation/metric jobs become Calculated Insights in Data Cloud (N03); row lookups become Flow Get Records; reporting becomes Reports.
• Sandbox counts are edition/license-gated and MC-Next sandbox support is young (Winter '26; Mobile App Messaging excluded at launch, and Data 360 in sandbox requires the license provisioned in production first — Data 360 in a Sandbox). Feature-in-sandbox coverage expands each release — verify before promising a client a test plan.
• Setup moves around between releases. Quick Find labels occasionally shift (e.g. Flow settings pages). The reflex to teach yourself: never browse the Setup tree; always type into Quick Find.

---

Sources

• Marketing Cloud Next — Salesforce Help
• Get Started with Marketing Campaigns and Flows — Salesforce Help
• User is missing tabs for Marketing Cloud Next — Salesforce KB
• Flow Builder Elements for Marketing Flows — Salesforce Help
• The 8 Main Marketing Flow Types — The Agentic Marketer
• Marketing Cloud Growth vs. Advanced Editions — Salesforce Ben
• Marketing Cloud editions — Salesforce
• Agentforce Marketing (formerly Salesforce Marketing Cloud) — Salesforce
• Permissions in Profiles Retirement Cancelled — Salesforce KB
• Salesforce Permissions & Profiles: The Latest Retirement Updates — Salesforce Ben
• Salesforce Roles vs Profiles (and Permission Sets): 2026 Guide — DESelect
• Marketing Cloud Next: Testing with Sandbox (Winter '26) — SFMC Tips #196
• Data 360 in a Sandbox — Salesforce Help

➡️ Next: N03_Data_Cloud_Foundations.md

N02 — Data Cloud Foundations

🎯 Why this matters: Marketing Cloud Next has no Data Extensions and no SQL Query Activity. The "database + query" layer you lived in for a decade is gone — replaced by Data Cloud (rebranded Data 360 in Oct 2025), a customer data platform that ingests everything, resolves it into one unified profile per person, and lets you build audiences on top. If you understand this pipeline, everything else in MC Next (journeys, personalization, agents) is just consumers of it. Get this module wrong and the rest never clicks.

---

🧠 One-screen mental model

The whole engine is one left-to-right pipeline. Memorize the order, not the trivia:

                 ┌──────────────── DATA CLOUD / DATA 360 ────────────────┐
                 │                                                        │
 SOURCES  ──▶  DATA STREAMS  ──▶  DLO  ──(map)──▶  DMO  ──▶  IDENTITY     │
 (CRM, web,     (ingest:          (raw,           (canonical  RESOLUTION  │
  SFTP, API,     batch or          landed          C360 model, (match     │
  ad platforms)  streaming)        copy)           standard/    rules)    │
                 │                                  custom)        │       │
                 │                                                 ▼       │
                 │   CALCULATED INSIGHTS  ◀───────────  UNIFIED INDIVIDUAL │
                 │   (metrics/aggregations:            (one golden profile │
                 │    CLV, RFM, affinity)               per real person)   │
                 │            │                                 │          │
                 │            └──────────▶  SEGMENTS  ◀─────────┘          │
                 │                          (filter rules on               │
                 │                           Unified Individual)           │
                 └────────────────────────────┬───────────────────────────┘
                                               ▼
                                          ACTIVATION
                            (send audience → MC Engagement, Google Ads,
                             Meta, WhatsApp, custom via API…)
                     ⚠️ In MC Next: publish a segment = ready for a campaign
                        (no separate Activation step like classic Data Cloud)

---

🔑 Core in 60 seconds

• Data Streams = ingest. A Data Stream is a configured connection that pulls records from a source (Salesforce CRM, SFTP/CSV, web/mobile SDK, Ingestion API, ad platforms, MuleSoft connectors) into Data Cloud. Each stream can run batch (scheduled bulk) or streaming (real-time incremental). (Data Streams — Salesforce Help)
• DLO = raw landing. Every Data Stream lands data in a Data Lake Object — a typed, schema-based, materialized copy of the source, stored as Parquet in the data lake. This is your "as-ingested" layer; you inspect, transform, and map from here. (Ateko — Data Cloud Model Explained)
• DMO = canonical model. A Data Model Object is a standardized, (typically virtual) view. You map DLO fields → DMO fields so many different sources line up on one shared schema — the Salesforce Customer 360 Data Model (the canonical model). Many DLOs can map into the same DMO. (Model Data in Data 360 — Salesforce Developers)
• Identity Resolution = dedupe into a person. A ruleset of match rules (e.g. Normalized Email, Lead-to-Contact, Device-to-Known) stitches records that refer to the same human into one Unified Individual (the golden profile). More criteria per rule = stricter/more precise; more rules = higher consolidation. (Identity Resolution Match Rules — Salesforce Help)
• Calculated Insights = metrics. Multi-dimensional aggregations computed across the data model — CLV, RFM scores, engagement level, product affinity, purchase counts. Reusable in segments. (Salesforce Ben — What Data Cloud Has)
• Segments = audiences. Filter rules over the model that select matching people. In MC Next, campaign segments must be built on the Unified Individual object in the default data space. (Segmentation in MC Next — Salesforce Help)
• Activation = send it somewhere. Push a segment to a destination: MC Engagement, Google Ads, Meta, WhatsApp, custom endpoints. In MC Next specifically, you don't do a separate activation step — publishing the segment makes it ready for a campaign. Classic Data Cloud still uses explicit Activation Targets. (Segmentation in MC Next — Salesforce Help)
• Data Spaces = partitions. Logical boundaries (by brand / region / business unit) over the same org. Every org has a default data space; MC Next campaign segments live in default. (Ateko — Data Cloud Model Explained)

---

🧩 Mnemonics & memory hooks

• The pipeline word: S-S-D-D-I-U-C-S-A → Sources, Streams, DLO, DMO, Identity, Unified, Calculated insights, Segments, Activation. Chant it once and you own the module. Try: "Seven Store Dogs Dig In Under Cold Snow Always."
• DLO vs DMO — "L is Landed, M is Modeled." DLO = the Landed raw copy. DMO = the Modeled canonical shape. Data flows L → M (never the reverse).
• DLO is a photo, DMO is the passport. The DLO is the raw snapshot exactly as the source sent it. The DMO is the standardized official record everything else trusts.
• Identity Resolution = the merge magnet. Match rules are magnets: more criteria = stronger/pickier magnet (fewer, cleaner merges); more rules = more magnets (more merges). Precision vs consolidation — the classic trade-off.
• Unified Individual = "All Subscribers, but smart." One row per real human, not one row per email address.
• Calculated Insight = the SQL Query Activity's ghost. Anywhere you'd have written a nightly SQL aggregate into a DE, you now define a Calculated Insight once and reuse it.
• Data Space = a tenant fence. Think of it like a Business Unit fence, but for data instead of sends.

---

🔁 Coming from classic Engagement

You already know the concepts — the nouns just changed. This table is the whole mental port:

One-line reframe: You stop building and querying tables, and start mapping sources into one profile and filtering it.

---

🎤 Rapid-fire

1. Q: What's the difference between a DLO and a DMO? A: A DLO is the raw, materialized copy of ingested source data (Parquet in the lake). A DMO is the standardized, usually virtual view onto the canonical Customer 360 Data Model. You map DLO fields → DMO fields; data flows DLO → DMO, never back.

2. Q: Can two different sources feed the same DMO? A: Yes — multiple DLOs (e.g. web signups + POS + CRM contacts) can map to the same target DMO, as long as field data types are compatible. That's the whole point of a canonical model.

3. Q: What produces the Unified Individual? A: Identity Resolution — a published ruleset of match rules runs across the individual-level DMOs and merges records referring to the same person into one Unified Individual profile.

4. Q: I want stricter matching — more match rules or more criteria per rule? A: More criteria within a single rule = stricter (records must satisfy all of them → precise, but risk undermatching). More match rules = higher consolidation (more ways to match). It's a precision-vs-consolidation dial.

5. Q: Where does a Calculated Insight fit, and how is it used in a segment? A: It's a reusable metric/aggregation (CLV, RFM, affinity) computed over the model. To use it in segmentation it must relate to the Segment-On object, with that object's primary key present as a dimension in the insight; then you drag the insight into segment rules.

6. Q: In MC Next, after I build a segment, what's the activation step? A: There basically isn't a separate one. Publish the segment and it's ready for a campaign. (Classic Data Cloud still uses explicit Activation Targets to push audiences to external destinations like ad platforms.)

7. Q: What object must a MC Next campaign segment be built on? A: The Unified Individual object, in the default data space. Not arbitrary DMOs.

8. Q: Batch vs streaming — when does each apply? A: Batch/bulk = scheduled large syncs (e.g. nightly CSV via SFTP or bulk Ingestion API) when real-time isn't needed. Streaming = real-time incremental updates (web/mobile SDK, streaming Ingestion API) for time-sensitive data. A Data Stream is configured for one pattern.

---

⚠️ Gotchas / currency note

• NAME CHANGE (verify before you speak): Salesforce renamed Data Cloud to "Data 360" on Oct 14, 2025, under the "Agentforce 360" umbrella. Docs, URLs, and help articles are mid-migration — you'll see both "Data Cloud" and "Data 360" in the wild, sometimes on the same page. Treat them as the same product. It's had six names (Customer 360 Audiences → Salesforce CDP → Marketing Cloud CDP → Genie → Data Cloud → Data 360), so expect churn. (Salesforce Ben — Renamed to Data 360) · (Data 360 — salesforce.com/data)
• "Activation" means two different things. In classic Data Cloud it's an explicit step (Activation Targets → ad platforms/MC Engagement). In MC Next, publishing a segment is enough — don't go hunting for an activation step in the campaign builder. Know which product the interviewer means. (Segmentation in MC Next)
• Identity Resolution costs credits. Rulesets consume Data 360 credits/consumption; the guidance is one active ruleset per object to limit billing impact. Don't casually spin up many rulesets. (Configure Identity Resolution for MC Next)
• Segment publish cadence ≠ instant by default. MC Next offers Don't Refresh / Standard (12–24h) / Rapid (every 1–4h, uses ~1 week of recent data) / Immediately. "Real-time-ish" behavior depends on choosing Rapid/Immediately, and identity-resolution timing still affects the final population. (Segmentation in MC Next)
• Segment limits are real. Max 50 filters per Include tab and 50 per Exclude tab in MC Next segmentation — design around it. (Segmentation in MC Next)
• "Zero-copy" is a genuinely new muscle. Data 360 can query external warehouses (Snowflake, BigQuery, Databricks) without physically copying the data — there's no classic-Engagement analog. Flag it as evolving; capabilities expand each release. (Data 360 — salesforce.com/data)
• Terminology drifts by release. Match-rule presets, insight authoring (SQL vs no-code builder), and the exact segment UI have shifted across the 2025→2026 releases. When precision matters in an interview, cite the Help doc and note "as of the current release."

---

Summary: Marketing Cloud Next runs on Data Cloud/Data 360 — Sources → Data Streams ingest into raw DLOs, which map onto canonical DMOs; Identity Resolution match rules merge them into one Unified Individual, over which Calculated Insights (metrics) and Segments (audiences) are built and then activated — conceptually replacing the classic Data Extensions + SQL Query Activity model.

➡️ Next: N04_Segmentation_and_Audiences.md

N03 — Segmentation & Audiences

🎯 Why this matters: In classic Engagement you were the segmentation engine — you wrote SQL Query Activities against Data Extensions, deduped by hand, and dropped results into a "sendable" DE. In Marketing Cloud Next the audience lives in Data Cloud (Data 360), and segments are built declaratively on the Unified Individual profile. Your SQL brain still helps you reason about the data, but the marketer now drags attributes onto a canvas. If you can map "SELECT … FROM … WHERE … dedup" onto "Segment On → Include/Exclude → Publish," you've made the pivot.

---

🧠 One-screen mental model

The audience flows left → right: raw sources are unified into one profile, you slice that profile into a segment, and the segment is published so Marketing Cloud can send to it.

  DATA CLOUD (Data 360)                                 MARKETING CLOUD NEXT
  ─────────────────────                                 (Growth / Advanced)
                                                        ┌────────────────────┐
  DMOs ─┐                                                │  Flow / Campaign   │
  (Unified Individual,   ┌───────────────────────────┐  │  ─ email send      │
   Order, Engagement) ──▶│      SEGMENT BUILDER       │  │  ─ personalization │
                         │  Segment On: Unified Indiv │  └──────────┬─────────┘
  Calculated Insights ──▶│  ┌───────────┬───────────┐│             ▲
  (LTV, open-rate)       │  │ INCLUDE   │ EXCLUDE    ││   PUBLISH   │
                         │  │ container │ container  ││  ══════════▶│  (segment is
  Related objects ──────▶│  │  AND/OR   │  (batch    ││             │   available;
  (Orders, Cases)        │  │  nested   │   only)    ││  no separate│   no synced-DE
                         │  └───────────┴───────────┘│  activation │   step in MC Next)
                         │  Standard vs Rapid publish │  needed     │
                         │  Real-time (streaming)     │             │
                         └───────────────────────────┘             │
                                     │                              │
                                     └── segment membership ────────┘
                                         (who is in, refreshed on schedule)

  CLASSIC CONTRAST (Data Cloud ▶ MC ENGAGEMENT):
     Segment ──▶ Activation Target ──▶ Activation ──▶ synced Data Extension ──▶ send
     (MC Next collapses those middle steps — you just publish the segment.)

Wireframe.

---

🔑 Core in 60 seconds

• Segments live in Data Cloud (Data 360), not in Marketing Cloud. In MC Next you don't build "sendable Data Extensions" — you build segments against unified data and point campaigns/flows at them. (Salesforce Help — Publish a Segment)
• Segment On = the DMO you count. For marketing sends this is almost always the Unified Individual DMO produced by Identity Resolution (the ruleset that de-dupes people across sources). Bad identity resolution → duplicate sends. (SFMC Tips #92 — Basics of Segmentation)
• You slice with three ingredient types: direct attributes (1:1, e.g. country on the profile), related attributes (1:many, e.g. order amount, engagement events), and Calculated Insights (pre-aggregated metrics like Lifetime Value or 30-day open count). A Calculated Insight must expose the primary key of the Segment On DMO as a dimension to be usable in a segment. (David Palencia — Data Cloud Segmentation)
• Include / Exclude + containers. The canvas has an INCLUDE and an EXCLUDE tab. Attributes in the same container are ANDed on the same data row (e.g. an order that is both "> $100" and "in the last 30 days"); attributes in separate containers are evaluated independently. Nested segments let you reuse an existing segment as a building block. (David Palencia — Data Cloud Segmentation)
• Publish schedules decide freshness: Standard Publish (every 12–24h, up to ~2 years of engagement data) vs Rapid Publish (every 1–4h, ~7-day window, and can only send to Marketing Cloud). Real-time segments compute on demand in milliseconds but can't use exclusion criteria, nested batch segments, manual publish, or counts. (Salesforce Help — Create a Real-Time Segment, Rapid Segment Publish GA)
• Segment membership = the resolved set of Unified Individuals matching your rules, refreshed each publish. That set is what a flow or campaign sends to.
• Activation is where classic and MC Next diverge (see below). In the classic Data Cloud → MC Engagement pattern you create an Activation Target + Activation and the segment lands as a synchronized Data Extension. In MC Next (Growth/Advanced, "on core") the segment is used directly after publish — no separate activation-to-synced-DE step. (SFMC Tips #92)

---

🧩 Mnemonics & memory hooks

• "S-O-I-E-P" = the five decisions for any segment: Segment On (which DMO) → Objects/attributes to bring in → Include → Exclude → Publish schedule.
• "D-R-C" ingredients = Direct attributes, Related attributes, Calculated Insights. (If you need math across many rows — LTV, open count — reach for C.)
• Containers = a JOINed WHERE. Same container = same row = AND (like conditions on one joined record). Different containers = different subqueries. This is the mental bridge from your SQL joins.
• Real-time = "fast but shallow." Milliseconds, but no Exclude, no nesting, no counts, no manual publish. If your ask has the word "exclude" in it, it's a batch segment.
• Rapid = "hot but small, MC-only." 1–4h refresh, 7-day data window, and it can only target Marketing Cloud.
• "Publish, don't export." In MC Next you publish a segment; you no longer export/query into a sendable DE. Kill the reflex to build a target DE.

---

🔁 Coming from classic Engagement

The classic muscle memory: to email "high-value customers who opened in the last 30 days," you wrote a SQL Query Activity that joined a customer DE to the _Open data view, filtered by date and spend, deduped with ROW_NUMBER(), and wrote the survivors into a sendable target Data Extension. (RizeX Labs — SFMC SQL Guide, Salesforce Help — Opens in Last 30 Days)

Classic SQL (Query Activity → target DE):

-- Runs in a SQL Query Activity; results overwrite a sendable target DE.
SELECT
    s.SubscriberKey,
    s.EmailAddress
FROM (
    SELECT
        c.SubscriberKey,
        c.EmailAddress,
        ROW_NUMBER() OVER (
            PARTITION BY c.SubscriberKey        -- dedup: one row per person
            ORDER BY o.EventDate DESC
        ) AS rn
    FROM   Customers        AS c                -- your customer Data Extension
    JOIN   _Open            AS o                -- system data view of opens
           ON o.SubscriberKey = c.SubscriberKey
    WHERE  c.LifetimeValue   > 500              -- "high value"
      AND  o.EventDate >= DATEADD(day, -30, GETDATE())   -- opened in 30 days
) AS s
WHERE s.rn = 1;                                 -- keep only the deduped row

Line-by-line, in classic terms: - SELECT s.SubscriberKey, s.EmailAddress — the sendable columns the target DE needs. - The inner ROW_NUMBER() OVER (PARTITION BY … ) — you are doing dedup by hand, because a person may have many open rows. - FROM Customers JOIN _Open — you are stitching a profile DE to an engagement data view. - WHERE LifetimeValue > 500 AND EventDate >= DATEADD(day,-30,GETDATE()) — the actual business rule. - WHERE s.rn = 1 — collapse to one row per subscriber so the send doesn't double-mail.

Same segment, built declaratively in Data Cloud (no SQL):

1. New Segment → Segment On = Unified Individual. (Identity resolution already deduped people across sources — so the hand-written ROW_NUMBER() dedup disappears.)
2. On the INCLUDE tab, drag in a Calculated Insight Lifetime Value → set > 500. (The aggregation that would've been SQL SUM/join is pre-computed in the CI.)
3. In the same container, add the related engagement attribute Email Engagement → Event = Open with Event Date in the last 30 days → the AND-on-same-row container gives you "opened, within 30 days."
4. (Optional) EXCLUDE tab → Unsubscribed = true — a one-click exclusion instead of an anti-join.
5. Choose Standard or Rapid Publish, then Publish. Membership refreshes on that schedule; no target DE to design.
6. In Marketing Cloud Next, point a flow/campaign at the published segment and send. (No Activation Target / synced DE step — that's the classic Data Cloud → MC Engagement path.)

What changed for you:

---

🎤 Rapid-fire

Q1. In MC Next, what object do you build a marketing segment on, and why does it matter? A. The Unified Individual DMO. It's the identity-resolved profile, so counts and sends are de-duplicated across sources; weak identity resolution causes duplicate emails.

Q2. What are the three kinds of "ingredients" you can drag onto the segment canvas? A. Direct attributes (1:1 on the profile), related attributes (1:many, e.g. orders/engagement), and Calculated Insights (pre-aggregated metrics like LTV or open counts).

Q3. Two conditions in the same container vs separate containers — what's the difference? A. Same container = ANDed on the same data row (e.g. one order that is both big and recent). Separate containers = evaluated independently across the profile's related data.

Q4. When can't you use a real-time segment? A. When you need exclusion criteria, nested batch segments, segment counts, or manual publish — real-time supports none of those. Use a batch segment instead.

Q5. Standard vs Rapid Publish — one-line each. A. Standard: every 12–24h, up to ~2 years of engagement data. Rapid: every 1–4h, ~7-day window, Marketing-Cloud-only target.

Q6. Your classic query did ROW_NUMBER() … PARTITION BY SubscriberKey to dedup. Where does that go in Data Cloud? A. It largely goes away — Identity Resolution collapses duplicates into the Unified Individual before you ever segment.

Q7. How does "activation" differ between classic Data Cloud → MC Engagement and MC Next? A. Classic: create an Activation Target + Activation; the segment lands as a synchronized Data Extension you send from. MC Next (on core): publish the segment and use it directly in a flow/campaign — no separate activation-to-DE step. (Verify per release — see currency note.)

Q8. A marketer says "email people the moment they enter the segment." What MC Next feature is that? A. An Activation-Triggered Flow — a flow that fires when a segment's publish/activation completes, so members are messaged at that moment (with a realistic lag of minutes). (SFMC Tips #243)

---

⚠️ Gotchas / currency note

• "Activation" is the most confusing overlap. Salesforce uses Activation Target / Activation / synced Data Extension in the classic Data Cloud → Marketing Cloud Engagement integration. In Marketing Cloud Next (Growth/Advanced, built "on core"), community write-ups state activation is not required — you publish a segment and use it directly. But newer features like Activation-Triggered Flows still surface the word "activation." Treat this as evolving and confirm against the release you're on. (SFMC Tips #92, SFMC Tips #243)
• Product naming is in flux. "Data Cloud" is being rebranded "Data 360", and "Marketing Cloud Next" / "Marketing Cloud on Core" / "Growth & Advanced" are used loosely for the same on-platform stack. Don't over-index on a single label.
• Publish cadence ≠ real time. Even a manually published batch segment can take tens of minutes before members are actually messaged; Rapid Publish is 1–4h, not instant. Plan send timing accordingly. (SFMC Tips #243)
• Real-time limits bite silently. If your segment quietly won't let you add an Exclude or a nested segment, check whether it's a real-time segment — those disallow exclusion, nesting, counts, and manual publish. (Salesforce Help — Create a Real-Time Segment)
• Calculated Insight must carry the right key. A CI is only usable in a segment if it exposes the Segment On DMO's primary key as a dimension — otherwise it won't appear as a filterable attribute. (David Palencia — Data Cloud Segmentation)
• Rapid Publish is Marketing-Cloud-only. Don't design a Rapid segment expecting to activate it to ad platforms or other targets. (Rapid Segment Publish GA)
• Container logic trips SQL people. "Same container = AND on the same row" is not the same as ANDing two independent filters. Two related-object conditions in one container both apply to one related record (e.g. one order); split them into two containers and you get "has some big order AND has some recent order" — a different, larger audience.

---

➡️ Next: N05_Content_and_Email.md

N04 — Content & Email in Marketing Cloud Next

🎯 Why this matters: In classic Engagement, you were AMPscript + Content Builder + Data Extensions. In Marketing Cloud Next (Growth/Advanced), content creation is rebuilt on Salesforce CMS + Data Cloud, personalized with Handlebars merge fields against the Unified Individual, made dynamic with Personalization Points, and drafted by Einstein generative AI. AMPscript did arrive — but only a limited, display-only subset (Summer '26). If you walk in expecting classic AMPscript to be your first tool, you'll build the wrong way. This is the module that resets that instinct.

---

🧠 One-screen mental model

   BRAND (colors, fonts, tone)      DATA CLOUD
        │                          Unified Individual ──┐
        ▼                            + related DMOs     │
 ┌──────────────────────┐         (exposed via a        │
 │  CONTENT BUILDER      │          DATA GRAPH) ─────────┤
 │  (drag-drop, on CMS)  │                               │
 │  Email · LP · Form ·  │◀── merge fields {{...}} ──────┘
 │  SMS · WhatsApp       │        (Handlebars, native)
 │                       │
 │  + Components         │◀── Personalization Points ── Variations/
 │    (Repeater, Button, │      (conditional/dynamic     Decisions
 │     Heading, Image…)  │       content, AND/OR)        + Default
 │                       │
 │  + Einstein (draft    │◀── generative copy & images
 │    copy/subject/image)│
 │                       │
 │  + AMPscript (LTD,    │◀── display-only subset,
 │    Summer '26) &      │      41 funcs (~30%)
 │    Handlebars in code │
 └──────────┬────────────┘
            ▼
      SEND via a FLOW / Journey  ──► resolves merge fields
                                     per Unified Individual → deliver

---

🔑 Core in 60 seconds

• Where content lives: Content Builder in Marketing Cloud Next is a drag-and-drop builder built on Salesforce CMS, not classic Content Builder. One hub creates email, landing pages, forms, SMS, and WhatsApp. (Mavlers, Manras)
• Building blocks are Components, grouped into Basics / Layout / Media — e.g. Button, Heading (auto-applies brand style), Image, and the Repeater (binds to a data source and renders a list from one layout — think looped rows without writing a loop). (Mavlers, SFMC Tips #134)
• Brand kit: A brand selection applies predefined colors, fonts, button styles, brand identity, and tone to content automatically; content blocks can be saved and reused for consistency. Summer '26 added custom web fonts with fallbacks. (Mavlers, SFMC Tips #285)
• Personalization = merge fields against Data Cloud. Merge fields reference the Unified Individual and any related DMO (cross-object merge fields), surfaced through a Data Graph. A Data Graph is effectively required to personalize. Native syntax is Handlebars {{ ... }}, not %%...%%. (Salesforce Ben, Salesforce Developers — Handlebars for MCN)
• Dynamic/conditional content = Personalization Points. A Personalization Point is a reusable container of Variations/Decisions (rules like Favorite Genre = Rock) with AND/OR composite logic, priority ordering, and a Default fallback. Limits: 25 points/email, 15 variations/point. (SFMC Tips #174)
• Einstein generative AI is built in. Einstein Co-Create drafts full assets (emails, landing pages) from a natural-language prompt; you can generate/adjust subject lines, copy, tone, length, and images, governed by brand personalities (2 default + up to 10 custom). (email.uplers, ABSYZ)
• AMPscript: it exists, but limited. As of Summer '26, MC Next supports a display-only subset — 41 functions (~30%) — usable in both code view and the visual editor, alongside Handlebars. No Data Extension ops, CloudPages, HTTP, API calls, or encryption. It's a personalization display tool, not a data-manipulation engine. (SFMC Tips #280, dev.to — AMPscript Ninja)

---

🧩 Mnemonics & memory hooks

• "C-P-A" — the personalization ladder, in order of reach for: Conditional? → Personalization Point (Variations/Decisions). Plain field? → merge field {{...}} (Handlebars). AMPscript? → last resort, only if a display function needs it and it's in the 41. Reach left-to-right; AMPscript is the far end, not the default.

• "UID is the root of all merge." Every merge field hangs off the Unified InDividual via a Data Graph. No graph → no personalization.

• "41 / 30 / 0" — the AMPscript reality card: 41 functions, ~30% coverage, 0 data-writing power (no DE writes, no HTTP, no API, no encryption).

• "Curly, not percent." Syntax moved %%Firstname%% → {{...}}. If you type percent tags, you're in the old platform.

• "Point = Rules, not Content." A Personalization Point makes the targeting rules reusable — the content itself isn't reused. (Classic Dynamic Content Blocks bundled both; here they split.)

• "Repeater = your for loop without code." Where classic dynamic tables meant AMPscript loops over rows, the Repeater component binds a data source and renders the list.

---

🔁 Coming from classic Engagement

The honest summary for an AMPscript expert: Your AMPscript knowledge still helps you reason about personalization and formatting, and Summer '26 lets you drop familiar functions like Lookup(), Concat(), FormatDate(), Iif(), ContentBlockByName() right into content. But the platform-shaping AMPscript you relied on — writing to DEs, HTTPGet, API calls, RaiseError, encryption — does not exist here. That logic now lives in Flow and Data Cloud, and most day-to-day personalization is declarative merge fields + Personalization Points. Treat AMPscript as a targeted display helper, not the backbone.

---

🎤 Rapid-fire

1. Q: Does AMPscript work in Marketing Cloud Growth/Advanced? A: Yes, but limited. As of Summer '26 a subset of 41 functions (~30%) is supported in both the code and visual editors — display/personalization only. No Data Extension ops, CloudPages, HTTP, API, or encryption. (SFMC Tips #280)

2. Q: If not AMPscript, what's the default personalization tool? A: Handlebars merge fields {{...}} referencing the Unified Individual (and related DMOs) via a Data Graph. (Salesforce Developers)

3. Q: How do I pull a field from a related object (like classic Lookup)? A: Cross-object merge fields — any attribute on any object related to the Unified Individual, no code, provided the object/field is in your Data Graph. For repeating related rows, use the Repeater component. (Salesforce Ben)

4. Q: What replaces Dynamic Content Blocks / AMPscript IF conditional content? A: Personalization Points — reusable containers of Variations/Decisions with AND/OR logic, priority, and a Default fallback (25/email, 15 variations each). (SFMC Tips #174)

5. Q: Can Einstein write my email copy and images? A: Yes — Einstein Co-Create drafts emails/landing pages from a prompt; generate/adjust subject lines, copy (tone/length), and images, controlled by brand personalities (2 + up to 10 custom). (email.uplers, ABSYZ)

6. Q: What content types can the builder produce? A: Email, landing pages, forms, SMS, and WhatsApp from one CMS-based builder. (Mavlers)

7. Q: Do I still need Data Extensions to personalize? A: No. Personalization sources from Data Cloud DMOs through a Data Graph rooted on the Unified Individual — the graph is effectively a prerequisite for personalization. (The Spot)

8. Q: My merge field syntax %%Firstname%% isn't working — why? A: Wrong platform's syntax. MC Next uses Handlebars {{...}}; since Spring '26 fields added in the drag-drop editor emit Handlebars. (Salesforce Developers)

---

⚠️ Gotchas / currency note

• AMPscript support is brand-new and evolving. It shipped in Summer '26 (this is a 2026 capability — anything written before ~2025 saying "no AMPscript in Growth/Advanced" is now outdated). The 41-function / ~30% / display-only scope will likely grow in later releases — re-verify the current function list before scoping a build. (SFMC Tips #280, dev.to)
• AMPscript here can't do data operations. No DE reads/writes, no HTTPGet, no API/CloudPages, no encryption. If a classic pattern relied on those, redesign around Flow + Data Cloud, not scripting.
• Handlebars is the true native language. Don't over-index on AMPscript because it's familiar — for most personalization, Handlebars merge fields + built-in helpers are the intended, better-supported path. (The Agentic Marketer)
• No Data Graph = no personalization. The fields available for merge fields, dynamic content, and Flow decision splits are exactly those in your Data Graph. Model the graph first. (The Spot)
• Personalization Points reuse rules, not content. Don't assume classic Dynamic Content Block behavior; the content still lives per-placement. Enforce a naming convention early. (SFMC Tips #174)
• Growth vs Advanced differences exist (volume, channels, features). Feature availability and limits shift per release — confirm against current Salesforce Summer '26 release notes for your edition before committing to a design.

---

➡️ Next: N06_Flows_and_Journeys.md

N05 — Flows & Journeys

🎯 Why this matters: In classic Marketing Cloud Engagement (MCE) you orchestrated customers in Journey Builder — a standalone canvas with its own entry sources, splits, and waits. In Marketing Cloud Growth / Advanced ("Marketing Cloud Next," MC on Core), that orchestration is done with Salesforce Flow (Flow Builder) running on the Core platform, entered from Data Cloud segments and other Core triggers. Your Journey Builder muscle memory transfers, but the tool, entry model, and pricing dynamics change. This module maps the old mental model onto the new one so you don't freeze in an interview when they say "there's no Journey Builder here."

---

🧠 One-screen mental model

A Growth "journey" is a Marketing Flow in Flow Builder: a Segment-Triggered Start injects members of a Data Cloud segment, then you chain Wait, Decision, and Send Email/SMS Message elements — same shapes as a Journey Builder canvas, different engine.

   DATA CLOUD                         SALESFORCE FLOW  (Flow Builder / "Marketing Flow")
 ┌───────────┐        entry          ┌──────────────────────────────────────────────────────┐
 │  Segment  │ ───────────────────►  │ ▶ Start  (Segment-Triggered)                          │
 │ (Dynamic) │  members injected     │      │   recurring? re-entry: always/never/after done │
 └───────────┘  on schedule/publish  │      ▼                                                 │
                                     │  ✉  Send Email Message  (from Salesforce CMS)          │
                                     │      │                                                 │
                                     │  ⏳ Wait for Amount of Time (mins→months)              │
                                     │      │                                                 │
                                     │  ◇  Decision  ── meets criteria? ──┐                    │
                                     │      │ (No path)          (Yes path)│                    │
                                     │      ▼                              ▼                    │
                                     │  📱 Send SMS Message        ✉ Send follow-up Email     │
                                     │      │                              │                    │
                                     │      ▼                              ▼                    │
                                     │  ⏹ End                          🔧 Update Records (Core) │
                                     └──────────────────────────────────────────────────────┘

---

🔑 Core in 60 seconds

• There is no separate Journey Builder in Marketing Cloud Growth/Advanced. Orchestration is built in Flow Builder (Salesforce Flow) on the Core platform. Marketers use a Campaign as the wrapper, and the underlying automation is a Marketing Flow (aka "Campaign Flow"). (Salesforce Ben)
• Primary entry = a Data Cloud segment. The Segment-Triggered Flow is the most common type: a scheduled flow where members of the related Data Cloud segment are injected into the flow. (The Spot, Salesforce Ben)
• Send actions have explicit element names: Send Email Message (sends an email using Salesforce CMS content to an audience segment) and Send SMS Message. Both are marketing-only Flow elements. (Salesforce Help — Send Email Message, Send SMS)
• Waits are real Flow elements: Wait for Amount of Time (minutes → months), Wait Until Date, and Wait Until Event (proceed on behavior like opens/clicks). (The Spot, MarketingCloudTips)
• Branching = Decision element (plus Path Experiment in Advanced for A/B/n testing, and Einstein Decision for AI-scored routing). (MarketingCloudTips)
• You also get real Core actions: because it's Flow, you can Update Records, call sub-flows, and touch CRM data mid-journey — something classic JB could not do natively. (Salesforce Help — Flow Builder Elements for Marketing Flows)
• Segments run on a schedule, not truly real-time, because Data Cloud segmentation is consumption/credit-based — refresh (republish) the segment right before a send so newly qualified individuals are included. (Salesforce Ben, The Spot)
• Classic Journey Builder is not going away for MCE customers. Salesforce's stated direction is Flow and Journey Builder working side by side, with Journey Builder being brought "on Core" over time — not a forced migration. (Salesforce Ben)

---

🧩 Mnemonics & memory hooks

• "S-E-W-D" = the backbone of a Growth journey: Segment start → Email send → Wait → Decision. Say it like "sewed a journey together."
• "Segment IN, Flow RUNS, CMS OUT." Entry is a Data Cloud segment, logic is Flow, content comes from Salesforce CMS (not classic Content Builder).
• Three Waits = "Time, Date, Event" — Wait for Amount of Time, Wait Until Date, Wait Until Event. (Classic JB had exactly this trio too: duration wait, date wait, wait-by-attribute/behavior.)
• "Decision, not Split." The word "split" is MCE vocabulary; in Flow the element is a Decision (Advanced adds Path Experiment = the random/optimizer split).
• "Scheduled, not streaming." Because Data Cloud burns credits per segment run, Growth journeys batch on a schedule — the opposite of JB's always-listening API/event entry feel.

---

🔁 Coming from classic Engagement

Key mindset shifts: 1. It's Flow, so it's governed by Flow. You inherit Core concepts: elements, resources/variables, sub-flows, and platform limits — not the JB-specific canvas rules. 2. Data Cloud is your segmentation + Automation Studio replacement. Heavy SQL/filtering logic moves to Data Cloud segments, calculated insights, and data transforms rather than Automation Studio SQL activities. (Ateko) 3. Advanced ≠ Growth. Path Experiments (A/B/n) and some richer decisioning are Advanced-edition features. (The Agentic Marketer)

---

🎤 Rapid-fire

1. Q: In Marketing Cloud Growth, what tool builds journeys? A: Salesforce Flow Builder on the Core platform. There is no separate Journey Builder app; orchestration is a Marketing/Campaign Flow wrapped by a Campaign.

2. Q: What's the most common flow type and how does it start? A: The Segment-Triggered Flow — a scheduled flow that injects members of a related Data Cloud segment at the Start element.

3. Q: Name the three wait elements. A: Wait for Amount of Time (minutes to months), Wait Until Date, and Wait Until Event (proceed on behavior like opens/clicks).

4. Q: How do you branch a journey, and what's the classic equivalent? A: With a Decision element (≈ JB Decision Split). For random/optimized testing use Path Experiment (Advanced only, ≈ Random Split / Path Optimizer); for AI-scored routing use Einstein Decision.

5. Q: What are the send actions called? A: Send Email Message (uses Salesforce CMS content to an audience segment) and Send SMS Message — both marketing-only Flow elements.

6. Q: Can a Growth journey update CRM records? Could classic JB? A: Yes — because it's Flow, you can use Update Records and other Core actions mid-journey. Classic JB had no native record-update; you'd need an Update Contact activity or external automation.

7. Q: Why isn't a segment-triggered journey truly real-time? A: Data Cloud segmentation is consumption/credit-based, so segments run on a schedule. Best practice: republish the segment immediately before the send to capture newly qualified individuals.

8. Q: Is classic Journey Builder being killed off? A: No. Salesforce's stated position is Flow and Journey Builder used side by side, with Journey Builder moving "on Core" over time — no forced migration for existing MCE customers.

---

⚠️ Gotchas / currency note

• "Journey" is loose terminology. In Growth/Advanced there is no object literally called a "Journey" — you build Marketing Flows / Campaign Flows. Interviewers may still say "journey"; know they mean a Flow.
• Segment-triggered = scheduled, not streaming. Don't promise sub-second real-time entry from a segment; that's what Record-Triggered / On-Demand / event-triggered flows are for. Match the flow type to the latency requirement.
• Wait "resume at time of day" can silently extend the wait. A 3-day wait set to resume at 3:00 PM can effectively become ~4 days. Watch this in QA. (MarketingCloudTips)
• Decision on unified attributes needs a Data Graph. If the required Data Graph linking to the Unified Individual isn't configured in advance, those attributes won't be selectable in the Decision element. (MarketingCloudTips)
• Edition-gated features. Path Experiments are Advanced-only. Verify what a given org's edition (Growth vs Advanced) actually unlocks before designing. (The Agentic Marketer)
• 🔄 This area is evolving fast — verify against the current release. Element inventory and behavior change most releases. Example: a Determine CRM Record for Individual branching element (routes a unified individual to Contact/Lead/Prospect) was reported added in the Winter '26 release. Always confirm against the live release notes and Salesforce Help before quoting specifics in an interview. (The Agentic Marketer, Salesforce Help)

---

➡️ Next: N07_Channels_SMS_WhatsApp.md

N07 — Channels: Email, SMS & WhatsApp in MC Next

🎯 Why this matters: In classic Engagement you had Email Studio, MobileConnect, and GroupConnect — three separate studios, three separate contact models. Marketing Cloud Next collapses all sending into one stack: every channel is configured in one Settings area, every send goes out through a Flow, and every message passes through one consent gate (Communication Subscription Consent in Data 360) before it leaves. If there's no opt-in record, the message doesn't go — the exact opposite of classic email's "everyone's sendable until they unsubscribe." Interviewers love this module because it's where classic instincts fail loudest.

---

🧠 One-screen mental model

Every send — email, SMS, or WhatsApp — walks the same corridor:

                        A SEND IN MC NEXT (any channel)

 ┌───────────────┐      ┌───────────────────────────┐
 │ FLOW /        │      │  CONSENT GATE (Data 360)  │
 │ CAMPAIGN      │─────▶│  Communication Subscription│
 │ "Send Email / │      │   + Engagement Channel     │
 │  SMS / WA"    │      │  Comm Subscription CONSENT │
 └───────────────┘      │   (per contact point)      │
                        │  ⚠️ NO RECORD = OPT-OUT    │
                        └─────────┬─────────────────┘
                                  ▼  opted-in only
        ┌────────────── CHANNEL INFRASTRUCTURE ────────────────┐
        │ EMAIL     Authenticated Domain: 3 DKIM out,          │
        │           5 CNAMEs in (reply mail), SPF handled by   │
        │           Salesforce, DMARC recommended              │
        │ SMS       Code: Brand → Campaign → Code (+ messaging │
        │           credits; long vs short code)               │
        │ WHATSAPP  Paid add-on + Meta business account +      │
        │           Meta-approved templates                    │
        │ (RCS      newest channel — Summer '26, 6 countries)  │
        └──────────────────────┬────────────────────────────────┘
                               ▼
                    RECIPIENT — a contact point
                    on the Unified Individual
                               │  replies (SMS / WhatsApp)
                               ▼
        UNIFIED MESSAGING (Advanced edition): one number, two-way —
        marketing stays in Flow; service replies route via
        Omni-Channel to a human agent or an Agentforce bot

---

🔑 Core in 60 seconds

• Email needs an Authenticated Domain — no exceptions. MC Next Growth/Advanced can't send from arbitrary addresses: the From address must live on a DKIM-authenticated domain you set up under Settings → Channels → Email → Authenticated Domains. Only self-hosted DNS is supported (no delegated-subdomain option like classic SAP). (Authenticating MC Next Emails — Salesforce Help)
• The DNS shopping list: 3 DKIM records (outbound signing: s1/s2/s3-e360-…._domainkey), 5 inbound CNAMEs for reply mail management (anonymous, bounce, fbl, reply, leave), and an optional-but-recommended DMARC TXT. SPF is managed by Salesforce — you add nothing for it. (Domain Setup and DNS Tips — Salesforce Help, SFMC Tips #140)
• SMS is in both Growth and Advanced; two-way is Advanced-only. One-way marketing SMS ships with both editions (paid via messaging credits). Unified Conversations for SMS — two-way dialogue on a single number, routed between Flow (marketing) and Omni-Channel (service agents/bots) — is Advanced edition, and the service side needs a Digital Engagement license. (What's Unified Messaging — Salesforce Help, Salesforce Ben — Growth vs Advanced)
• SMS provisioning is a 3-step regulatory ladder: Request a Brand (~5 business days) → Request a Campaign (~10 days, needs sample messages) → Request a Code (~2 days). Long code: self-service, ~4–6 weeks total, no setup fee, slower throughput. Short code: partner-managed, 12+ weeks, roughly $8k–15k, high volume, country-locked. (The Spot — SMS Provisioning on Core)
• WhatsApp is GA as a paid add-on for both Growth and Advanced (purchased like SMS). Prerequisites: a Meta Business Manager account, a verified business, a phone number, and Meta-approved message templates. Advanced adds Unified Conversations for WhatsApp (promo message → live two-way with a service agent). (Salesforce blog — Expanded availability, Set Up WhatsApp in MC Next — Salesforce Help)
• Consent is subscription-based, per contact point, stored in Data 360. Four DMOs do the work: Engagement Channel Type → Communication Subscription → Communication Subscription Channel Type → Communication Subscription Consent. Status is per email address / phone number / WhatsApp number, per subscription. If no consent record exists, MC Next treats the person as OPT-OUT and skips them. (Consent Concepts — Salesforce Help, The Agentic Marketer — Consent Management)
• Deliverability on the new stack: shared IPs by default; Spring '26 made dynamic dedicated IPs GA — senders around 5M emails/month are auto-migrated, with automatic IP warming (0–35 days) and up to 32 IPs (reclaimed if volume drops). Salesforce recommends a separate subdomain from your MCE sending domain. (SFMC Tips #218 — Spring '26)
• Pricing awareness (rough, verify current rate card): Growth from ~$1,500/mo and Advanced from ~$3,250/mo, org-based; public figures have quoted 180k email sends/org/year on Growth and SMS around $10 per 1,000 sends, with messaging-credit multipliers varying by code type and country. Numbers move — quote the mechanism, not stale figures. (Concret.io — Editions, Salesforce Ben — MC Pricing)

---

🧩 Mnemonics & memory hooks

• "3 OUT, 5 IN, 1 MAYBE" — the email DNS card: 3 DKIM records outbound, 5 CNAMEs inbound (reply mail), 1 optional DMARC. SPF? Zero — Salesforce owns it.
• The 5 inbound CNAMEs: "A Big Fish Rarely Leaves" — Anonymous, Bounce, Fbl, Reply, Leave.
• SMS ladder: "Brand, Campaign, Code — 5, 10, 2." Three requests, and their approval times in business days. Brand proves who you are, Campaign proves what you'll send, Code is the number itself.
• Consent chain: "Every Channel Sells Subscriptions, Subscriptions Collect Consent." Engagement Channel Type → Comm Subscription → Subscription Channel Type → Consent. Channel exists → subscription rides on it → the pairing collects consent per contact point.
• "Silence means STOP." No consent record = opt-out = no send. (Classic email assumed the opposite: silence meant sendable. This flip is the #1 migration trap.)
• "Growth broadcasts, Advanced converses." One-way messaging in both editions; two-way (Unified Conversations SMS/WhatsApp) only in Advanced.
• "One corridor, three doors." Flow → consent gate → channel infra. The corridor (Flow + consent) is identical for every channel; only the last door (domain / code / Meta account) differs.

---

🔁 Coming from classic Engagement

One-line reframe: Three studios became one Settings page; three contact models became one consent gate.

---

🛠️ In practice (what you would actually click)

A. Authenticate an email sending domain (mandatory before any email send)

1. Open the Marketing Cloud Next app (App Launcher → Marketing Cloud), then go to Settings → Channels → Email and click Go to Authenticated Domains. (Label churns slightly by release: you may see Channel → Email.)
2. In All Authenticated Domains, click + Add Domain → Continue.
3. Enter your sending subdomain (e.g. mail.yourbrand.com — not the root, and not the subdomain MCE already uses) → Submit.
4. Under Create an email address for this domain, type the local part (before the @) for your default From address → Create New.
5. Copy the generated DNS records to your IT/DNS team: 3 DKIM records + 5 CNAMEs (anonymous, bounce, fbl, reply, leave) + the recommended DMARC TXT. ⚠️ Many DNS consoles auto-append the parent domain — strip the duplicated suffix or you'll register bounce.mail.brand.com.brand.com.
6. Once records are placed, tick the confirmation box → Activate My Domain → enter a notification email → Finish. Propagation is quoted at up to 48 h (often ~1 h).
7. Return to Authenticated Domains and confirm status = Active. ⚠️ An authenticated domain cannot be deleted afterwards — name it carefully.

B. Provision SMS

1. Follow the official Quick Starts: SMS path: in the Marketing Cloud app, Settings → Channels → SMS (help: Set Up SMS Messages in Marketing Cloud Next). Exact node naming is fluid — search Setup for "Messaging" if you don't see it.
2. Request a Brand — legal entity details; ~5 business days to verify.
3. Request a Campaign — use case + sample SMS messages; ~10 business days.
4. Request a Code — pick long code (self-serve, free, slower) or engage your AE/partner for a short code (12+ weeks, ~$8k–15k); ~2 business days for the long-code grant.
5. Only after the code is provisioned, import existing SMS consent records (CSV/flow) so opt-ins attach to your unified individuals.
6. Optional but smart: create a branded link-shortening domain for SMS URLs, and confirm compliance keywords (STOP/HELP-type handling) for your market.
7. (Advanced only) To make the number conversational, set up the Unified Messaging SMS channel and routing: marketing messages stay in Flow; service replies route through Omni-Channel to agents or an Agentforce bot (needs Digital Engagement).

C. Connect WhatsApp (paid add-on, Growth & Advanced)

1. Buy the WhatsApp add-on via your AE (licensed like SMS, consumes messaging credits).
2. Prereqs outside Salesforce: a Meta Business Manager account (business.facebook.com), business verification, and a phone number not already bound to another WhatsApp account.
3. In the Marketing Cloud app: Settings → Channels → WhatsApp and walk the guided connect (Meta embedded sign-up linking your WhatsApp Business Account). (Help: Set Up WhatsApp in Marketing Cloud Next — screen names shift by release; the Meta prerequisites don't.)
4. Create WhatsApp message templates in the content workspace — every template needs Meta approval before a flow can send it.

D. Stand up consent & subscriptions (do this before your first send)

1. In the Marketing Cloud app, open the Consent area and create a Communication Subscription (e.g. "Promotional Email") and attach it to an Engagement Channel (Email / SMS / WhatsApp).
2. Import historical opt-ins (CSV import or a flow) so Communication Subscription Consent records exist — remember: no record = opt-out.
3. Add the Privacy Consent Status component to Lead/Contact (and Person Account) Lightning record pages via Setup → Edit Page, so anyone can see and flip per-subscription status.
4. Build a preference page (custom branded preference centers are GA since Spring '26) and wire your email footer's unsubscribe/manage-preferences links to it.
5. Migrating from MCE? The consent mapping tool maps MCE subscriber/publication lists onto Communication Subscriptions — SMS/WhatsApp mapping rolling out gradually by August 17, 2026. Verify availability in your org before promising it.

---

🎤 Rapid-fire

1. Q: What must exist before MC Next will send a single email? A: An active Authenticated Domain (DKIM-verified, self-hosted DNS) and a From address on it. …and in practice: Settings → Channels → Email → Go to Authenticated Domains → + Add Domain.

2. Q: Who handles SPF on the new stack? A: Salesforce — you add no SPF records. Your job is 3 DKIM records, 5 inbound CNAMEs, and (recommended) DMARC. …and in practice: hand the generated records to IT from the Add Domain wizard and click Activate My Domain when they're live.

3. Q: A contact has no consent record for your "Offers" subscription — what happens on send? A: They're treated as opt-out and skipped. Consent is default-deny per contact point. …and in practice: check the Privacy Consent Status component on the Contact record, or import consent via CSV/flow before the campaign.

4. Q: Map classic subscriber status to the new model. A: All Subscribers status → Communication Subscription Consent (per contact point, per subscription, per channel); publication lists → Communication Subscriptions. …and in practice: create subscriptions in the Consent area, then use the MCE consent-mapping tool for migration (SMS/WhatsApp mapping GA-rolling by Aug 17, 2026).

5. Q: Two-way SMS — which edition and what routes the replies? A: Advanced (Unified Conversations for SMS): one number; Flow owns marketing sends, Omni-Channel routes service replies to agents or an Agentforce bot (Digital Engagement license needed). …and in practice: set up the Unified Messaging SMS channel, then define routing.

6. Q: WhatsApp in MC Next — GA or roadmap? A: GA as a paid add-on on both Growth and Advanced; Advanced adds Unified Conversations for WhatsApp. Templates require Meta approval. …and in practice: Meta Business Manager + verified business first, then Settings → Channels → WhatsApp guided connect.

7. Q: How long until you can actually send SMS in a new org? A: Long code ≈ 4–6 weeks self-service (Brand ~5 days → Campaign ~10 → Code ~2, plus queue time); short code 12+ weeks via partner at ~$8k–15k. …and in practice: start Brand registration on day one of any implementation — it's the long pole.

8. Q: How do dedicated IPs work now? A: Dynamic dedicated IPs (GA Spring '26): ~5M emails/month triggers auto-migration, automatic warming over 0–35 days, up to 32 IPs, reclaimed if volume falls. …and in practice: nothing to click — it's volume-driven; your job is consistent volume and clean lists.

9. Q: MobileConnect and GroupConnect — where did they go? A: Functionally replaced by the SMS channel and the native WhatsApp channel on Unified Messaging, both sent via Flow. Keywords/compliance and Meta plumbing survive; the studios don't. …and in practice: everything lives under Settings → Channels, not in separate studios.

10. Q: Why does Salesforce say to use a different subdomain than your MCE one? A: Reputation isolation — MC Next and MCE are different sending infrastructures; sharing a subdomain muddies DKIM alignment and deliverability signals. …and in practice: mail.brand.com for MCE, msg.brand.com (or similar) for MC Next.

---

⚠️ Gotchas / currency notes

• The implicit opt-out flip is the migration killer. Classic email sent to anyone not unsubscribed; MC Next sends to no one without an opt-in record. Budget a consent-import workstream (and remember SMS consent can only be imported after the code is provisioned).
• Authenticated domains are forever. Once created they can't be deleted — typo'd subdomains haunt the org. Double-check before Submit.
• "Unified Messaging" ≠ "Unified Conversations." Unified Messaging is the channel framework (Email/SMS/WhatsApp/RCS on the Unified Conversation Platform + Data 360); Unified Conversations is the two-way, Advanced-only capability on top. Help pages are mid-rename — read edition tables carefully.
• Number portability is release-dependent. Help long said Unified SMS needs a new number (no upgrades from legacy Service Cloud channels), but later releases enabled reusing US/Canada MCE short/long codes in MC Next. Verify the current help article for your region before telling a client they must re-provision. (SFMC Tips #165 — Winter '26)
• Duplicate consent DSOs exist. Since Summer '25, Communication Subscription Consent may map to both MessagingConsent (legacy) and MessagingConsentV2 DSOs — only V2 is written to, but older orgs show two records per contact point/subscription. Don't panic in a data audit.
• WhatsApp/MMS features are heavily country-gated: WhatsApp payments = Brazil (Spring '26) and India UPI (Summer '26); MMS/contact cards = US/Canada only; RCS (Summer '26) = US, UK, Mexico, Brazil, Germany, France. Never quote a feature without its country list.
• Pricing metric names churn. Public materials have variously quoted per-send email allowances (e.g. 180k/yr on Growth), SMS per-1,000 pricing, and messaging-credit multipliers by code type/country; older rate cards used different send metrics. In an interview, explain the mechanism (org-based edition fee + send allowance + messaging credits) and say "current rate card would confirm exact numbers."
• Classic vocab trap: if you say "Sender Authentication Package," "MobileConnect keyword," or "All Subscribers" in a MC Next interview, immediately translate: Authenticated Domain, SMS channel compliance keywords, Communication Subscription Consent. Showing the mapping is the differentiator.

---

Summary: every MC Next send — email, SMS, WhatsApp — flows from a Flow through one consent gate (Communication Subscription Consent, default opt-out) into channel infrastructure: an Authenticated Domain (3 DKIM + 5 CNAMEs, SPF by Salesforce) for email, a Brand→Campaign→Code provisioned number plus credits for SMS, and a Meta-connected paid add-on for WhatsApp — with two-way Unified Conversations reserved for Advanced edition.

Sources

• Marketing Cloud Next — Authenticating Marketing Cloud Next Emails (Salesforce Help)
• Marketing Cloud Next — Email Authenticated Domains Setup and DNS Tips (Salesforce Help)
• SFMC Tips #140 — Steps for Email Domain Authentication
• What's Unified Messaging? (Salesforce Help)
• Set Up an SMS Conversation in Unified Messaging (Salesforce Help)
• Quick Starts: SMS for Marketing Cloud Next (Salesforce Help)
• Set Up SMS Messages in Marketing Cloud Next (Salesforce Help)
• Set Up WhatsApp in Marketing Cloud Next (Salesforce Help)
• Understanding Consent Concepts in Marketing Cloud Next (Salesforce Help)
• The Agentic Marketer — Consent Management in Marketing Cloud Next explained
• The Spot — SMS Provisioning and Marketing Cloud on Core
• Salesforce blog — Expanded Global Availability for Marketing Cloud Growth and Advanced
• Salesforce Ben — Marketing Cloud Growth vs. Advanced Editions
• Salesforce Ben — Salesforce Marketing Cloud Pricing
• Concret.io — Marketing Cloud Next Explained: Growth, Advanced & Plus
• SFMC Tips #218 — Marketing Cloud Next: Spring '26 Release Highlights
• SFMC Tips #285 — Marketing Cloud Next: Summer '26 Release Highlights
• SFMC Tips #165 — Marketing Cloud Next: Winter '26 Release Highlights

➡️ Next: N08_Campaigns_End_to_End.md

N08 — Campaigns End-to-End (brief → audience → content → flow → send → results)

🎯 Why this matters: This is the module where the whole course becomes muscle memory. N02–N05 gave you the parts — Data Cloud, segments, CMS content, flows. Here you run one complete campaign through the new UI, twice: once letting Agentforce draft it from a brief, once building it by hand. In classic Engagement you'd say "I built the DE, wrote the SQL, made the email in Content Builder, wired Journey Builder." Your interview-winning sentence for Marketing Cloud Next is: "I wrote the brief, the agent drafted the segment, content, and flow, and I reviewed, fixed, activated, and read the dashboards." Your known gap is click-fluency — this module is nothing but clicks.

---

🧠 One-screen mental model

Six stages, always in this order. Agentforce can draft the first four from one prompt; you always own the last two.

        ┌───────────────────────────────────────────────────────────────┐
        │  AGENTFORCE CAMPAIGN AGENT (chat panel in the Marketing app)   │
        │  one prompt → Campaign Brief → Campaign Preview → drafts of    │
        │  the segment, the messages, and the flow — YOU edit and ship   │
        └──────┬───────────┬─────────────┬─────────────┬────────────────┘
               ▼           ▼             ▼             ▼
 1 BRIEF ──▶ 2 AUDIENCE ──▶ 3 CONTENT ──▶ 4 FLOW ──▶ 5 ACTIVATE ──▶ 6 RESULTS
 (Campaign    (Segment on    (email in     (Segment-     (publish        (Analytics tab:
  Brief rec:   Unified        email editor  Triggered     segment,        dashboards +
  goal, KPIs,  Individual,    / CMS, brand  Flow: Send    Activate the    reports on
  audience,    publish        kit, merge    Email, Wait,  flow → sends    Data 360 /
  key msg,     schedule)      fields, AI    Decision,     run on the      Tableau Next;
  CTAs)                       copy)         Path Exp.*)   schedule)       ask the agent)

  *Path Experiment = Advanced edition only

---

🔑 Core in 60 seconds

• The Campaign is a real Salesforce object, and it's the container. Everything hangs off the campaign record: brief, flows, content, members, metrics. A campaign can hold many flows, but each flow belongs to one campaign. The record mirrors some of the Flow Builder canvas — not all of it, and vice versa. (Get Started with Marketing Campaigns and Flows)
• Agent-assisted creation is GA, and brief-first. From the Marketing app home: New Campaign → Draft with Agentforce, describe the objective, and the agent drafts a Campaign Brief (name, description, key message, target audience, goal, CTAs, KPIs), then a Campaign Preview with segments, multichannel message content, and the flow. You refine conversationally, then save — the save creates the campaign record, flow, and content. (Agentforce in Marketing Cloud Next — Salesforce Help)
• Three manual ways to start a flow on a campaign: pick a flow trigger (build from scratch), a flow template, or a quick start (common use cases like Single Email, Message Series, Sign-up Form — most map to a Segment-Triggered Flow). (Create and Manage a Campaign Flow, The Agentic Marketer — 8 flow types)
• Audience = a published segment on Unified Individual in the default data space; publishing it makes it campaign-ready (no separate activation step — N03's rule). (Segmentation in MC Next)
• Content = the email editor on Salesforce CMS, personalized with Handlebars-style merge fields resolved through the data graph (any attribute related to the Unified Individual). Insert via the picker, never hand-type. (Personalizing Content with Merge Fields)
• Send = activate the flow. Send Email Message / Send SMS Message elements + Waits + Decisions (N05's S-E-W-D). Activation is a human click; the agent never activates for you.
• Approvals are DIY, not built-in. MC Next ships no native campaign-approval feature (classic MCE Campaign Approvals was even retired). The agent actions (Draft a Campaign Brief, Create a Campaign from a Brief, Save Campaign…) are themselves powered by Flow — your admin can open them in Flow Builder and bolt on approval steps or notifications. (Agentforce in MC Next, Campaign Approvals Retirement)
• Results live on the Analytics tab — dashboards powered by Data 360 + Tableau Next (rearrangeable widgets, filters by campaign/flow/segment/message), plus standard reports like All Email Activities, Top Campaigns by Click-Through Rate, Email Send Outcomes. You can also just ask Agentforce to summarize campaign performance in chat. (Measure Success in MC Next, SFMC Tips #114)
• Edition gate: all of the above needs Enterprise or Unlimited with Marketing Cloud Growth or Advanced; the agent needs Einstein generative AI switched on in Setup first. (Agentforce in MC Next)

---

🧩 Mnemonics & memory hooks

• The six stages: "B-A-C-F-A-R" → "Brilliant Agents Craft Flows; Anyone Reviews." Brief → Audience → Content → Flow → Activate → Results. Chant it before any demo or interview whiteboard.
• "Agent drafts, human ships." Agentforce owns stages 1–4 as drafts; activation and results are always yours. If an interviewer asks "does the agent send the campaign?" — no, it stops at draft.
• Three ways to start a flow: "T-T-Q" → Trigger, Template, Quick start. From-scratch, pre-built-but-editable, or use-case-in-a-box.
• Brief anatomy: "Name-D-K-T-G-C-K" is too ugly — use "a brief is a mini creative agency form": name, description, key message, target audience, goal, CTAs, KPIs. If you can fill a creative-agency intake form, you can write a campaign brief.
• Advanced-only extras: "P.U.E.E." → "Paths Unlock Einstein Extras." Path Experiment, Unified Conversations (two-way SMS), Einstein Engagement Scoring, Einstein Engagement Frequency.
• Campaign : Flow = Journey folder : Journey. One campaign, many flows; one flow, one campaign. (Classic analogy: a campaign is the program, each flow is one journey/automation inside it.)

---

🛠️ In practice (what you would actually click)

Worked example throughout: "Northloft" — a GAP-like apparel brand. Goal: a welcome series for new loyalty signups → 3 emails + an SMS nudge, 10% off first purchase.

Phase 0 — one-time admin prerequisites (know these exist)

1. Setup (gear icon) → Einstein Setup → turn on Einstein generative AI. Without this, Draft with Agentforce never appears. (Requires Enterprise/Unlimited + MC Growth or Advanced.)
2. Data foundation from N02–N03 must exist: streams flowing, identity resolution published, a default data space with Unified Individuals.
3. For dashboards: Set Up Marketing Performance and install the required analytics packages (Analytics tab stays thin until this is done). (Measure Success in MC Next)
4. Brand: define your brand (logo, colors, fonts, button styles) so generated content lands on-brand. (Setup naming around brands/brand kits has shifted across releases — find it via Setup Quick Find → "Brand".)

Phase A — the agent-assisted path (the demo they will ask about)

1. App Launcher (waffle, top-left) → search "Marketing" → open the Marketing app.
2. On the Marketing app home: New Campaign → Draft with Agentforce (or open the Agentforce chat panel via its icon and start typing). (Salesforce Help)
3. Describe the objective in plain language. Northloft prompt: "Create a welcome campaign for customers who joined our loyalty program in the last 7 days and haven't purchased yet. Three emails over two weeks, warm friendly tone, 10% off first purchase, drive first online order." You can also point it at an existing brief or uploaded strategy doc.
4. The agent drafts a Campaign Brief: proposed name, description, key message, target audience, primary goal, CTAs, KPIs. Refine in chat ("make the tone more premium", "target only India") until it's right, then click Save Brief. A Campaign Brief record is created. (SFMC Tips #117)
5. On the brief record, click Select Brand → pick Northloft's brand so colors/fonts/buttons apply to everything generated.
6. Click Generate Campaign Preview. The agent proposes the campaign: email sequence (e.g., 3 emails), wait intervals between sends, subject lines, body copy — and the audience/segment drafted from the brief's target-audience line.
7. Click Preview → review everything under the Campaign Preview tab. Click into each message to edit subject/body; ask the chat to change channels, tone, or wait times.
8. Click to save the campaign preview → this is the moment the real artifacts are created: the Campaign record, the associated flow (send → wait → send…), and the email content with brand settings applied. (SFMC Tips #117)
9. Now inspect like an engineer: open the segment (does the logic really say joined ≤ 7 days AND purchases = 0?), open each email (merge fields present? fallbacks?), open the flow (waits correct? re-entry sensible?). The draft is a junior marketer's first pass — treat it that way.
10. Fix, then Activate the flow (Phase B step 10 below). The agent does not activate.

Phase B — the manual path (build the same thing by hand — know both!)

Audience (N03 skills): 1. Marketing app → Segments tab → New. 2. Segment on Unified Individual (default data space — campaign segments must live here). 3. Drag attributes into the rule canvas: Loyalty Join Date within last 7 days AND Total Purchases = 0 (via related objects/calculated insights). 4. Set the publish schedule (Standard 12–24h / Rapid / Immediately — pick Rapid for a welcome series so new joiners flow in quickly), then Save and Publish. Published = campaign-ready; there's no separate activation step.

Campaign shell: 5. Campaigns tab → New → name it Northloft_Welcome_2026 → Save. (Create and Manage a Campaign Flow)

Flow (N05 skills): 6. On the campaign record, create the flow — choose one of the three starts: a flow trigger (from scratch), a flow template, or a quick start like Message Series (which gives you a pre-wired Segment-Triggered Flow, often with placeholder CMS content). 7. In the Start element, select your published segment, set the schedule/recurrence, and re-entry (after completion is the safe welcome-series default). 8. Build the spine: Send Email Message (Welcome + 10% code) → Wait for Amount of Time (2 days) → Decision (clicked the offer?) → Yes: Send Email Message (style-guide email) / No: Send SMS Message ("your 10% is waiting") → Wait (5 days) → final Send Email Message (last-chance reminder). 9. Advanced edition only: replace the first send with a Path Experiment (e.g., 50/50 subject-line test) — this element simply isn't there in Growth.

Content (N04 skills — done inline from each Send element or ahead of time in CMS): 10. From the Send Email Message element, create/select the email → the email editor opens (Salesforce CMS-backed): drag components, apply the brand, use the sparkle (Einstein generative AI) button to draft or rewrite copy, and insert merge fields via the picker — e.g. first name from the data graph (Handlebars-style triple-brace tokens; never hand-type them). Check consent: sends honor communication-subscription/consent status, so make sure your loyalty signup writes consent correctly. 11. Preview and test: use the preview-as-recipient and send-test options in the editor before you ever activate.

Approvals (if your org added them): 12. Out of the box there is no approval gate. If governance requires one, the admin has either (a) added a standard Approval Process on Campaign, or (b) edited the agent-action flows (Save Campaign etc.) in Flow Builder to insert approval steps. Ask which pattern the org uses — good interview question to ask them.

Activate: 13. Save the flow → Activate. Members of the published segment are injected on the flow's schedule; sends begin. Editing an active flow creates a new version you must activate — core Flow behavior, nothing like Journey Builder's "stop and copy".

Phase C — results (close the loop)

1. Campaign record → check flow/engagement summary panels on the record itself.
2. Marketing app → Analytics tab → open the dashboards (powered by Data 360 + Tableau Next): filter by date range, campaign, flow, segment, or email. The Email Performance Dashboard covers sends, delivery rate, opens, clicks, bounces, unsubscribes. (Email Performance Dashboard)
3. Standard reports to name-drop: All Email Activities (metrics by flow), Top Campaigns by Click-Through Rate, Email Send Outcomes (per email element in the flow). (SFMC Tips #114)
4. Or just ask the agent: "Summarize the performance of Northloft_Welcome_2026 and suggest one improvement." Performance Q&A in chat is a supported Agentforce use. (Salesforce Help)
5. Iterate: tighten the segment, rewrite the losing email, adjust waits — on Advanced, read the Path Experiment results to pick the winning variant.

---

🆚 Growth vs Advanced in this walkthrough

(Salesforce Ben — Growth vs Advanced)

---

🎤 Rapid-fire

1. Q: Walk me through a campaign in Marketing Cloud Next in one breath. A: Brief → audience → content → flow → activate → results. Agentforce can draft the first four from one prompt; a human reviews, activates, and reads the dashboards. …and in practice: Marketing app → New Campaign → Draft with Agentforce → refine → Save Brief → Generate Campaign Preview → save → inspect → Activate.

2. Q: What exactly does the agent generate from a brief? A: A campaign preview containing the proposed name, the segment(s), multichannel message content (email/SMS drafts with subject lines and body), and the flow with waits — saving the preview creates the campaign record, flow, and content as drafts. …and in practice: the buttons are Save Brief, Select Brand, Generate Campaign Preview, then save the preview.

3. Q: Campaign vs flow — what's the data relationship? A: Distinct objects. One campaign relates to many flows; each flow relates to exactly one campaign. The campaign record mirrors only part of the Flow Builder canvas. …and in practice: you switch between a campaign's flows from the campaign record, but deep edits happen in Flow Builder.

4. Q: Three ways to add a flow to a campaign? A: Flow trigger (from scratch), flow template, or quick start (Single Email, Message Series, Sign-up Form…). …and in practice: quick starts pre-wire a Segment-Triggered Flow with placeholder CMS content — fastest demo path.

5. Q: Where does the campaign audience come from? A: A published segment on the Unified Individual object in the default data space; publishing makes it campaign-ready — no separate activation step. …and in practice: Segments tab → build → set publish schedule (Rapid for time-sensitive campaigns) → Publish, then select it in the flow's Start element.

6. Q: How do you A/B test inside the flow, and what's the catch? A: Path Experiment — weighted random path assignment (e.g., 60/40) with winner readout. Catch: Advanced edition only; on Growth you approximate with a Decision on a random-ish attribute, which is not a clean experiment. …and in practice: drag Path Experiment after Start, set variations and weights.

7. Q: Does Marketing Cloud Next have campaign approvals? A: Nothing native. You add governance yourself — a standard Salesforce Approval Process on Campaign, or by editing the Flow-powered agent actions (Save Campaign, etc.) to insert approval steps. …and in practice: admins open those actions in Flow Builder and add the gate there.

8. Q: Campaign is live — where do you read results? A: The Analytics tab: dashboards powered by Data 360 + Tableau Next, filterable by campaign/flow/segment/message, plus standard reports (All Email Activities, Top Campaigns by Click-Through Rate, Email Send Outcomes). …and in practice: you can also ask the Agentforce panel to summarize campaign performance in chat.

9. Q: Can you edit a live campaign flow? A: Editing an active flow saves a new version that you then activate — standard core Flow versioning, no Journey Builder-style "create new version of journey" ceremony, and no editing history semantics from classic. …and in practice: deactivate/activate is on the Flow Builder toolbar; in-flight members follow the version rules of core Flow.

10. Q: What must an admin enable before any of this works? A: Enterprise/Unlimited org with MC Growth or Advanced, Einstein generative AI turned on in Setup, Data Cloud foundations (identity resolution, default data space), and the marketing analytics packages for dashboards. …and in practice: if Draft with Agentforce is missing, check Einstein Setup first.

---

⚠️ Gotchas / currency notes

• The agent drafts; it does not ship. Generated copy quality is genuinely mid (practitioners note it "hasn't reached the level we envision") and segment logic can be looser than the brief implied. Review every artifact before activating — in an interview, saying "I always audit the generated segment logic" is a senior signal. (SFMC Tips #117)
• Campaign Preview buttons go inert after save. Once the preview becomes a real campaign, its generate/preview buttons deactivate — iterate on the campaign, not the old preview record.
• Segment cadence vs flow schedule mismatch = stale audience. If the segment publishes Standard (12–24h) but the flow runs hourly, you send to yesterday's list. Match Rapid/Immediately publishing to time-sensitive flows — and remember segment refreshes burn Data 360 credits.
• Brief quality is the real lever. Vague prompt → generic campaign. Feed the agent specifics (audience definition, tone, offer, KPIs, guardrails) or reference an uploaded strategy doc. "Creating a high-quality brief is the key to success" is the practitioner consensus.
• Don't claim classic features exist here. No Content Builder approvals, no Journey Builder Test mode, and classic MCE Campaign Approvals was retired as a product feature — approvals in MC Next are platform DIY. Saying "I'd use the approval workflow in Marketing Cloud" without qualifying which Marketing Cloud will hurt you.
• Naming drift, again (July 2026): the same product surface has been marketed as Marketing Cloud Growth/Advanced → Marketing Cloud Next (Connections, June 2025) → increasingly Agentforce Marketing under the Agentforce 360 umbrella; analytics moved to Tableau Next-powered dashboards. Feature names in this module were verified against Salesforce Help as of July 2026 — recheck before an interview, since agent capabilities (e.g., PDF/Word-to-campaign, more subagents) are expanding every release.
• Classic-vs-Next reflex to retrain: old you = "DE → SQL → Content Builder → Journey Builder → Tracking." New you = "Brief → Segment → CMS email → Flow → Analytics tab." Same marketing brain, different nouns, plus an agent drafting alongside you.

---

Sources

• Agentforce in Marketing Cloud Next — Salesforce Help
• Get Started with Marketing Campaigns and Flows — Salesforce Help
• Create and Manage a Campaign Flow in Marketing Cloud Next — Salesforce Help
• Measure Success in Marketing Cloud Next — Salesforce Help
• Email Performance Dashboard — Salesforce Help
• Segmentation in Marketing Cloud Next — Salesforce Help
• Personalizing Content with Merge Fields — Salesforce Help
• Marketing Cloud Campaign Approvals Retirement — Salesforce Knowledge
• SFMC Tips #117: Campaign Creation Agent — Nobuyuki Watanabe (Medium)
• SFMC Tips #114: Standard Reports and Dashboards — Nobuyuki Watanabe (Medium)
• Marketing Cloud Growth vs Advanced Editions — Salesforce Ben
• The 8 Main Marketing Flow Types — The Agentic Marketer
• Saving Time with Flow Templates in Agentforce Marketing — The Spot (Apr 2026)
• Create and Customize a Marketing Campaign with Agentforce — Trailhead
• 5 Ways to Accelerate Campaign Creation with Agentforce — Salesforce Blog

➡️ Next: N09_Einstein_and_Agentforce_Marketing.md

N06 — Einstein & Agentforce for Marketing

🎯 Why this matters: In classic Marketing Cloud Engagement (MCE) "Einstein" meant a handful of bolt-on predictive/analytic tools — Send Time Optimization (STO), Engagement Scoring, Engagement Frequency, Copy Insights — plus early generative subject-line/copy help. In Marketing Cloud Growth / Advanced ("Marketing Cloud Next," on the Agentforce 360 / Core platform), the AI story splits into two layers: (1) the same predictive Einstein features (now edition-gated), and (2) a generative + agentic layer — generative content and Agentforce marketing agents that draft a brief, build segments from prompts, generate emails/SMS, and assemble a campaign flow. This is the single most hype-prone area of the platform, so this module is deliberately careful to separate GA today from roadmap. Nail the GA-vs-coming split in an interview and you sound like someone who has actually used it — not someone repeating a keynote.

---

🧠 One-screen mental model

You (or an agent) write a prompt. Before the LLM answers, Salesforce grounds it in your real data — Data Cloud (Data 360) unified profiles/segments plus brand context — and applies permissions/guardrails (the Einstein Trust Layer). The model returns a generated asset (subject line, copy, image, whole email) or a segment/campaign draft, and a human accepts or refines before anything ships.

                                   ┌───────────────────────────────────────────┐
   YOU / AGENT                     │        GROUNDING  (Einstein Trust Layer)    │
 ┌──────────────┐   prompt         │   • Data Cloud / Data 360 unified profiles  │
 │  Prompt /    │ ───────────────► │   • Segments, calculated insights           │
 │  Brief goal  │                  │   • Brand context (voice/assets)            │
 └──────────────┘                  │   • Permissions, masking, audit             │
        ▲                          └───────────────────┬─────────────────────────┘
        │ accept / refine                               │ grounded prompt
        │ (human in the loop)                           ▼
 ┌──────┴───────────────────────┐              ┌─────────────────┐
 │  GENERATED OUTPUT             │ ◄─────────── │       LLM       │
 │  • subject line / body copy   │   response   │ (foundation     │
 │  • image (add-on)             │              │  model via      │
 │  • Data Cloud SEGMENT draft   │              │  secure gateway)│
 │  • campaign brief → flow      │              └─────────────────┘
 └───────────────────────────────┘
   then → activated in a Marketing Flow (see N05)

---

🔑 Core in 60 seconds

• Two AI layers, don't conflate them. (1) Predictive Einstein = the classic scoring/timing/frequency models. (2) Generative + Agentforce = LLM content creation and autonomous/assistive marketing agents. Both exist in Marketing Cloud Next; they're licensed and edition-gated differently. (Trailhead — AI in Marketing Cloud Next)
• Generative content is GA in both Growth and Advanced: draft subject lines and body copy in Content Builder / the Content Editor, and get Einstein Campaign Briefs (draft brief + suggested KPIs/components). (Salesforce Ben — Growth vs Advanced, Salesforce Help — Agentforce in Marketing Cloud Next)
• The Campaign Creation Agent (Agentforce) is real and GA. From one brief/prompt it can draft a campaign brief, create a target segment (via Einstein Segment Builder), generate email + SMS content, and assemble a campaign flow — and you accept or refine each proposed item (human in the loop). (Salesforce Help, The Agentic Marketer — Campaign & Content agents)
• Segments from natural language is GA in both editions. "Create a segment of high-value customers in California who haven't purchased in 90 days" → a Data Cloud segment, grounded in Data 360 (marketing/sales/service/commerce data). (Salesforce Ben — Growth vs Advanced, Salesforce — Agentic Marketing)
• Grounding is the whole trust story. Prompts are grounded in Data Cloud / Data 360 unified data plus brand context, and governed by permissions and the Einstein Trust Layer (masking, audit). Garbage/ungrounded data = garbage output — clean, unified data is a prerequisite, not a nice-to-have. (Salesforce — Agentic Marketing, The Agentic Marketer — AI & Agentforce)
• Predictive Einstein is edition-split. STO and Metrics Guard are in both Growth and Advanced; Engagement Scoring and Engagement Frequency (the predictive propensity models) are Advanced only. (The Agentic Marketer — Growth vs Advanced, Salesforce Ben — Growth vs Advanced)
• "Campaign Designer" (auto-builds the whole campaign flow) is Advanced-only. Growth gets the AI-generated pieces (brief, segment, draft content); the richer auto-assembly/optimization sits in Advanced. (The Agentic Marketer — Growth vs Advanced)
• Brand personalities/Brand Center feed brand voice into the model, but be careful with naming: the mature "2 default + up to 10 custom brand personalities" and the Typeface image add-on are documented on the classic MCE generative feature set; on-core Brand Center has been noted as limited GA. Verify per org. (Salesforce Help — Einstein Generative AI in MCE, Salesforce Help — Agentforce in Marketing Cloud Next)

---

🧩 Mnemonics & memory hooks

• "Predict vs Produce." Two AI buckets: Predict = classic Einstein models (STO, scoring, frequency). Produce = generative/agentic (copy, images, segments, campaigns). Interviewers reward you for separating them.
• "G.R.A.B." for grounding: Ground in Data Cloud → Restrict with permissions/Trust Layer → Apply brand voice → Build the asset. No grounding, no trust.
• "Both / Advanced" for predictive Einstein: Both editions = STO + Metrics Guard. Advanced-only = Scoring + Frequency (the propensity predictions). Hook: "Scoring & Frequency are the Fancy pair → Advanced."
• "Brief → Segment → Content → Flow → Summary" = the five things the Campaign Creation Agent touches, in order. Say it as "B-S-C-F-S."
• "Accept or Refine" — the two-word reminder that these are assistive with a human gate, not fire-and-forget autonomy. Never claim an agent ships a campaign unsupervised.
• "Designer = Advanced." Campaign Designer (auto-assembles the flow) lives in Advanced; Growth gets the parts, not the auto-build.

---

🔁 Coming from classic Engagement

Key mindset shifts: 1. Predictive Einstein didn't disappear — it got re-packaged and edition-gated. If you say "Engagement Scoring" without noting it's Advanced-only, you'll look out of date. 2. The new thing is generative + agentic, and it lives on top of Data Cloud. No unified data → weak grounding → weak output. Your MCE "build the DE first" instinct becomes "get the Data Cloud model + segments right first." 3. Agents are assistive with a human gate, today. The realistic pitch is "draft in minutes, human approves," not "autonomous marketer." Overclaiming is the #1 way to sound like you're quoting marketing.

---

🎤 Rapid-fire

1. Q: What are the two distinct AI layers in Marketing Cloud Next, and why keep them separate? A: Predictive Einstein (STO, Engagement Scoring, Engagement Frequency, Metrics Guard) and generative/agentic (LLM content, Agentforce agents). They're licensed and edition-gated differently, so lumping them together leads to wrong claims about availability.

2. Q: Which predictive Einstein features are in Growth vs Advanced? A: Both: Send Time Optimization and Metrics Guard. Advanced-only: Einstein Engagement Scoring and Einstein Engagement Frequency (the propensity-prediction models). Path Experiment is also Advanced-only.

3. Q: What does the Agentforce Campaign Creation Agent actually do today? A: From a brief/prompt it drafts a campaign brief, builds a target segment (Einstein Segment Builder), generates email + SMS content, assembles a campaign flow, and can summarize results — with the marketer accepting or refining each proposed item. It's assistive with a human in the loop, not unsupervised.

4. Q: How does grounding work, and why does it matter for trust? A: Before the LLM answers, the prompt is grounded in Data Cloud / Data 360 unified data (profiles, segments, calculated insights) plus brand context, and governed by permissions and the Einstein Trust Layer (masking, audit). It makes output relevant and keeps sensitive data controlled — and it means clean, unified data is a prerequisite.

5. Q: Can you build a segment by just describing it? A: Yes — natural-language segment creation is GA in both Growth and Advanced, producing a Data Cloud segment grounded in Data 360 across marketing/sales/service/commerce data.

6. Q: Is generative image creation a safe thing to claim as GA? A: Be careful. Generative text (subject lines, body copy) is GA. Generative images are documented largely via the Typeface add-on on classic MCE; for Marketing Cloud Next, verify per org/edition rather than asserting it's standard GA.

7. Q: What's the deal with Brand Center / brand personalities? A: Brand context feeds voice/tone into the model. The mature "2 default + up to 10 custom brand personalities" is documented on classic MCE; on-core Brand Center has been reported as limited GA. Say "brand grounding exists; confirm the exact Brand Center status per org."

8. Q: What's the honest limit of Agentforce marketing agents right now? A: They draft and assist — brief, segment, content, flow — with a human approval gate, and they depend on well-modeled Data Cloud data. They are not autonomous end-to-end marketers; overclaiming autonomy is the classic hype trap.

---

⚠️ Gotchas / currency note

• 🔄 This is the fastest-moving, most hype-prone area of the platform — verify every claim against the current release before an interview. Feature names, edition gating, and GA status shift most releases. What's below is accurate to mid-2026 sourcing but must be re-checked. (Salesforce Help — Agentforce in Marketing Cloud Next)
• Don't claim full autonomy. Today's marketing agents are assistive with a human accept/refine gate. The realistic story is "draft a campaign in minutes, human approves," not "the agent runs marketing by itself." (The Agentic Marketer — Campaign & Content agents)
• Watch classic-vs-Next naming. The mature generative details — 2 default + up to 10 brand personalities, a ~10,000 generation cap, the Typeface image add-on — come from the classic MCE "Einstein Generative AI" docs. Don't assert them verbatim for on-core Growth/Advanced without confirming. (Salesforce Help — GenAI in MCE)
• Generative images ≠ generative text in maturity. Text generation is clearly GA; treat image generation as verify-per-org. (Salesforce Help — GenAI in MCE)
• Grounding depends on Data Cloud being set up right. Agents/generation are only as good as the unified data, data graphs, and segments behind them. If Data 360 isn't modeled, grounding is weak and "AI magic" underdelivers — call this out as a prerequisite. (The Agentic Marketer — AI & Agentforce)
• Edition gating traps. Saying "we'll use Engagement Scoring in Growth" is wrong (Advanced-only). Same for Path Experiment and Campaign Designer (auto-flow build) — both Advanced. Confirm the org's edition first. (The Agentic Marketer — Growth vs Advanced)
• Roadmap items that are dated, not "someday": conversational campaign preview refinement was noted for Spring '26; two-way messaging targeted for Feb 2026; Business Units are Advanced-edition. Cite these as roadmap/recent-release, not as long-standing GA. (The Agentic Marketer — Campaign & Content agents, Salesforce Ben — Rebuilding Marketing Cloud)
• "Einstein GPT / Marketing GPT" is legacy branding. Older articles use "Einstein GPT" or "Marketing GPT"; the current umbrella is Einstein + Agentforce on the Agentforce 360 platform. Use current names in an interview. (Salesforce Ben — Rebuilding Marketing Cloud)

---

➡️ Next: N10_Analytics_and_Attribution.md

N10 — Analytics, Reporting & Attribution in MC Next

🎯 Why this matters: In classic SFMC you measured with the Tracking tab, data views (_Sent, _Open, _Click…), tracking extracts and maybe Datorama. All of that is gone in Marketing Cloud Next. Engagement events now land in Data 360 DMOs, and you look at them through core Reports & Dashboards, Tableau Next–powered dashboards, and a native revenue-attribution feature (Opportunity Influence) that classic never had. Interviewers love this module because it's where "I know classic" people get exposed — you'll be the one who can name the exact dashboard, the exact DMO, and the exact Setup node.

---

🧠 One-screen mental model

One pipe in, four windows to look through, one judge of credit:

   CAPTURE                    STORE (Data 360)                LOOK AT IT (4 windows)
 ┌──────────────┐          ┌─────────────────────┐        ┌────────────────────────────────┐
 │ sends, opens │  events  │ Engagement DMOs      │        │ 1 Campaign page → Insights      │
 │ clicks, SMS, │ ───────▶ │  · Email Engagement  │ ─────▶ │ 2 Analytics tab → standard      │
 │ WhatsApp,    │          │  · Message Engagement│        │   Reports & Dashboards          │
 │ forms, pages │          │ (DLO: Messaging      │        │ 3 Marketing Performance         │
 └──────────────┘          │  EventsEmailV2)      │        │   Intelligence (Tableau Next)   │
                           └──────────┬──────────┘        │ 4 Record page → Unified         │
                                      │                    │   Engagement History            │
                        ┌─────────────▼─────────────┐     └───────────────┬────────────────┘
                        │ Calculated Insights ·      │                     │
                        │ Data Explorer · reports on │     WHO GETS CREDIT (attribution)
                        │ DMOs · segments on         │    ┌───────────────▼────────────────┐
                        │ engagement → activation    │    │ Opportunity Influence (native,  │
                        └───────────────────────────┘     │  first/last touch, via Data 360)│
                        REUSE & EXPORT the same data      │ Marketing Intelligence add-on   │
                                                          │  (multi-touch + funnel models)  │
                                                          └────────────────────────────────┘

---

🔑 Core in 60 seconds

• Edition line to memorize: reporting in MC Next is "Available in: Salesforce Enterprise and Unlimited Editions with Marketing Cloud Next Growth or Advanced Edition." (Measure Success in Marketing Cloud Next)
• Engagement lands in Data 360, not data views. Email sends/opens/clicks/bounces flow into a DLO (MessagingEventsEmailV2 since Summer '25; V1 was MessagingEventsEmail) mapped to the Email Engagement DMO; SMS/WhatsApp events land in the Message Engagement DMO. (Email Engagement DMO — Salesforce Developers) · (SFMC Tips #97)
• Window 1 — the campaign itself. Open a campaign record → Insights (left side) → Campaign Performance Dashboard: opens, clicks, CTR, delivery/bounce/unsubscribe rates, filterable by date, flow, segment, channel (Email / SMS / WhatsApp), with export. (Reporting in Marketing Cloud Next) · (SFMC Tips #115)
• Window 2 — standard core Reports & Dashboards. After installing analytics packages, the Analytics tab carries pre-built email/SMS/forms/landing-page engagement reports & dashboards (e.g. All Email Activities, KPIs for Email Engagement, Top Campaigns by Click-through Rate). This is ordinary core reporting — a skill classic never taught you. (SFMC Tips #114)
• Window 3 — Marketing Performance Intelligence (renamed from "Marketing Performance" in Summer '26): a Tableau Next-powered suite with a Marketing Performance Dashboard (aggregate, by campaign/channel/flow/segment), Campaign Performance Dashboard, Content & Deliverability views. Installed from Setup; needs the Marketing Data Kit; consumes Data Cloud credits; dashboards are not customizable. (SFMC Tips #115)
• Window 4 — Unified Engagement History Dashboards (Spring '26): person-level engagement (opens, clicks, interactions) embedded on Lead / Contact / Person Account / Account record pages, keyed off the Unified Individual ID. (Turn On Unified Engagement History Dashboards)
• Attribution, native: Opportunity Influence attributes revenue to campaigns using Data 360 engagement — First Touch and Last Touch models, no campaign membership required, refreshed hourly, counting touches from 30 days before opportunity creation until Closed Won. Replaces (and can't coexist with) Customizable Campaign Influence. (Attribute Revenue to a Specific Campaign) · (The Agentic Marketer — Opportunity Influence)
• Attribution, multi-touch: lives in Marketing Intelligence — a separately licensed product on Data 360 + Tableau with Multi-Touch Attribution and Funnel-Based Attribution models, anchor campaigns, and AI campaign summaries. Not part of Growth/Advanced by default. (Marketing Intelligence in Marketing Cloud Next)
• Reuse & export: the same engagement DMOs feed Calculated Insights (e.g. opens per person, 30-day engagement score), segments on engagement data, ad-hoc inspection in Data Explorer, and CSV export from reports/dashboards — your tracking-extract replacement. (SFMC Tips #98)

---

🧩 Mnemonics & memory hooks

• The four windows spell C-R-M-U — "CRM + U (you)": Campaign Insights, Reports & Dashboards (Analytics tab), Marketing Performance Intelligence, Unified Engagement History. Aggregate → granular → fancy → per-person.
• The four analytics packages: M-S-L-F — "Marketers Send Lots of Flows": Marketing Engagement, SMS, Landing Pages & Forms, Flow Report analytics packages.
• Attribution ladder — "OMG, who gets the credit?": Opportunity Influence (native, first/last), Marketing Intelligence (add-on, multi-touch/funnel), Gone-era tooling (classic MC Intelligence/Datorama MTA app — different, dying product).
• Opportunity Influence rules of thumb — "2 models, 1 hour, 30 days": 2 models (first/last touch), refreshed every 1 hour, touchpoints counted from 30 days pre-opportunity.
• 730 = 2 years. Classic Engagement's retention story: engagement data retained/accessible for 730 days (policy effective June 16, 2025).
• "MPI ≠ MI ≠ MCI." Marketing Performance Intelligence (dashboards inside MC Next) ≠ Marketing Intelligence (attribution add-on on Data 360/Tableau) ≠ Marketing Cloud Intelligence (classic Datorama). Three near-identical names — interviewers will mix them up; you shouldn't.

---

🔁 Coming from classic Engagement

One-line reframe: you stop pulling tracking extracts out of a black box and start reporting on engagement DMOs like any other CRM data — with revenue attribution built in.

---

🛠️ In practice (what you would actually click)

A. Install the reporting stack (one-time admin, Growth/Advanced): 1. Setup → Quick Find "Marketing Cloud" → Analytics → install the four packages: Marketing Engagement Analytics, SMS Analytics, Landing Pages and Forms Analytics, Flow Report Analytics. (SFMC Tips #114) 2. Setup → Marketing Cloud → Marketing Features → Marketing Performance → install (the Marketing Data Kit is a required prerequisite; web-tracking integration optional). Assign users the Tableau Next Included App Business User permission set. Summer '26 added an install-progress tracker. (SFMC Tips #115)

B. Open campaign performance: 1. App Launcher → Marketing Cloud (the app) → Campaigns → open your campaign. 2. In the left-side menu, click Insights → the Campaign Performance Dashboard loads. 3. Filter by date range, flow, segment, channel (Email / SMS / WhatsApp); use the activity list and export for row-level opens/clicks. (Requires Marketing Performance installed; menu placement can shift by release.)

C. Find email metrics fast: 1. App Launcher → Analytics (or Reports/Dashboards tabs). 2. Search "Email Engagement Dashboard" (V2 = newer object model) or open reports like KPIs for Email Engagement / All Email Activities — sends, delivery rate, bounce rate, open rate, CTR, unsubscribe rate.

D. Build a simple engagement report yourself: 1. App Launcher → Reports → New Report. 2. In the report-type picker, search "Email Engagement" (types appear after package install; exact names vary V1/V2). 3. Group by Campaign Name, add Opens / Clicks / Bounces columns, filter to last 30 days → Save & Run → Export if needed.

E. Inspect raw engagement rows (your data-view muscle): 1. App Launcher → Data Cloud / Data 360 → Data Explorer. 2. Object type DMO → pick Email Engagement → filter by Individual ID / date. (Content fields like subject line generally aren't in the DMO — check the DLO MessagingEventsEmailV2 for more fields.) For reusable metrics, build a Calculated Insight (e.g. clicks per Unified Individual, 30 days) and use it in segments/personalization.

F. Turn on attribution: 1. Setup → Quick Find "Opportunity Influence" → enable (Growth/Advanced; blocked if Customizable Campaign Influence is in use). First data ≈ 1 hour, then hourly refresh; view influence on Opportunity/Campaign records and reports. (Help) 2. Setup → Quick Find "Unified Engagement" → Unified Engagement History Dashboards → turn on; assign View Unified Engagement History Dashboards perm set; add the component to Lead/Contact pages in Lightning App Builder (Spring '26). 3. For a flow: open the flow → Open Details (replaced the old View Report button, Spring '26) → element-level Tableau Next metrics.

---

🎤 Rapid-fire

1. Q: Where do email opens/clicks physically live in MC Next? A: In Data 360 — the MessagingEventsEmailV2 DLO mapped to the Email Engagement DMO (SMS/WhatsApp → Message Engagement DMO). …and in practice: Data Explorer → DMO → Email Engagement, filter by individual.

2. Q: Quickest way to see how a campaign performed? A: Open the campaign record → Insights → Campaign Performance Dashboard; filter by date/flow/segment/channel. …and in practice: it needs Marketing Performance installed first — no install, no Insights.

3. Q: What is Marketing Performance Intelligence and what powers it? A: The MC Next analytics suite (Marketing Performance + Campaign Performance dashboards, Deliverability tab since Summer '26), powered by Tableau Next, fed by the Marketing Data Kit, consuming Data Cloud credits. …and in practice: Setup → Marketing Features → Marketing Performance → install; dashboards are not customizable.

4. Q: Does MC Next have native attribution? A: Yes — Opportunity Influence: first-touch and last-touch models over Data 360 engagement, no campaign membership needed, hourly refresh, 30-day pre-opportunity window. …and in practice: Setup → Opportunity Influence → enable; incompatible with Customizable Campaign Influence.

5. Q: And multi-touch attribution? A: Not in Growth/Advanced natively — it's in the separately licensed Marketing Intelligence product (Multi-Touch + Funnel-Based Attribution on Data 360 + Tableau). …and in practice: if the org hasn't bought MI, your answer is first/last touch via Opportunity Influence.

6. Q: Classic data views vs MC Next — what replaced _Open and _Click? A: Engagement DMOs + Data Explorer for rows, Calculated Insights for aggregates, core reports for business users. …and in practice: the SQL you'd write against _Click becomes a Calculated Insight or an Email Engagement report grouped by campaign.

7. Q: What's the 730-day story? A: Classic Engagement's retention policy (effective June 16, 2025): engagement data retained/accessible for 730 days; older data inaccessible via UI/API and deleted at renewal for pre-Apr-2024 contracts. …and in practice: in MC Next, retention rides on your Data 360 contract/credits instead — different governance conversation.

8. Q: How do you get engagement data OUT of MC Next? A: Export from reports/dashboards (CSV), inspect via Data Explorer, build segments on engagement DMOs and activate, or query Data 360 programmatically. …and in practice: the Campaign Performance Dashboard's activity list has an export button — that's your tracking-extract stand-in.

9. Q: How do you measure a flow (journey)? A: Flow Performance (Spring '26): open the flow → Open Details → element-level execution and email-engagement metrics on Tableau Next screens. …and in practice: flow-version analytics were still rolling out at launch — check before promising them.

10. Q: A sales rep asks "what has this lead engaged with?" — where do they look? A: The Unified Engagement History Dashboard component on the Lead/Contact record (Spring '26), keyed on Unified Individual ID. …and in practice: enable in Setup, assign the viewer perm set, drop the component onto the record page in Lightning App Builder.

---

⚠️ Gotchas / currency notes

• Three products, one confusing family: Marketing Performance Intelligence (MC Next dashboards) vs Marketing Intelligence (attribution add-on) vs Marketing Cloud Intelligence (classic Datorama, whose Multi-Touch Attribution app needs the Granular Data Center — a totally different stack). Say the full name in interviews.
• Renames are live: "Marketing Performance" → Marketing Performance Intelligence (Summer '26); Data Cloud → Data 360 (Oct 2025). Docs show both names mid-migration.
• V1 vs V2 objects: email engagement moved from MessagingEventsEmail to MessagingEventsEmailV2 around Summer '25, and reports/dashboards exist in V1 and V2 flavors — build new work on V2.
• Opportunity Influence limits: only first/last touch (no native multi-touch), 30-day pre-opportunity attribution window, hourly (not real-time) refresh, and it cannot coexist with Customizable Campaign Influence.
• MPI dashboards aren't customizable and consume Data Cloud credits — an admin/cost conversation classic folks never had. Standard Analytics-tab reports are your customization outlet.
• Nothing works before installation. Fresh orgs show no engagement reports, no Insights menu, no Flow Performance — the analytics packages, Marketing Data Kit, and feature toggles must be installed/enabled first. In a demo interview, mention the install step: it signals real hands-on knowledge.
• Release velocity is high: Winter '26 added dashboard collections and objective-based summaries on the Marketing Analytics tab; Spring '26 added Flow Performance + Unified Engagement History; Summer '26 renamed MPI and added Deliverability. Preface UI claims with "as of the current release." (MarTech — Winter 2026 release)
• Classic contrast trap: if asked "where are send logs / tracking extracts?", the answer is they don't exist here — engagement DMOs + report exports + Data 360 queries replace them. Don't hunt for Automation Studio.

---

Summary: MC Next stores engagement in Data 360 DMOs (Email/Message Engagement) and surfaces it through four windows — campaign Insights, standard Reports & Dashboards, Tableau Next–powered Marketing Performance Intelligence, and per-person Unified Engagement History — with native first/last-touch revenue attribution via Opportunity Influence and multi-touch/funnel models in the separately licensed Marketing Intelligence add-on.

Sources

• Measure Success in Marketing Cloud Next — Salesforce Help
• Reporting in Marketing Cloud Next — Salesforce Help
• Attribute Revenue to a Specific Campaign (Opportunity Influence) — Salesforce Help
• Turn On Unified Engagement History Dashboards — Salesforce Help
• Marketing Intelligence in Marketing Cloud Next — Salesforce Help
• Email Engagement DMO — Salesforce Developers
• SFMC Tips #114: Standard Reports and Dashboards — Nobuyuki Watanabe
• SFMC Tips #115: Marketing Performance Intelligence — Nobuyuki Watanabe
• SFMC Tips #262: Flow Performance — Nobuyuki Watanabe
• SFMC Tips #97: How to Check Email Engagement Data — Nobuyuki Watanabe
• SFMC Tips #98: How to Utilize Email Engagement Data — Nobuyuki Watanabe
• SFMC Tips #108: Engagement Data Retention Policy 730 Days — Nobuyuki Watanabe
• Engagement Data Retention and Access Policy Is Changing — Salesforce Release Notes
• Opportunity Influence deep dive — The Agentic Marketer
• Winter 2026 Salesforce release heavy on Agentforce for marketers — MarTech

➡️ Next: N11_Admin_and_Setup.md

N11 — Admin & Setup: provisioning, permissions, environments

🎯 Why this matters: In classic Engagement you never touched "real" Salesforce Setup — provisioning meant Salesforce spinning up a stack, buying an SAP, and cloning Business Units. In Marketing Cloud Next you are the core-platform admin: the whole product is enabled, permissioned, domain-authenticated, sandboxed and deployed from ONE Salesforce org's Setup tree. Interviewers use admin questions to separate "watched a demo" candidates from "could stand up an org Monday morning" candidates. This module makes you the second kind.

---

🧠 One-screen mental model

Admin work in MC Next is a six-layer stack you build top to bottom, once, in order — the "Six P's":

        ═══════════ ONE SALESFORCE ORG (Enterprise/Unlimited + Growth or Advanced SKU) ═══════════
        one login · one Setup tree · NO separate stack · NO MIDs/Business Units · NO SAP purchase

  ┌─ 1. PROVISION ────────────────────────────────────────────────────────────────┐
  │  Data 360 (Data Cloud) license lands in the org (free 250k-credit tier exists)│
  │  gear ⚙ ▸ Data Cloud Setup ▸ Get Started  →  ~1 hr of auto-configuration      │
  └──────────────────────────────────┬────────────────────────────────────────────┘
                                     ▼
  ┌─ 2. PRODUCT ENABLE ───────────────────────────────────────────────────────────┐
  │  Setup ▸ Marketing Cloud ▸ Assistant Home / Basic Settings:                   │
  │  CRM connector → default email channel → pick DATA SPACE → Enable Marketing   │
  │  Cloud → install the 5 DATA KITS → Generate Identity Resolution ruleset       │
  └──────────────────────────────────┬────────────────────────────────────────────┘
                                     ▼
  ┌─ 3. PEOPLE ───────────────────────────────────────────────────────────────────┐
  │  Permission sets: Marketing Cloud Admin · Marketing Cloud Manager ·           │
  │  Data Cloud Architect (fka Data Cloud Admin, renamed Sep 2025)                │
  └──────────────────────────────────┬────────────────────────────────────────────┘
                                     ▼
  ┌─ 4. PLUMBING (channel) ───────────────────────────────────────────────────────┐
  │  Authenticated Domain: 8 CNAMEs (3 DKIM s1–s3 + 5 reply-mgmt) → Activate.     │
  │  DKIM then passes automatically. Company address · consent · Einstein toggles │
  └──────────────────────────────────┬────────────────────────────────────────────┘
                                     ▼
  ┌─ 5. PIPES (data) ─────────────────────────────────────────────────────────────┐
  │  Data 360 app ▸ Data Streams ▸ New → connectors (CRM, SFTP, web SDK,          │
  │  Ingestion API…) → DLO → map to DMO  (the N02 pipeline starts here)           │
  └──────────────────────────────────┬────────────────────────────────────────────┘
                                     ▼
  ┌─ 6. PROMOTE (environments) ───────────────────────────────────────────────────┐
  │  Sandboxes (Dev / Dev Pro / Partial / Full — GA since Winter '26) → build →   │
  │  CHANGE SETS to production (with exceptions) · credits burn → DIGITAL WALLET  │
  └───────────────────────────────────────────────────────────────────────────────┘

---

🔑 Core in 60 seconds

• Provisioning = a SKU on a core org, not a new stack. Growth/Advanced runs inside a Salesforce Enterprise or Unlimited org. Data 360 (Data Cloud) is a prerequisite — it must be licensed and set up first (a free 250k-credit Data 360 tier exists, e.g. via Salesforce Foundations). Both editions ship with Agentforce campaign creation built in; Advanced adds Einstein Engagement Scoring & Frequency, path optimization and Unified Conversations (2-way SMS/WhatsApp). List prices as of mid-2026: Growth ~$1,500/mo, Advanced ~$3,250/mo. (Salesforce Ben, The Spot)
• First-run flow is guided. Gear ⚙ → Data Cloud Setup → Get Started (~1 hr of automatic config), then Setup → Marketing Cloud → Assistant Home / Basic Settings walks you through: CRM connector, default email channel, select a data space, Enable Marketing Cloud, install data kits, generate an Identity Resolution ruleset. (Getting Started with MC Next Setup, SFMC Tips #151)
• Data kits = the product's own schema, delivered as packages. MC Next needs five deployed in Data 360: Sales, Marketing Setup Objects, Consent Objects, Flows Integration, Email Channel. No kits deployed = Marketing app half-works. (Configure your Org — dev guide, arthurbackouche.com)
• Users = Salesforce users + permission sets (no per-BU MC accounts). Core trio: Marketing Cloud Admin (Setup access + full control), Marketing Cloud Manager (campaigns/segments/non-admin flows, no Setup), Data Cloud Architect (all of Data 360 — renamed from Data Cloud Admin on Sep 4, 2025). Marketing-only humans can ride an Identity license. (Assign Permission Sets, Data 360 permission changes)
• Sending domain is self-service, and mandatory. You cannot send email without an activated authenticated domain: 8 required CNAME records (3 DKIM keys s1–s3 + 5 reply-mail-management hosts) + optional DMARC TXT. DKIM (2048-bit) then passes automatically. There is no SAP to buy and no delegated-subdomain option — self-hosted DNS only. (Authenticating MC Next Emails, Domains Setup & DNS Tips)
• Environments are REAL now. Since Winter '26, MC Next works in all four sandbox types (Developer, Developer Pro, Partial Copy, Full). Flows and Data Cloud config copy down; content/campaigns copy only in Full sandboxes; CRM person records never copy. Promote back with change sets (with exceptions). Classic Engagement never had this. (Test MC Next in a Sandbox, SFMC Tips #196)
• Limits are consumption-shaped. Active flows 500 (Growth) / 750 (Advanced); email credits 180k / 360k per year; SMS credits sold separately; scoring models 1 / 2; CMS storage 10 GB + 2 GB per user. Everything Data-360-side burns credits — watch them in Digital Wallet. (Allocations & Limits in MC Next, Digital Wallet)

---

🧩 Mnemonics & memory hooks

• The Six P's (setup order): Provision → Product-enable → People → Plumbing → Pipes → Promote. "Proper Preparation Prevents Painful Production Panics." Recite it and you can narrate an entire greenfield implementation in an interview.
• Data kits (5): S-M-C-F-E — Sales, Marketing setup, Consent, Flows integration, Email channel → "Smart Marketers Check Fine Email."
• The 8 CNAMEs: "3 keys + ABFRL." 3 DKIM selectors (s1, s2, s3) plus 5 reply-management hosts — Anonymous, Bounce, FBL, Reply, Leave → "A Big Friendly Rabbit Leaves."
• Permission trio = "A-M-A: Admin, Manager, Architect." Admin runs Setup, Manager runs campaigns, Architect runs the data. (Ask the interviewer which hat the role wears.)
• Sandbox copy rule: "Flows follow, content needs Full, people never come." Flows/config copy to any sandbox type; content & campaigns only to Full; CRM person records never copy.
• Credits mantra: "Nothing in Data 360 is free — check the Wallet." Identity rulesets, streams, segments, even sandboxes meter credits.

---

🔁 Coming from classic Engagement — the admin translation table

---

🛠️ In practice (what you would actually click)

Assumes a fresh Enterprise/Unlimited org with the Growth or Advanced SKU on the contract. Labels below reflect mid-2026 UI; Setup nodes still mostly say "Data Cloud" even though the product was renamed Data 360 (Oct 2025) — expect both names on screen.

1. Turn on Data 360 (Data Cloud) — Layer "Provision" 1. Log in → click the gear ⚙ (top right) → Data Cloud Setup (some orgs: Data 360 Setup). 2. Scroll down → click Get Started. Provisioning is one click and runs automatically (~1 hour). 3. Come back later and confirm the setup page shows components as configured.

2. Enable Marketing Cloud — Layer "Product enable" 1. Setup → Quick Find: "Marketing Cloud" → Assistant Home (a.k.a. Basic Settings). This wizard tracks required vs recommended tasks. 2. Let the auto-tasks finish: Salesforce CRM Connector, default email channel, data protection details. 3. Select a Data Space (usually default). If the dropdown is greyed out, you're missing the Marketing Cloud Admin permission set — fix that first. 4. Marketing Cloud auto-enables once the data space is chosen. 5. Still in Basic Settings, scroll to the data-kit card → click Update/Install and wait (~30 min; retries are normal) until all five data kits (Sales, Marketing Setup Objects, Consent, Flows Integration, Email Channel) show Deployed. 6. Scroll to Identity Resolution → Generate Ruleset → refresh after ~5 min → status Success. (To run it manually: App Launcher → Data Cloud/Data 360 → Identity Resolutions → Individual → Run Ruleset.)

3. Assign permissions — Layer "People" 1. Single user: Setup → Quick Find: "Users" → Users → pick the user → Permission Set Assignments → Edit Assignments → add → Save. 2. Bulk: Setup → Quick Find: "Permission Sets" → pick a set → Manage Assignments → Add Assignments. 3. Who gets what: implementation lead → Marketing Cloud Admin + Data Cloud Architect; campaign marketers → Marketing Cloud Manager; analytics viewers → Tableau Next Included App Business User (dashboards). Users without a CRM license can be created on an Identity license with the marketing permission sets.

4. Authenticate the sending domain — Layer "Plumbing" (email is blocked until this is done) 1. Setup → Marketing Cloud → Channels → Email → Go to Authenticated Domains. 2. Click + Add Domain → enter a dedicated subdomain (e.g. mktg.yourbrand.com) not used by any other sender (keep it separate from your classic Engagement SAP domain). 3. The wizard lists 8 CNAME records (3 DKIM: s1/s2/s3 + 5 reply-management: anonymous, bounce, fbl, reply, leave) and an optional DMARC TXT. Hand them to whoever owns DNS; propagation can take 24+ hours. 4. Back in the wizard: tick the confirmation box → Activate My Domain → enter a notification email. Activation typically ~1 hour → status shows Active. 5. While in Channels → Email: Go to Company Information → Edit → enter the physical mailing address (CAN-SPAM), and review consent settings. 6. ⚠️ Once created, an authenticated domain cannot be deleted — name it carefully.

5. Connect data streams — Layer "Pipes" 1. Connector credentials/config live in Data Cloud Setup → Connectors (e.g. more CRM orgs, S3, SFTP, web SDK, Ingestion API). 2. App Launcher (⋮⋮⋮) → "Data Cloud" (or Data 360) → Data Streams tab → New. 3. Pick source → objects/bundles → batch vs streaming → deploy. The MC Next data kits already deployed starter streams for CRM contacts/leads; add SFTP/web/API streams the same way. (Full pipeline mechanics: module N02/N03.)

6. Enable AI — Einstein & Agentforce 1. Setup → Quick Find: "Einstein Setup" → Turn on Einstein (generative AI master switch). Refresh the browser. 2. Setup → Agentforce Agents → enable Agentforce — this powers Agentforce campaign creation (brief → campaign → drafted emails/SMS), included in both Growth and Advanced. 3. Optional per-channel toggles under Marketing Cloud → Channels → Email: Einstein Send Time Optimization, Einstein Metrics Guard. (Engagement Scoring / Frequency models: Advanced edition only.)

7. Environments & change management — Layer "Promote" 1. Create: Setup → Quick Find: "Sandboxes" → New Sandbox → pick type (Developer / Dev Pro / Partial Copy / Full). GA for MC Next since Winter '26. 2. In the sandbox, re-enable in order: Data Cloud → CRM connector → Setup → Marketing Cloud Setup → Enable Marketing Cloud. 3. Know the copy matrix: flows + Data Cloud config (identity rules, calculated insights, data graphs) copy to all types; content, campaigns, subscriptions copy in Full only; CRM person records never copy (segments show 0 — create sample records). 4. Promote: Setup → Outbound Change Sets (sandbox) → add flows/content → upload → Inbound Change Sets (prod) → validate → deploy. Cannot deploy: campaigns, communication subscriptions, expression content, tracked-link content — rebuild those in prod. 5. Spring '26 safeguard: Full/Partial sandboxes auto-discard outbound email; allow up to 5 domains via the sandbox allowlist if you need real test sends.

8. Watch the meters 1. App Launcher → "Your Account" / search "Digital Wallet" or "Consumption Cards" → view Data 360 credit burn by resource type (streams, unification, segments, queries). Needs the View Consumption Cards permission. 2. Turn on the consumption alert flow template (e.g. email at 80% of allowance). 3. Marketing limits table: Setup → Marketing Cloud help link "Allocations and Limits" — key numbers below.

---

🎤 Rapid-fire

1. Q: What has to be true before Marketing Cloud can even be enabled in the org? A: Data 360 (Data Cloud) must be provisioned and set up, the CRM connector created, and a data space selected — Marketing Cloud auto-enables after data-space selection. …and in practice: gear ⚙ → Data Cloud Setup → Get Started (~1 hr), then Setup → Marketing Cloud → Basic Settings.

2. Q: Which permission sets cover a day-one marketing team? A: Marketing Cloud Admin (Setup + full control), Marketing Cloud Manager (campaigns/segments/non-admin flows), Data Cloud Architect (all of Data 360; renamed from Data Cloud Admin, Sep 2025). …and in practice: Setup → Permission Sets → Manage Assignments → Add Assignments.

3. Q: How does sending-domain setup differ from classic's SAP? A: No SAP purchase, no dedicated-IP SKU, no delegated subdomain — it's self-service: add a subdomain, publish 8 CNAMEs (3 DKIM + 5 reply-management), activate; DKIM (2048-bit) then passes automatically. …and in practice: Setup → Marketing Cloud → Channels → Email → Go to Authenticated Domains → + Add Domain → Activate My Domain.

4. Q: Can you send email before the domain is active? A: No — an activated authenticated domain is required for any email send in MC Next. …and in practice: if sends are blocked in a new org, check Authenticated Domains status = Active and the company address is filled in.

5. Q: What's the sandbox story? A: GA since Winter '26, all four core types. Flows + Data Cloud config copy everywhere; content/campaigns need a Full sandbox; CRM person records never copy; sandbox usage still burns credits. …and in practice: Setup → Sandboxes → New Sandbox, then re-enable Data Cloud + Marketing Cloud inside it.

6. Q: How do you promote work from sandbox to production? A: Change sets carry flows and most content; campaigns, communication subscriptions, expression content and tracked-link content don't deploy — rebuild them. Data 360 metadata travels via data kits. …and in practice: sandbox Outbound Change Set → upload → prod Inbound Change Set → validate → deploy.

7. Q: What replaced Business Units? A: Nothing 1-for-1. Separation = one org + data spaces (data partitioning) + permission sets (access) — there is no per-BU sending hierarchy. …and in practice: the data space is picked once in Basic Settings; brand/regional separation is a design decision, not a MID.

8. Q: An exec asks "are we going to blow through our credits?" — where do you look? A: Digital Wallet — near-real-time Data 360 consumption cards by resource type, plus threshold alert flows (e.g. notify at 80%). …and in practice: App Launcher → Your Account / Digital Wallet → Consumption Cards; enable the alert flow template.

9. Q: What are data kits and why does an MC Next admin care? A: Installable packages of Data 360 metadata (streams, objects, mappings). MC Next itself ships as five kits that must all deploy or the app misbehaves. …and in practice: Setup → Marketing Cloud → Basic Settings → data-kit card → Update/Install, retry until all five show Deployed.

10. Q: Name two hard org limits you'd design around. A: Active flows: 500 Growth / 750 Advanced, and email credits: 180k / 360k per year (SMS separate). …and in practice: archive dead flows and check Allocations & Limits before promising campaign volumes.

---

⚠️ Gotchas / currency notes

• Naming drift on the tin. Product renamed Data Cloud → Data 360 (Oct 2025), but Setup nodes, permission sets and docs still say "Data Cloud" in many places in mid-2026. Say either in interviews, but show you know both.
• Permission-set churn is real. Data Cloud Admin → Data Cloud Architect (Sep 4, 2025); the old Data Cloud Marketing Admin/Manager/Specialist sets are Legacy/deprecated, replaced by Activation Manager/Specialist. Don't quote the pre-2025 names as current.
• A greyed-out data space dropdown = missing permission set. Classic head-scratcher in Basic Settings; assign Marketing Cloud Admin and reload.
• Setup tasks are flaky by design tolerance. Data-kit installs and data-stream deploys commonly need retries (30-min waits are normal). That's expected behavior, not a broken org.
• Authenticated domains are forever. They can't be deleted once created; and Salesforce recommends a unique subdomain per platform — don't reuse your classic SAP domain (reputation cross-contamination + conflicting DNS).
• Sandboxes cost money too. They consume Data 360/messaging credits (metered at a reduced rate per current docs), and since Spring '26 Full/Partial sandboxes auto-discard outbound email unless a domain is on the 5-slot allowlist — don't debug "missing sends" for an hour.
• Change sets ≠ full coverage. Campaigns, communication subscriptions, expression content and tracked-link content won't deploy; some flow/content deployments still fail with rebuild-it workarounds. ALM here is younger than core Salesforce ALM — verify per release before promising a client a clean pipeline.
• Identity Resolution burns credits. Guidance remains one active ruleset per object; casually regenerating rulesets = surprise Wallet drain.
• Classic trap: don't say "we'll test in a lower BU" or "we need an SAP" in an MC Next interview — the answers are sandbox + change sets and self-service authenticated domain. Those two swaps alone signal you've made the jump.
• Currency check (July 2026): sandbox GA Winter '26; sandbox email safeguard Spring '26; edition prices (Growth $1,500/mo, Advanced $3,250/mo) as of April 2026 — all likely to move; re-verify at interview time.

---

Summary: MC Next admin = core Salesforce admin with a marketing hat — Provision Data 360 (one click, ~1 hr), Product-enable Marketing Cloud (data space + five data kits + identity ruleset), People (Admin/Manager/Architect permission sets), Plumbing (mandatory 8-CNAME authenticated domain, auto-DKIM), Pipes (data streams), Promote (real sandboxes since Winter '26 + change sets, credits watched in Digital Wallet) — with no BUs, no SAP and no separate stack anywhere.

Sources - Getting Started with Marketing Cloud Next Setup — Salesforce Help - Assign Permission Sets for Marketing Cloud Next — Salesforce Help - User Permissions in Marketing Cloud Next — Salesforce Help - Data 360 License, Credits, and Permission Set Changes (Sep–Nov 2025) — Salesforce Help - Authenticating Marketing Cloud Next Emails — Salesforce Help - Email Authenticated Domains Setup and DNS Tips — Salesforce Help - Test Marketing Cloud Next in a Sandbox — Salesforce Help - Allocations and Limits in Marketing Cloud Next — Salesforce Help - Enable AI Features in Marketing Cloud Next — Salesforce Help - Monitor Usage in Digital Wallet — Salesforce Help - Configure your Org — Marketing Cloud Next developer guide - Marketing Cloud Growth vs. Advanced — Salesforce Ben - Getting Started with MC Growth & Advanced — The Spot - SFMC Tips #151: MC Next Setup Steps — Nobuyuki Watanabe - SFMC Tips #140: MC Next Email Domain Authentication — Nobuyuki Watanabe - SFMC Tips #196: MC Next Testing with Sandbox — Nobuyuki Watanabe - SFMC Tips #246: Sandbox Email Sending Safeguard — Nobuyuki Watanabe - How to set up Marketing Cloud Next — arthurbackouche.com - Track Data Cloud Usage in Digital Wallet — Salesforce Admins blog

➡️ Next: N12_Skills_Bridge_from_Classic.md

N07 — Skills Bridge: Classic → MC Next

🎯 Why this matters: After four years of AMPscript, SSJS, Data Extensions, SQL Query Activities, Journey Builder, and Automation Studio at GAP, the scariest thing about Marketing Cloud Next (Marketing Cloud Growth / Advanced on Core) is the fear that none of it counts. It does. The concepts are almost all the same — audience, personalization, orchestration, sending, reporting — the tools and vocabulary changed. This module is the Rosetta Stone: for every classic skill you own, it tells you (1) what transfers 1:1, (2) what's genuinely new to learn, and (3) a one-line "how to say it in an interview." Learn this and your classic experience becomes your biggest asset in the room, not a liability.

---

🧠 One-screen mental model

Same five jobs, new toolbox. Everything you did in classic still needs doing in MC Next — it just moves onto Data Cloud (Data 360) + Salesforce Core. Here is the full map.

---

🔑 Core in 60 seconds

• The jobs are identical; the platform moved to Data Cloud + Core. Audience, personalization, orchestration, sending, and reporting all still exist — they just run on Data 360 (Data Cloud) and Salesforce Flow instead of Email Studio / Automation Studio / Journey Builder. (Mavlers)
• Data Extension → DLO then DMO. Your raw table lands as a Data Lake Object, then gets mapped to a Data Model Object (e.g., Individual, Contact Point) so it joins into the shared model. Since Aug 12, 2025, connecting MCE data into Data Cloud is free. (Salesforce Developers — DMO Mapping Guide)
• Your SQL doesn't die — it splits. Aggregations/metrics (LTV, RFM, counts) become Calculated Insights (ANSI SQL or a visual builder); audience WHERE-logic becomes a Segment. (Salesforce Help — SQL Rules for Insights, Trailhead)
• Dedup becomes configuration. Your ROW_NUMBER() dedup pattern is replaced by Identity Resolution rulesets that reconcile duplicates into a single Unified Individual — avoiding duplicate sends by design. (Salesforce Geek, Salesforce Help — Identity Resolution for MC Next)
• AMPscript is back — as a subset. Handlebars (Spring '26) is the native templating language; AMPscript support arrived Summer '26 with ~30% of functions available (many utility/math/date/output; missing much of the DE/CloudPages/HTTP/file world). Internally AMPscript is even converted to Handlebars. (MarketingCloudTips — AMPscript has arrived, Concret.io, The Agentic Marketer — Handlebars)
• Content Builder → Content tab on Salesforce CMS; Dynamic Content → Personalization Points. Personalization Points are reusable containers of Variations + Decisions (up to 25 per email, up to 15 variations/decisions each), built on a Data Graph over the Unified Individual. (Salesforce Help — Content Personalization, MarketingCloudTips — Dynamic Content)
• Journey Builder → Flow; Automation Studio → Flow + Data Cloud. Orchestration is Salesforce Flow (segment-, event-, record-, schedule-triggered); the SQL/import/schedule jobs of Automation Studio move to scheduled Flows and Data Cloud transforms/CIs. (The Agentic Marketer — 8 Flow Types)
• Reporting moves to the unified model. Data Views become Engagement DMOs (Email Engagement, Message Engagement, Website Engagement, Flow Run) reportable via standard reports and CRM Analytics / Tableau Next, plus Data Cloud Profile Engagement on the individual record. (MarketingCloudTips — CRM Analytics Lenses, Salesforce Help — Reporting in MC Next)

---

🧩 Mnemonics & memory hooks

• "DE grows up twice: DLO then DMO." Raw lands as a Data Lake Object, then gets modeled into a Data Model Object. (Lake = raw water; Model = plumbed in.)
• "SQL splits: Segment + Insight." Audience logic → Segment; math/metrics → Calculated Insight. If it had a WHERE → Segment; if it had GROUP BY/aggregates → CI.
• "Dedup goes from code to config." ROW_NUMBER() → Identity Resolution ruleset → one Unified Individual.
• "Handlebars first, AMPscript 30%." Native language is Handlebars; your AMPscript is a limited subset — always verify the function exists before you rely on it.
• "Points, not blocks." Dynamic Content blocks → Personalization Points (25 max, 15 variations each).
• "One canvas, one truth." Journey Builder canvas → Flow canvas; All Subscribers → Unified Individual truth.
• "Data Views become DMOs you can report on." Tracking data survives as Engagement DMOs in Data Cloud, queryable with CRM Analytics.
• Master mnemonic — "A-P-O-S-R": Audience (Segment/CI), Personalization (Handlebars/Points), Orchestration (Flow), Sending (config/consent), Reporting (Engagement DMOs). Same five jobs you already do — memorize the five buckets and every mapping hangs off one of them.

---

💪 What transfers vs what's new

Transfers almost 1:1 (lean on these hard): - SQL fluency — Calculated Insights use ANSI SQL; your JOIN/CASE/aggregate skills apply directly. - Set-based audience thinking — WHERE-clause / filter logic maps straight onto the Segment builder. - Personalization instinct — merge fields, conditional content, fallback/default values: same idea in Handlebars and Personalization Points. - Journey/orchestration design — entry → wait → decision → send is the same shape in Flow. - Data modeling & relationships — sendable DE + relationships ≈ DMOs + Data Graph relationships. - Deliverability & compliance concepts — from-identity, CAN-SPAM, consent/subscriptions still matter; only the config surface changed. - Debugging discipline — QA-ing personalization, previews, test sends, and edge cases is identical work.

Genuinely new (budget study time here): - Identity Resolution — dedup as ruleset configuration, not a query you author. - DLO → DMO mapping & the canonical data model — understanding standard DMOs (Individual, Contact Point, Party Identification) and mapping to them. - Data Graphs — the pre-joined structure personalization and Flow decisions read from (nothing works without the right graph). - Handlebars syntax + AMPscript's missing 70% — knowing which classic functions are gone is as important as the ones that stay. - Salesforce Flow as the automation engine — Core Flow concepts, elements, resources, sub-flows, and platform limits. - Consumption/credit economics — Data Cloud segmentation burns credits; batch-vs-real-time is now a cost decision, not just a design one. - Salesforce CMS — workspaces/folders content model instead of Content Builder. - CRM Analytics / Tableau Next reporting — analytics moves off Data Views into the Data Cloud + analytics stack.

---

🎤 Rapid-fire

1. Q: You've never used Data Cloud. How does your SFMC experience apply to MC Next? A: "The five jobs are identical — audience, personalization, orchestration, sending, reporting. My Data Extensions become DMOs, my SQL Query Activities become Calculated Insights and Segments, my Journey Builder work becomes Salesforce Flow. I'm re-tooling, not re-learning the discipline."

2. Q: What happens to your SQL skills in MC Next? A: "They get more useful. Calculated Insights run on ANSI SQL, so my JOINs, CASE statements, and aggregations transfer directly — the difference is they now build reusable metrics on a unified model instead of writing rows into a Data Extension."

3. Q: How would you handle dedup, which you used to do with ROW_NUMBER()? A: "In MC Next that's not my query to write — it's Identity Resolution. I configure match-and-reconcile rules that collapse duplicate records into one Unified Individual, which prevents duplicate sends by design. My old dedup logic tells me exactly what rules to configure."

4. Q: Is your AMPscript knowledge worthless now? A: "No — as of Summer '26 AMPscript is supported as roughly a 30% subset, and Handlebars is the native language. My personalization logic transfers; my job is to know which functions survived and which moved into Flow or the data model. Interestingly, AMPscript is converted to Handlebars under the hood."

5. Q: There's no Journey Builder. Can you still build journeys? A: "Yes — journeys are now Salesforce Flows, usually segment-triggered from a Data Cloud segment. Entry, waits, decisions, and sends are the same shapes I built in Journey Builder; it's a different engine on the Core platform, and it can now touch CRM records mid-flow, which classic JB couldn't."

6. Q: What replaces Automation Studio for you? A: "It splits. Orchestration and scheduling go to Flow — schedule-, event-, and record-triggered types. The data heavy-lifting — the SQL, transforms, and aggregations — goes to Data Cloud as Calculated Insights and data transforms."

7. Q: How do you personalize content without Dynamic Content blocks? A: "Personalization Points — reusable containers of Variations and Decisions, up to 25 per email. Same rule-based content-swapping I did with Dynamic Content, now reading from a Data Graph over the Unified Individual, with Handlebars/AMPscript and Einstein generative for the copy."

8. Q: Where did Data Views and your tracking reports go? A: "Into the unified model as Engagement DMOs — Email, Message, and Website Engagement — which I report on with standard reports and CRM Analytics / Tableau Next, plus Profile Engagement right on the individual's record. Same tracking data, now queryable across the whole customer profile."

9. Q: What's the single biggest new thing you have to learn? A: "The Data Cloud data model — DLO-to-DMO mapping, Identity Resolution, and Data Graphs. Once data is modeled and resolved correctly, everything downstream — segments, personalization, Flow decisions — is work I already know how to do."

---

🗣️ Your 60-second pitch

"I've spent four years as an email developer at GAP living inside Marketing Cloud — AMPscript, SSJS, Data Extensions, SQL Query Activities, Journey Builder, and Automation Studio. When I look at Marketing Cloud Next, I don't see a platform I have to learn from scratch — I see the same five jobs I do every day wearing new names. My Data Extensions are DMOs. My SQL Query Activities are Calculated Insights and Segments — and Calculated Insights run on ANSI SQL, so that skill transfers directly. My ROW_NUMBER() dedup becomes Identity Resolution rulesets. My AMPscript personalization is now Handlebars plus a supported AMPscript subset. My Journey Builder canvases become Salesforce Flows, and Automation Studio splits between Flow and Data Cloud. What's genuinely new for me is the Data Cloud layer — DLO-to-DMO mapping, Identity Resolution, and Data Graphs — and I'm already studying it, because I know that once the data is modeled correctly, everything downstream is work I've done thousands of times. So I bring day-one production instincts on deliverability, personalization QA, and journey design, plus the SQL depth Data Cloud rewards. I'm not a classic developer who's behind — I'm a classic developer with a head start."

---

➡️ Next: N13_Hands_On_Lab_Path.md

N13 — Hands-On Lab Path (free orgs, Trailhead, exercises zero→hero)

🎯 Why this matters: Your known gap is not concepts — it's "what would you actually click." Nobody will pay you to learn MC Next; you have to manufacture hands-on experience for free, and in July 2026 that is genuinely possible: the new Developer Edition ships with Agentforce + Data 360 built in, and Trailhead now spins up badge-specific Marketing Cloud Next playgrounds. This module is the map of every free environment, what each one can and cannot do, and a 12-lab ladder that takes you from "created a custom object" to "flow-orchestrated campaign send." Walk into interviews saying "I built it in my dev org" instead of "I read about it."

---

🧠 One-screen mental model

Five environments, stacked from "always free" to "the actual paid product." Your home base is the persistent Developer Edition; everything else is a satellite you spin up per lab.

                       THE FREE-ORG LADDER  (July 2026)
 ─────────────────────────────────────────────────────────────────────────────
  RUNG 5  💰 PAID  Marketing Cloud Growth / Advanced org  ← the job itself
          (or Foundations features inside an employer's Enterprise+ org)
 ─────────────────────────────────────────────────────────────────────────────
  RUNG 4  🔒 PARTNER-GATED  SDO demo org with MC Growth
          Partner Learning Camp → Demo Org tab  (needs partner-company login)
 ─────────────────────────────────────────────────────────────────────────────
  RUNG 3  ⏱️ BADGE-SPECIFIC CUSTOM PLAYGROUNDS  (short-lived, pre-loaded)
          ├── Data Cloud playground  → streams, mapping, insights, segments
          └── MC NEXT playground     → ≈Advanced features, ~3 days/instance,
                                        NO real email delivery
 ─────────────────────────────────────────────────────────────────────────────
  RUNG 2  🏠 HOME BASE — Developer Edition w/ Agentforce + Data 360
          developer.salesforce.com/signup · never expires if used every 45 days
          Data Cloud: 1 data space, 10 GB · Agentforce: 150 LLM outputs/hr
 ─────────────────────────────────────────────────────────────────────────────
  RUNG 1  🆓 STANDARD TRAILHEAD PLAYGROUND  (avatar → Hands-On Orgs)
          Core platform: objects, apps, FLOW BUILDER — no Data Cloud
 ─────────────────────────────────────────────────────────────────────────────
          ★ Flow Builder works on EVERY rung — practice journeys anywhere ★

---

🔑 Core in 60 seconds

• Home base = the new Developer Edition. Since TDX '25 the free DE at developer.salesforce.com/signup includes Agentforce and Data Cloud/Data 360 and doesn't expire as long as you log in every 45 days. Limits: 1 data space, 10 GB of Data Cloud data, 150 LLM generation requests/hour. Since April 2026 it also bundles Agentforce Vibes IDE + hosted MCP servers (capped). (Dev blog 2025, Help, Apex Hours)
• Standard Trailhead Playgrounds = Core only. Objects, apps, reports, and — crucially — Flow Builder work in every playground. Data Cloud is NOT in a standard playground; Data Cloud badges provision a custom, badge-specific playground with sample data that "may not work for other badges." (Trailhead — custom Data Cloud playground)
• A free MC Next playground now exists (≈May 2026). Specific MC Next hands-on badges (e.g., email-sending essentials, segment creation/activation) spin up a playground functionally like Advanced edition — but no real email delivery and roughly a 3-day life per instance. Treat it as a timed lab bench, not a home. (SFMC Tips #301)
• There is NO general Marketing Cloud free trial. Salesforce Help states it plainly. Don't hunt for one; use DE + playgrounds + (if applicable) partner SDO. (Help — no MC free trials)
• Partner shortcut: employees of Salesforce partner companies request an SDO demo org with Marketing Cloud Growth via Partner Learning Camp → Demo Org tab (time-limited, renewable). (DYDC, SFMC Tips #151)
• Employer shortcut: any Sales/Service Cloud Enterprise+ org can switch on Salesforce Foundations free — 2,000 email sends/month, 10,000 Data Cloud segmentation/activation credits, Agentforce starter credits. Useful if a future employer "doesn't have Marketing Cloud." (Salesforce Foundations, Salesforce Ben)
• Curated learning: the Meet Agentforce Marketing trail (5 modules, ~1h20m, conceptual), the 3-level Data 360 Learning Journey, the Data 360: Explore Setup to Activation trail, and the hands-on Superbadge: Data Stream Fundamentals (+ Data Quality and Validation superbadge). (Trail, Journey, Superbadge)

---

🧩 Mnemonics & memory hooks

• The 5 free environments — "Poor Devs Can Still Fly": Playground (standard), Developer Edition (home base), Custom playgrounds (Data Cloud / MC Next), SDO (partner), Foundations (employer's Enterprise org).
• The lab ladder phases — "Clicks Drive Actual Ability": Core (L1–L4) → Data (L5–L8) → Audience & journeys (L9–L11) → AI (L12).
• "45 or die." The DE terminates after 45 days of no logins. Calendar a fortnightly login.
• "3-day sprint org." The MC Next playground is a hotel room, not a house — check in with a lab plan already written.
• "Flow is free everywhere." The one MC Next muscle you can train in literally any org, today, unlimited: Flow Builder.
• DE vs playground in one line: DE = your permanent gym; playgrounds = rented courts for specific matches (badges).

---

🛠️ In practice (what you would actually click)

A. Stand up your permanent home base (do this today)

1. Go to developer.salesforce.com/signup → fill the form → verify email → set password. This is the new DE with Agentforce + Data 360 baked in. (source)
2. Enable Data Cloud: Setup ⚙️ → Quick Find "Data Cloud" → Data Cloud Setup → Get Started. Provisioning can take minutes to a few hours — start it, walk away. (Docs may say "Data 360" post-rename; same screen.)
3. Turn on AI: Setup → Quick Find "Einstein Setup" → toggle Einstein on (refresh), then Setup → Quick Find "Agentforce" → Agentforce Agents → enable. The Help doc's required order: Data Cloud → Einstein generative AI → Agentforce. (Help)
4. Bookmark App Launcher (⋮⋮ grid, top-left) → "Data Cloud" — your Streams / Mapping / Identity / Insights / Segments tabs live in that app.

B. Spin up satellite orgs per lab

5. Standard playground: trailhead.salesforce.com → your avatar → Hands-On Orgs → Create Playground. Use for Core/Flow labs if you'd rather not clutter the DE.
6. Custom Data Cloud playground: open a hands-on Data Cloud badge (e.g., Data Cloud in Flows setup unit) → in the challenge box at the bottom, click the org picker → Create Playground — it arrives pre-loaded with data bundles. It only works for that badge. (Trailhead)
7. MC Next playground: search Trailhead for current "Marketing Cloud Next" hands-on badges (as of mid-2026: email sending essentials, segment creation & activation) and launch the playground from the challenge box. Expect ~3 days of life, no real sends; badge names shift by release — search fresh. (SFMC Tips #301)
8. Partner SDO (only if you join a partner company): log in at partners.salesforce.com → Partner Learning Camp → Demo Org tab → request the Marketing Cloud Growth SDO; follow the MC Growth setup guide it links. (DYDC)

C. THE LAB LADDER — 12 exercises, zero→hero

Legend: 🆓 = fully free today · ⏱️ = free but in a short-lived playground · 🔒 = needs paid/partner org (fallback given).

— Phase 1: Core platform (he's never touched Core — fix that first) —

L1 · Create a custom object + record 🆓 — DE or any playground - Goal: Prove you can model data on Core (the "DE-but-not-a-DE" moment). - Steps: Setup ⚙️ → Object Manager → Create → Custom Object Workshop_Signup → add fields (Email, Status picklist, Signup_Date) → App Launcher → open the object's tab → New record. - You can now say: "I've built custom objects with fields and records on the Core platform."

L2 · Build an app + import data 🆓 — same org - Goal: Navigate like a Core admin: apps, list views, wizard imports. - Steps: Setup → App Manager → New Lightning App → add your object's tab → then Setup → Data Import Wizard → load a 20-row CSV of signups → fix a list view with filters. - You can now say: "I've imported CSV data with the Data Import Wizard and built Lightning apps and list views."

L3 · Record-triggered Flow 🆓 — any org (Flow is free everywhere) - Goal: Your first "journey" — the MC Next orchestration engine is Flow. - Steps: Setup → Quick Find "Flows" → New Flow → Start from Scratch → Record-Triggered Flow → object Workshop_Signup, trigger = created → Decision on Status → Update Records + Action → Send Email Alert to yourself → Save → Activate → create a record and watch it fire. - You can now say: "I've built and activated record-triggered flows with decisions and email actions."

L4 · Scheduled flow + loop + debug 🆓 — any org - Goal: The Automation Studio replacement muscle: scheduled batch logic. - Steps: Flow Builder → Schedule-Triggered Flow (daily) → Get Records (all signups where Status = Pending) → Loop → Assignment → Update Records → use Debug to step through before activating. - You can now say: "I've replaced an Automation Studio mental model with scheduled flows, and I debug flows before activating."

— Phase 2: Data 360 (the DE unlocks all of this) —

L5 · Provision Data Cloud + first data stream 🆓 — your DE - Goal: Ingest something. Zero external infra: use your own org's CRM data. - Steps: (after A2 provisioning) App Launcher → Data Cloud → Data Streams tab → New → Salesforce CRM → pick the Contact bundle → deploy → watch the DLO appear. (CSV via SFTP/S3/Ingestion API needs external infra — the CRM connector is the free-instant path; Trailhead custom playgrounds ship pre-built data bundles as the CSV-style alternative.) - You can now say: "I've configured a Data Cloud data stream and inspected the resulting DLO."

L6 · Map DLO → DMO 🆓 — your DE - Goal: Touch the canonical model with your hands. - Steps: Data Streams → your Contact stream → review the auto-mapping (starter bundles pre-map to Individual / Contact Point Email) → open Data Lake Objects tab → add one manual field mapping yourself so you've done it, not just seen it. - You can now say: "I've mapped DLO fields onto the Customer 360 data model — Individual and Contact Point Email DMOs."

L7 · Identity resolution ruleset 🆓 — your DE - Goal: Manufacture a Unified Individual. - Steps: Add 2–3 Contacts that are obviously the same human (same email, name variants) → Data Cloud → Identity Resolutions tab → New → object = Individual → match rule preset (e.g., Fuzzy Name & Normalized Email) → default reconciliation rules → Save → publish/run → after the run, check the Unified Individual count merged them. - You can now say: "I've published an identity resolution ruleset and verified records merged into one Unified Individual." (In prod, note rulesets burn credits — one active ruleset per object.)

L8 · Calculated Insight 🆓 — your DE (or the Data Cloud playground) - Goal: Replace your SQL-Query-Activity instinct with a reusable metric. - Steps: Data Cloud → Calculated Insights → New → use the builder (or SQL) → e.g., count of cases (or signups) per Individual, keeping the Individual ID as a dimension → save → publish. The canonical Trailhead version is the "Number of Abandoned Carts" CI. (Trailhead) - You can now say: "I've built and published a Calculated Insight and made it segment-ready by including the primary key as a dimension."

— Phase 3: Audiences & journeys —

L9 · Build + publish a segment 🆓 — your DE (Data Cloud app) or MC Next playground - Goal: The audience-building core skill. - Steps: Data Cloud → Segments → New → Segment On: Unified Individual (default data space) → drag attributes / your L8 insight into the rule canvas → set publish schedule (Standard vs Rapid) → Save → Publish → check member count. - You can now say: "I've built and published segments on Unified Individual, including Calculated Insight filters."

L10 · Superbadge: Data Stream Fundamentals 🆓⏱️ — its own custom playground - Goal: A public, verifiable, requirements-only proof (no step-by-step) — closest thing to work experience on your Trailhead profile. - Steps: Open the superbadge unit → provision its playground → meet the business requirements: connect the data bundle stream, add a formula field, extend the DMO mapping. Follow with the Data Quality and Validation superbadge unit. - You can now say: "I hold the Data Stream Fundamentals superbadge — assessed hands-on, not multiple choice." (Superbadge)

L11 · Flow-orchestrated campaign send ⏱️/🔒 — MC Next playground (build) · paid/SDO org (real delivery) - Goal: The end-to-end money shot: segment → marketing flow → email send. - Steps: In the MC Next playground: create a Campaign → build the email in the content editor → Flow Builder → Segment-Triggered Flow → start = your L9-style segment → add Send Email Message element → wait + decision → Activate. - Reality check: the free playground cannot actually deliver email and dies in ~3 days — you can build and activate, not receive. Fallback: rebuild the same shape in your DE as a record-triggered flow + Email Alert to yourself (L3/L4); real delivery needs a paid Growth/Advanced org, a partner SDO, or a Foundations-enabled employer org. - You can now say: "I've built a segment-triggered marketing flow with an email send step in Marketing Cloud Next."

— Phase 4: AI —

L12 · Build and test an agent 🆓 — your DE - Goal: Say "I've built an Agentforce agent" truthfully. - Steps: (after A3) Setup → Agentforce Agents / Agentforce Studio → New Agent → pick a template (e.g., a service-style Q&A agent) → add a topic with instructions + a standard action (answer from CRM records) → test in the Agent Builder preview pane. Bonus: Prompt Builder → create a template grounded on a Data Cloud DMO field. Mind the 150 LLM outputs/hour cap. - You can now say: "I've configured an Agentforce agent — topics, instructions, actions — and tested it in Agent Builder."

---

🎤 Rapid-fire

1. Q: Is there a free Marketing Cloud Next trial? A: No — Salesforce Help explicitly says there are currently no MC free trials. Free access = DE (Agentforce + Data 360) + badge-specific MC Next playgrounds + partner SDO. …and in practice: sign up at developer.salesforce.com/signup first, then launch MC Next hands-on badges for the timed playground.

2. Q: Can a standard Trailhead Playground run Data Cloud? A: No. You need either a custom Data-Cloud playground provisioned by a specific badge (works only for that badge) or your own DE with Data Cloud enabled. …and in practice: always create the playground from the challenge box inside the badge, never reuse an old one.

3. Q: What are the DE's Data Cloud and AI limits? A: 1 data space, ~10 GB of data, 150 LLM generation requests/hour; org terminates after 45 days of no logins. …and in practice: set a recurring calendar reminder to log in fortnightly.

4. Q: What can't the free MC Next playground do? A: Deliver real email, and live beyond ~3 days per instance (Advanced-level features otherwise). …and in practice: write your lab script before spinning it up; screenshot everything for your portfolio.

5. Q: Zero external infrastructure — what's your first data stream? A: The Salesforce CRM connector against your own DE's Contacts — no SFTP/S3/API needed. …and in practice: Data Cloud app → Data Streams → New → Salesforce CRM → Contact bundle.

6. Q: What hands-on proof can you put on your profile? A: Superbadge: Data Stream Fundamentals (and Data Quality and Validation) — requirements-based assessments, plus the Data 360 Learning Journey badges and the Meet Agentforce Marketing trail. …and in practice: superbadges validate inside their own custom playground automatically.

7. Q: You join a Salesforce partner — fastest full MC Growth environment? A: Partner Learning Camp → Demo Org tab → request the MC Growth SDO, then run its setup guide. …and in practice: SDOs are time-limited — treat them like the MC Next playground, only bigger.

8. Q: An employer "has no Marketing Cloud budget." What do you propose? A: If they run Sales/Service Enterprise+, enable Salesforce Foundations free: 2,000 sends/month, 10k Data Cloud segmentation/activation credits, Agentforce starter credits — a real pilot environment. …and in practice: it's switched on from the org's own Setup/Your Account, no new contract.

9. Q: What can you practice today, in ANY org, that transfers 1:1 to MC Next? A: Flow Builder — record-triggered, scheduled, decisions, loops — because MC Next journeys are flows. …and in practice: L3/L4 in a plain playground already train 70% of the journey-building muscle.

---

⚠️ Gotchas / currency notes

• Badge names and playground types churn fast. The MC Next playground appeared around May 2026 via specific badges; names/availability may differ by the time you click. Search Trailhead for "Marketing Cloud Next" fresh rather than trusting a saved link — and never claim a capability in an interview without having re-checked that week.
• Custom playgrounds are badge-locked. A Data Cloud playground made for badge X routinely fails badge Y's checks. Spin a fresh one per badge; note its expiry date on creation.
• Data Cloud enablement is effectively one-way and slow. In your DE, provisioning can take hours, and you can't "un-provision" back to a clean slate — do it once in your permanent DE, deliberately.
• The free MC Next playground ≠ a sending environment. No real deliveries; ~3-day instance life. Don't tell an interviewer you've "sent campaigns" from it — say you've built and activated them (precise claims survive follow-up questions).
• The DE's 45-day idle termination is real (contractual, per Help). Losing it loses your Data Cloud setup and all lab artifacts.
• "Free Data 360 provisioning" (250k credits, 1 TB) is for paying Enterprise+ customers only — that's an employer conversation, not a job-hunter option. Same for Foundations. (Help)
• Data Cloud → Data 360 rename (Oct 2025) is mid-migration across Trailhead, Help, and org UI — you'll see both names on adjacent screens. Same product; don't let it shake you in a screen-share.
• Classic contrast: in the MCE world there was no self-serve free environment at all (partner-gated demo accounts only) — the July-2026 MC Next reality of "everyone gets Data 360 + Agentforce in a free DE" is a genuine improvement. Use it as your differentiator: most classic-SFMC candidates still haven't clicked through the new stack.
• Agentforce caps shift by quarter (150 LLM/hr today; Vibes/MCP token caps had explicit end dates like May 31, 2026). Verify current numbers before quoting them.

---

Sources

• Salesforce Developers Blog — Introducing the New Salesforce Developer Edition, Now with Agentforce and Data Cloud (Mar 2025)
• Salesforce Help — Developer Edition with Agentforce and Data Cloud (limits, enablement order, 45-day rule)
• Apex Hours — FREE Agentforce and Data Cloud Developer Org (1 data space, 10 GB, 150 LLM/hr)
• Salesforce Developers Blog — New in Developer Edition: Agentforce Vibes IDE, Claude 4.5, MCP (Apr 2026)
• SFMC Tips #301 — Marketing Cloud Next: A Free Developer Edition Available to Everyone (May 2026; 3-day instances, no sends)
• Salesforce Help — How can I sign up for a free trial of Marketing Cloud? (answer: no free trials)
• Trailhead — Set Up Your Custom Data Cloud Playground (badge-locked playgrounds, data bundles, abandoned-carts CI)
• Trailhead — Meet Agentforce Marketing trail
• Trailhead — Data 360 Learning Journey (3-level trail)
• Trailhead — Data 360: Explore Setup to Activation trail
• Trailhead — Superbadge: Data Stream Fundamentals
• Trailhead — Create a Trailhead Playground (Hands-On Orgs)
• SFMC Tips #151 — Marketing Cloud Next: Setup Steps for SDO (partner demo org)
• DYDC — How to Request a Salesforce Demo Org in Partner Learning Camp
• Salesforce — Salesforce Foundations (free marketing features for Enterprise+)
• Salesforce Ben — The Ultimate Guide to Salesforce Foundations (2,000 sends/mo, 10k Data Cloud credits)
• Salesforce Help — Free Data 360 Provisioning for Enterprise+ customers (250k credits, 1 TB)

➡️ Next: N14_Certifications_and_3_Month_Plan.md

N08 — Certifications & the 3-Month Plan

🎯 Why this matters: You already hold Marketing Cloud Email Specialist — a classic-MCE credential. It still counts, but it proves the old stack. For the "Marketing Cloud Next" world (Marketing Cloud Growth/Advanced running on Core + Data 360 + Agentforce), the certs that signal you've made the pivot are different: they live in the data and AI tracks, not the classic marketing track. Here's the surprising part you must know before spending money: as of 2026 there is NO Marketing-Cloud-Next / Growth-specific certification — Salesforce Ben expects one within ~24 months, but it doesn't exist yet. (Salesforce Ben) So the winning pivot play is: Data 360 Consultant + Platform Administrator + Agentforce Specialist, backed by the Meet Agentforce Marketing trailmix. This module gives you the cert ladder, the free-voucher reality (spoiler: the 2025 free-AI-cert window closed), and a concrete 12-week schedule.

---

🧠 One-screen mental model

Think of it as a 3-phase ladder: you already own the bottom-left classic rung; you climb right (data) then up (AI), and the MC-Next skill is proven by the trailmix + hands-on org, not a badge that doesn't exist yet.

                        THE 2026 PIVOT CERT LADDER
                        (classic → MC Next)

  PHASE 3  ┌───────────────────────────────────────────────────────┐
  (AI)     │  ★ Agentforce Specialist  (AI-201)   73% · $200        │  Wks 9–12
           │     proves: agentic marketing, prompts, Trust Layer    │
           └───────────────────▲───────────────────────────────────┘
                               │ needs data + flow foundation
  PHASE 2  ┌───────────────────┴───────────────────────────────────┐
  (Data)   │  ★ Data 360 Consultant  (Data-Con-101)  70% · $200     │  Wks 1–4
           │     proves: ingest · harmonize · segment · activate    │
           │  + Platform Administrator (Flows/security)  61%·$200    │
           └───────────────────▲───────────────────────────────────┘
                               │ same "audience→journey" instinct
  PHASE 1  ┌───────────────────┴───────────────────────────────────┐
  (Classic │  ✔ Marketing Cloud Email Specialist  (MC-202)          │  DONE ✅
   — you)  │     you already have this — keep it current            │
           └───────────────────────────────────────────────────────┘

   ⚠️ NO "Marketing Cloud Next / Growth" cert exists in 2026.
      You prove MC Next with the "Meet Agentforce Marketing" trailmix
      + a Growth/Advanced hands-on org, not a badge.

---

🎓 The certs that matter (2026)

Naming alert (verified July 2026): Data Cloud was rebranded to Data 360 on 14 Oct 2025, and the Data Cloud Consultant cert was renamed Salesforce Certified Data 360 Consultant effective 27 Mar 2026 — but the exam code stays Data-Con-101. (Salesforce Data 360 Consultant Exam Guide, Passcert rebrand note) Likewise, the Trailhead "Marketing Cloud Next" content is now surfaced under the "Agentforce Marketing" brand. (Meet Agentforce Marketing trail)

Verified exam facts (July 2026): - Data 360 Consultant — 60 questions (+ up to 5 unscored), 105 min, 70% pass, $200 (retake $100). Outline: Data Activations & Utilization 20% · Data Source Connection & Ingestion 18% · Data Enhancements/Sharing/Analysis 18% · Harmonization & Unification 17% · Solution Positioning 14% · Setup & Administration 13%. (Exam Guide) - Agentforce Specialist (AI-201) — 60 questions, 105 min, 73% pass, $200 (retake $100). Domains: AI Agents 35% · Prompt Engineering 20% · Data Cloud for Agentforce 20% · Development Lifecycle 20% · Multi-Agent Interoperability 5%. (Salesforce Ben guide, Trailhead credential) - Registration: all exams now book through Trailhead Academy (Webassessor retired ~July 2025). (The Salesforce Monk)

---

🧰 Trailmixes, trails & superbadges to lean on

• Data 360 (Data Cloud): Prepare for your Salesforce Data 360 Consultant Certification trail — the official prep path. Pair with the Data Cloud hands-on badges (ingestion, DMOs, identity resolution, calculated insights, segmentation, activation).
• MC Growth / MC Next (content, segments, flows): Meet Agentforce Marketing trail + Marketing Cloud Next Basics module + Marketing Cloud Next Setup: Quick Look. Community-curated: Get started with Marketing Cloud Growth or Advanced trailmix.
• Agentforce: Cert Prep: Agentforce Specialist module + the Become an Agentblazer Champion 2026 / Innovator 2026 trails. Agentblazer status is a Trailhead rank, not a certification — useful for hands-on reps and exam prep, but it doesn't replace AI-201. (Salesforce Ben on Agentblazer)
• Superbadges: hunt current Data Cloud / Agentforce superbadges in the Trailhead catalog — they're the closest thing to hands-on proof and reinforce exam scenarios. (Availability shifts per release — check the catalog live.)

---

🗓️ The 12-week plan

Assumes ~8–10 hrs/week alongside a job. Book each exam at the start of its phase so the date forces the pace.

Weeks 1–4 — Data 360 (your #1 cert)

• Week 1 — Foundations & setup. Work the Data 360 Consultant prep trail intro; internalize the model: Data Streams → DLOs → DMOs → Identity Resolution → Unified Individual. Map every classic concept to it (Data Extension → DMO; Subscriber → Unified Individual). Cross-reference your own N02_Data_Cloud_Foundations.md.
• Week 2 — Ingestion & harmonization (35% of exam combined). Data sources, connectors, mapping to the canonical model, transforms, source sequence, reconciliation rules. Do the hands-on ingestion badges in a Data Cloud playground.
• Week 3 — Segmentation, insights & activation (38% combined). Build segments, calculated insights, data graphs, and activations to a marketing target. This is where Data 360 meets MC Next — connect it to N03_Segmentation_and_Audiences.md.
• Week 4 — Setup/admin, solution positioning + mock exams. Security, sharing, sandbox migration; then 2–3 full practice exams, review every miss. Sit Data 360 Consultant (Data-Con-101) at end of Week 4. 🎯

Weeks 5–8 — MC Growth content / segments / flows + Platform Admin

• Week 5 — Platform Admin core. Users, profiles/perm sets, sharing, objects, reports/dashboards. You need Core fluency because MC Next lives on it.
• Week 6 — Flow Builder deep-dive. Screen, record-triggered, scheduled, and segment-triggered flows. This is the Journey Builder replacement — drill it hard against N05_Flows_and_Journeys.md. Build 3–4 marketing flows in a Growth/Advanced org or Developer edition.
• Week 7 — MC Next content & segments. Work Meet Agentforce Marketing + MC Next Basics/Setup: CMS content, Handlebars personalization, Personalization Points, data graphs, campaigns. Tie to N04_Content_and_Email.md.
• Week 8 — Platform Admin mocks + optional attempt. Practice exams; sit Platform Administrator if ready (or defer to Week 12). Consolidate MC Next hands-on into a small end-to-end demo (segment → flow → email).

Weeks 9–12 — Agentforce + practice + cert attempt

• Week 9 — AI & prompt fundamentals. Become an Agentblazer Champion 2026 AI fundamentals + prompt engineering. Understand LLMs, grounding, the Einstein Trust Layer.
• Week 10 — Build agents (35% domain). Agent topics/actions, Agent Builder, testing; Data Cloud for Agentforce grounding (20% domain) — ties directly back to your Week 1–4 Data 360 work.
• Week 11 — Dev lifecycle + multi-agent + full mocks. Deployment, monitoring, multi-agent interoperability; 2–3 AI-201 practice exams, review misses.
• Week 12 — Capstone. Sit Agentforce Specialist (AI-201). 🎯 Refresh your end-to-end MC Next demo (Data 360 segment → Flow journey → Agentforce assist) as an interview artifact; sit Platform Admin here if you deferred it.

Sequencing logic: Data 360 first because everything (segments, flows, Agentforce grounding) depends on the data model. Agentforce last because it reuses Data Cloud + Flow knowledge — you'll pass it far more easily after Weeks 1–8.

---

🧩 Mnemonics / how to stay consistent

• "D-A-A" ladder — Data (360) → Admin (Platform/Flows) → Agentforce. Climb in that order; each rung feeds the next.
• "No Next badge — prove it, don't chase it." There's no MC-Next cert in 2026; your proof is the Meet Agentforce Marketing trailmix + a hands-on org + a live demo.
• "Data-Con-101, still one-oh-one." The name became Data 360 but the exam code (and most content) didn't — old study material largely still applies; just re-map the vocabulary.
• Book the date to make the time. Schedule each exam at the start of its phase — a paid date is the most reliable motivator.
• One playground, one demo. Keep a single Developer/Growth org and grow one end-to-end use case across all 12 weeks; it doubles as revision and an interview artifact.
• Weekly cadence: 3 short weekday sessions (theory) + 1 weekend hands-on block. Miss a day, don't skip the weekend build.

---

⚠️ Currency note

Verify before you spend money. Salesforce renames and reprices certs frequently, and the info below is accurate as of July 2026 but will drift:

• Free vouchers reality — the 2025 window CLOSED. Salesforce's promo offering AI Associate + Agentforce/AI Specialist exams free ran through 31 Dec 2025 and is now expired. There is no confirmed universal free voucher for Agentforce Specialist or Data 360 in 2026. (Salesforce Ben on Agentblazer) Free vouchers still exist mainly for Salesforce Partners (partner-community requests; a 2026 window opened ~27 Apr 2026) and occasional Trailhead Quests — not the general public. Check the live Free Vouchers Trailblazer Community topic and Trailhead Quests before assuming any exam is free. (Partner voucher FAQ)
• Cert names/codes drift. Data Cloud → Data 360 already happened (code Data-Con-101 unchanged). Confirm names on the official credentials catalog before booking.
• A real MC-Next / Growth cert may launch. Salesforce Ben expects one "within ~24 months." If it appears during your prep, re-prioritize — but don't wait for it; the D-A-A ladder is the current best path. (Salesforce Ben 2026 guide)
• Exam outlines & prices ($200 / $100 retake here) can change per release — re-read the official exam guide for each cert the week you book.
• Registration is via Trailhead Academy now (Webassessor retired ~July 2025). (The Salesforce Monk)

---

➡️ Next: N15_Interview_QA_for_MC_Next.md

N09 — Interview Q&A for Marketing Cloud Next

🎯 Why this matters: A modern Marketing Cloud interview is no longer "explain AMPscript and Journey Builder." It probes whether you understand that the platform has moved onto Core + Data Cloud (now Data 360), that orchestration is Salesforce Flow, that content is Handlebars-first with an AMPscript subset, and that Agentforce is the headline story. Coming from classic Marketing Cloud Engagement (MCE), your job in the room is to prove you get the new architecture while translating your existing muscle memory into the new vocabulary. This bank gives you crisp, current, defensible answers — grouped the way interviewers actually cluster them — so you can pattern-match a question to a strong 30–60-second reply. ⭐ marks the questions that come up most.

---

🧠 One-screen mental model

What a modern MC interview is really probing — five concentric rings. If you can speak confidently to each ring, you cover ~90% of what gets asked.

        ┌──────────────────────────────────────────────────────────────┐
        │  (5) "COMING FROM CLASSIC" — can you translate MCE → Next?    │
        │  ┌────────────────────────────────────────────────────────┐  │
        │  │  (4) AGENTFORCE — do you know agentic marketing & GA?  │  │
        │  │  ┌──────────────────────────────────────────────────┐  │  │
        │  │  │  (3) SEGMENTS + CONTENT — declarative, Handlebars │  │  │
        │  │  │  ┌────────────────────────────────────────────┐  │  │  │
        │  │  │  │ (2) DATA CLOUD / DATA 360 — the foundation │  │  │  │
        │  │  │  │  ┌──────────────────────────────────────┐  │  │  │  │
        │  │  │  │  │ (1) LANDSCAPE — editions & "why Next"│  │  │  │  │
        │  │  │  │  └──────────────────────────────────────┘  │  │  │  │
        │  │  │  └────────────────────────────────────────────┘  │  │  │
        │  │  └──────────────────────────────────────────────────┘  │  │
        │  └────────────────────────────────────────────────────────┘  │
        └──────────────────────────────────────────────────────────────┘
   Flow (orchestration) cuts through all rings — expect it in every section.

---

🎤 The question bank

(a) Landscape / editions

⭐ Q1. What is "Marketing Cloud Next," and how does it relate to Growth and Advanced? "Marketing Cloud Next" is the umbrella name for the reimagined, AI-native Marketing Cloud that runs natively on the Salesforce Core platform with Data Cloud (Data 360) at its foundation — often described as "Marketing Cloud on Core." The two commercial editions you buy are Marketing Cloud Growth (for smaller / mid-market teams) and Marketing Cloud Advanced (built for scale). Both share the same foundation — Data Cloud + Core + Flow — and differ mainly in AI, experimentation, and account-based features. So "Next" is the vision/architecture; Growth and Advanced are the editions (Salesforce blog, Concret.io).

⭐ Q2. How is Marketing Cloud Next different from classic Marketing Cloud Engagement (MCE)? Three architectural shifts: 1. Where it runs — MCE is a separate, acquired stack (Contact Builder, its own Automation Studio, SFTP). Next runs inside the Salesforce Core org on standard metadata. 2. The data layer — MCE uses Data Extensions and All Subscribers; Next uses Data Cloud / Data 360 (data streams → DLOs → DMOs → unified profiles). 3. Orchestration & content — Journey Builder + AMPscript give way to Salesforce Flow and Handlebars (with an AMPscript subset). Key point to land: Salesforce is NOT forcing MCE customers to migrate — MCE continues, and Next is the path forward for new investment and unified data (Salesforce Ben).

⭐ Q3. What is the difference between Marketing Cloud Growth and Advanced? Both share Data Cloud + Core + Flow; Advanced layers on scale and intelligence: - A/B testing: Growth has no native A/B testing (you fake it with decision splits); Advanced has Path Experiments (up to ~10 variations, automated winner selection). - Predictive AI: Advanced adds Einstein Engagement Scoring and Einstein Engagement Frequency; Growth has basic generative/content AI only. - Messaging: Growth does outbound email/SMS/WhatsApp; Advanced adds Unified Conversations (two-way messaging, routing to Agentforce or Service Cloud) and send policies. - ABM: Advanced adds Unified Account profiles and Account Scoring; Growth is people-only. (The Agentic Marketer)

Q4. What is Data 360 and how does it relate to Data Cloud? Data 360 is the new name for Salesforce Data Cloud, rebranded at Dreamforce 2025 as part of the Agentforce 360 platform story. Same product, license, integrations, and data model — new name plus additions like semantic modeling, Clean Rooms, and deeper Agentforce integration. Good line to drop: "Data Cloud is on its sixth name — it's been Customer 360 Audiences, Salesforce CDP, Genie, Data Cloud, and now Data 360." (Salesforce Ben, Salesforce Help)

⭐ Q5. "Why Marketing Cloud Next?" — sell me the move. "Because it collapses the data silo. In classic MCE, my marketing data lived apart from the CRM and I stitched it together with integrations and Data Extensions. Next puts marketing on the same platform and the same customer record as Sales and Service, powered by Data Cloud — so segmentation, personalization, and orchestration all read from one unified profile, and Agentforce can act on that data autonomously. Less integration glue, one source of truth, and an AI-native execution layer." (Salesforce blog)

Q6. Was Marketing Cloud renamed to "Agentforce Marketing"? Yes — as of the Dreamforce 2025 / Agentforce 360 positioning, Salesforce has been branding Marketing Cloud as Agentforce Marketing, reflecting the shift from campaign automation to agentic marketing. Treat this as branding in flux — say "the product now positioned as Agentforce Marketing, built on the Growth/Advanced editions" so you're covered whichever name the interviewer uses (The Agentic Marketer).

Q7. Does Data Cloud / Data 360 come free with Marketing Cloud Next? Marketing Cloud Next requires Data 360 to be provisioned, and orgs consume Data 360 credits for ingestion, processing, and activation. So it's foundational, not optional — budget and consumption planning around Data 360 credits is a real implementation concern to mention (Cloud Analysts).

---

(b) Data Cloud / Data 360

⭐ Q8. Walk me through the Data Cloud ingestion-to-activation pipeline. "Data stream brings source data in on a schedule or in real time → it lands in a Data Lake Object (DLO), the raw staging copy → I map the DLO to a Data Model Object (DMO) to harmonize it into the canonical model → identity resolution unifies records into a Unified Individual profile → I build segments and calculated insights on the DMOs → then activate the segment to a target (email/SMS via a Marketing Flow, ads, etc.)." That five-word chain — stream → DLO → DMO → unify → activate — is your backbone (Salesforce Help, Ateko).

⭐ Q9. DLO vs DMO — what's the difference? A Data Lake Object (DLO) is the raw storage layer: it holds ingested data exactly as received, preserving original fields and format — your staging area. A Data Model Object (DMO) is the harmonized layer: a standardized structure that maps similar data from many sources into a common model, and it's what actually supports segmentation, identity resolution, and insights. Rule of thumb: DLO = raw/staging, DMO = clean/queryable. (Peoplewoo, jthathapudi)

Q10. What is identity resolution and why does it matter? Identity resolution is the rules-based process that matches and merges records across sources into a single Unified Individual (and, in Advanced, Unified Account). You define match rules (e.g., exact email, fuzzy name+address) and reconciliation rules (which source wins a conflict). It matters because everything downstream — a clean segment, correct personalization, suppression — depends on one person = one profile. Classic analogy: it's the Data Cloud equivalent of the SubscriberKey/contact-dedupe problem, but declarative and cross-source.

Q11. What is a Calculated Insight? A Calculated Insight is a metric computed across your DMOs on a schedule (batch) — think lifetime value, purchase frequency, average order value, engagement score. It runs over the whole unified data model with a broad historical lookback, and the output can be used in segments and personalization. Coming from classic, it's conceptually the counterpart to a SQL aggregate over Data Views — but reusable and profile-attached (Salesforce Ben).

Q12. What's the difference between a segment and an activation? A segment is the definition of an audience (declarative filters over DMOs / insights). An activation is sending that audience somewhere to act on it — e.g., publishing it to a Marketing Flow, an ad platform, or another target, on a schedule or in real time. Segment = "who," Activation = "where they go / what happens."

Q13. Real-time vs batch in Data Cloud — when does each apply? Data streams can ingest in batch (scheduled files/CRM syncs) or streaming/real-time (web/mobile events, Interaction SDK). Calculated insights are batch; streaming insights / real-time segmentation react to live events. In an interview, name the tradeoff: real-time costs more credits and suits triggered moments (abandoned cart), batch suits scheduled campaigns.

---

(c) Segmentation & content

⭐ Q14. How do you personalize content in Marketing Cloud Next? Content is Handlebars-first. You insert merge fields — including cross-object merge fields that pull any attribute on any object related to the Unified Individual (e.g., the individual's name, or the account name related to them) — plus new sources like Salesforce objects and content variables. You can drive dynamic content off a Data Cloud data graph so each contact gets tailored fields. As of Summer '26, you can also use an AMPscript subset and combine HTML + Handlebars + AMPscript in the visual editor with syntax validation (Salesforce Ben, marketingcloudtips).

⭐ Q15. Is AMPscript gone? What's its status in Next? Not gone, but reduced to a subset. AMPscript arrived in Marketing Cloud Next in the Summer '26 release (Growth & Advanced). Two things to know: (1) it's a subset — some MCE functions aren't available yet, though core things like IF conditional logic are supported; and (2) internally, AMPscript is converted to Handlebars before processing. So the strategic answer is "Handlebars is the native templating language; AMPscript is a supported subset layered on top for those of us coming from MCE." Flag this as actively evolving (marketingcloudtips Summer '26, marketingcloudtips personalization).

Q16. What are "declarative segments" and how do they differ from SQL/Data Extension filtering? In Next you build audiences declaratively — point-and-click filters, related-attribute lookups, and calculated insights over DMOs — rather than writing SQL against Data Views/DEs. The benefits: it reads from the unified profile (cross-source), it's governable/reusable, and non-developers can maintain it. Your SQL instinct still helps you reason about joins and aggregation, but the authoring surface is declarative.

Q17. What are personalization points / where does personalization happen? Personalization enters at several points: merge fields in subject/body/from-address, dynamic content blocks (show/hide by rule), data-graph-driven fields, and generative content. The interviewer wants to hear that personalization is data-driven off the unified profile and data graph, not hard-coded per send.

Q18. What is generative content in this stack? Generative content is AI-authored copy — subject lines, body, briefs — created from a prompt, grounded on your brand and data. In Growth it's part of the basic AI tier; the fuller experience (Campaign Creation / Campaign Designer) generates whole multi-channel campaigns from a single prompt. Frame it as AI drafts, human approves — human-in-the-loop (The Agentic Marketer).

Q19. (Practical) Show me how you'd greet a subscriber by first name with a fallback. Handlebars with a helper/default:

Hi {{#if Individual.FirstName}}{{Individual.FirstName}}{{else}}there{{/if}},

Line by line: - {{#if Individual.FirstName}} — Handlebars block helper; opens a conditional testing whether the unified profile's FirstName is present/truthy. - {{Individual.FirstName}} — merge field: outputs the first name from the Unified Individual DMO when it exists. - {{else}}there{{/if}} — fallback branch renders the literal there when the field is empty; {{/if}} closes the block. The AMPscript-subset equivalent (Summer '26+) would use an IF block instead — useful to mention you can do it either way, but Handlebars is the native path.

---

(d) Flows / orchestration

⭐ Q20. Flow vs Journey Builder — explain the shift. In MCE, orchestration lives in Journey Builder: a standalone canvas with its own entry sources, splits, and waits. In Next, orchestration is Salesforce Flow (Flow Builder) on Core — a Segment-Triggered start injects a Data Cloud segment, then you chain Wait, Decision, and Send Email/SMS/WhatsApp elements, and can also create/update Core records. The shapes map almost 1:1, but the engine, the entry model (Data Cloud segments + real-time CRM events), and the pricing dynamics change (Salesforce Ben, Salesforce Help — Flow elements for Marketing Flows).

Q21. Is Journey Builder being killed? No. Salesforce has been explicit that they're not shutting down Journey Builder or forcing migrations. The strategy is Flow and Journey Builder side by side — Flow can orchestrate across journeys ("air traffic control"), react to real-time CRM events, and daisy-chain/prioritize journeys. So the honest answer is "coexistence, with Flow as the higher-level orchestrator," not "rip and replace" (Salesforce Ben).

Q22. What's the difference between a Marketing/Campaign Flow and a regular Salesforce Flow? A Campaign/Marketing Flow is essentially a scoped version of Salesforce Flow with marketing-specific elements (channel sends, waits, decision splits, entry from segments) — a subset of full Flow. A regular Salesforce Flow is the general automation tool across the platform. Same engine, marketing-tuned palette (Salesforce Ben).

Q23. How does someone enter a Flow-based journey? Most commonly via a Segment-Triggered start — members of a Data Cloud segment are injected on schedule or publish, with re-entry rules (always / never / after done). You can also start from real-time CRM events on Core (record created/updated), which is the big unlock over classic Journey Builder entry sources.

---

(e) Agentforce

⭐ Q24. What is Agentforce, and what do marketing agents actually do? Agentforce is Salesforce's platform for autonomous AI agents that plan, execute, and optimize work with human oversight — powered by Data 360 for context. In marketing, agents do things like generate whole campaigns from a prompt (Campaign Creation), build content (Content Builder agent), and optimize paid media 24/7 (Paid Media Optimization). The narrative arc to state: automation → autonomous — the platform moves from "I build the journey" to "an agent proposes and runs the journey, I approve" (The Agentic Marketer, Salesforce Ben).

Q25. What's GA today vs roadmap for Agentforce Marketing? (be careful here) Frame this as fast-moving and cite dates. As of the Dreamforce 2025 / late-2025 wave: Campaign Creation became broadly available (including to Account Engagement customers); Marketing Performance & Campaign dashboards and two-way mobile were slated GA October 2025; two-way email was announced for February 2026; and Campaign Designer was in Beta. Always add: "these dates shift release-to-release — I'd confirm against the current release notes." (The Agentic Marketer — Dreamforce 2025, Salesforce blog)

Q26. What are the guardrails / governance concerns with marketing agents? Great senior-level answer: human-in-the-loop approval, grounding on trusted first-party data (Data 360) rather than open-web hallucination, brand/tone guardrails, consent and preference enforcement carried through from the unified profile, and auditability of what an agent sent and why. Interviewers love that you think about trust and control, not just capability.

---

(f) "Coming from classic" bridge questions

⭐ Q27. You're an MCE expert. What transfers, and what do you have to relearn? "Transfers: my instincts for audience logic, deliverability/IP warming, subscriber lifecycle, personalization thinking, and testing discipline. Relearn: the data layer (Data Extensions/All Subscribers → Data Cloud DLO/DMO/unified profiles), orchestration (Journey Builder → Salesforce Flow), templating (AMPscript → Handlebars + AMPscript subset), and the fact that everything now lives on the Core platform with Data 360 credits as a real cost dimension." Showing you can map old→new and name what's genuinely new is exactly the signal they want.

Q28. In MCE I used a Sendable Data Extension with a SubscriberKey. What's the equivalent in Next? The equivalent of "who can I send to and how do I dedupe them" is the Unified Individual profile produced by identity resolution over DMOs. Instead of a SubscriberKey on a DE, the unified profile is the canonical person, and you send by activating a segment built on it. So: DE+SubscriberKey → DMO + identity resolution + segment activation.

Q29. Where did Automation Studio / SQL Queries / SSJS go? There's no MCE-style Automation Studio in Next. Scheduled data work moves into Data Cloud (data streams, data transforms, calculated insights) and Core automation moves to Flow. Declarative segmentation replaces most Data-View SQL. SSJS isn't part of the Next content model — content is Handlebars + AMPscript subset. The honest note: some MCE power-user capabilities are still maturing in Next, which is why MCE isn't being force-migrated.

Q30. A stakeholder asks "should we migrate from MCE to Next today?" How do you answer? "It depends on data-unification value and feature-parity gaps. If they need marketing on the same profile as Sales/Service and want Agentforce, Next is compelling. But I'd audit for parity gaps (some advanced MCE features are still maturing), scope Data 360 credit consumption, and note that Salesforce isn't forcing migration — so a phased or coexistence approach is valid. I'd never say 'migrate everything now' without that assessment." That balanced, risk-aware answer reads as senior.

---

🧩 3 things to say that signal you're current

1. "Data Cloud is now Data 360." Drop that it was renamed at Dreamforce 2025 under the Agentforce 360 umbrella (and that Marketing Cloud is positioned as Agentforce Marketing). Naming currency instantly signals you're tracking the platform in 2025–2026, not 2022 (Salesforce Ben).

2. "Journeys are Flow-based now — but Journey Builder isn't dead." Saying orchestration moved to Salesforce Flow while correctly noting coexistence, not forced migration shows nuance most candidates miss (Salesforce Ben).

3. "Content is Handlebars-first, with an AMPscript subset that landed in Summer '26 and compiles to Handlebars." This one line proves you know the exact current state of templating — subset status, the direction of travel, and the implementation detail (marketingcloudtips).

---

⚠️ Currency note

This module reflects the state of Marketing Cloud Next as of mid-2026 and is a fast-moving area — treat all of the following as verify-before-the-interview: - Naming: "Data Cloud → Data 360" and "Marketing Cloud → Agentforce Marketing" were rebrands at Dreamforce 2025 (Oct 14, 2025); Salesforce marketing branding continues to shift release-to-release. - AMPscript subset: arrived in Summer '26; the set of supported functions is expanding — confirm current coverage in release notes. - Agentforce GA dates: the Oct 2025 / Feb 2026 milestones above are release-plan dates and slip; always cross-check the latest release notes and Trailhead. - Edition features: Growth vs Advanced boundaries (A/B testing, Einstein scoring, Unified Conversations) evolve — verify against the current edition comparison. Primary sources used: Salesforce blog — Next details · Salesforce Ben — Data 360 rename · Salesforce Ben — Journey Builder & Flow · marketingcloudtips — Summer '26 highlights · Salesforce Help — About Data 360.

---

➡️ Next: N16_Glossary_and_Cheat_Sheet.md

N16 — Glossary & One-Page Cheat Sheet

🎯 Why this matters: This is your revision asset — the whole course compressed into one sitting. Fifteen modules taught you the concepts; this one makes them retrievable under pressure. Skim the A–Z before any interview, screening call, or client conversation about Marketing Cloud Next, and you'll never again blank on "wait, what's a DLO vs a DMO?" Every term is 1–2 lines, every number is quotable, and every classic→Next mapping is one row. Ten minutes here refreshes three months of work.

---

🧠 One-screen mental model

Every glossary term lives in one of four rooms. If you can place a word in its room, you already half-know it.

 ┌─────────────────────────────────────────────────────────────────────────┐
 │ B — BRAND ROOM (names & wrappers)                                        │
 │   Agentforce Marketing (umbrella) · Agentforce 360 (platform brand)      │
 │   Marketing Cloud Next (vision) · Growth / Advanced (the SKUs you buy)   │
 └───────────────────────────────────┬─────────────────────────────────────┘
                                     ▼
 ┌─────────────────────────────────────────────────────────────────────────┐
 │ C — CORE-APP ROOM (what marketers click, on Lightning)                   │
 │   Campaign · Campaign brief · Content (Salesforce CMS) · Handlebars      │
 │   Personalization Point · Flow types · Wait/Decision · Path Experiment   │
 │   Communication Subscription · Consent · Permission Sets                 │
 └───────────────────────────────────┬─────────────────────────────────────┘
                                     ▼
 ┌─────────────────────────────────────────────────────────────────────────┐
 │ D — DATA ROOM (Data Cloud / Data 360)                                    │
 │   Data Stream → DSO → DLO → DMO → Identity Resolution → Unified          │
 │   Individual → Calculated Insight → Segment → Data Graph (+ Data Space,  │
 │   Data Transform, zero copy)                                             │
 └───────────────────────────────────┬─────────────────────────────────────┘
                                     ▼
 ┌─────────────────────────────────────────────────────────────────────────┐
 │ A — AI ROOM (Einstein + Agentforce)                                      │
 │   Predictive: STO · Metrics Guard · Engagement Scoring/Frequency (Adv)   │
 │   Generative/agentic: Campaign Creation Agent · Agentforce Builder ·     │
 │   Prompt Builder · Brand Center · Einstein Trust Layer (grounding)       │
 └─────────────────────────────────────────────────────────────────────────┘

---

🔑 Core in 60 seconds

• How to revise with this sheet: say the four rooms (Brand · Core app · Data · AI), chant the pipeline (S-S-D-D-I-U-C-S-A, from N02), state the 3 big shifts, quote two numbers, and rehearse the 10 rapid-fire one-liners out loud. That's a full warm-up in ~10 minutes.
• The single most important sentence: "Marketing Cloud Next is marketing rebuilt natively on core Salesforce — Data 360 as the data layer, Flow as the orchestration engine, Salesforce CMS as the content layer, and Agentforce as the AI layer — sold as the Growth and Advanced editions."
• The single most important contrast: classic MCE = you are the engine (SQL, AMPscript, Journey Builder). MC Next = the platform + agents draft, you model data, supervise, and approve.
• Currency discipline: platform is fast-moving; prefix any number or feature claim with "as of Summer '26" and never present roadmap as GA.

---

📖 A–Z glossary (~55 terms)

A–B

C

D

E–L

M–P

Q–Z

---

🧩 Mnemonics & memory hooks

• The four rooms — "A-B-C-D map": every term is AI, Brand, Core app, or Data. Place the word in its room before defining it and you'll sound structured.
• The 3 big shifts — "the old way is D.O.A.": Data (tables → one unified profile), Orchestration (proprietary studios → Flow on core), AI (you build → agents draft, you approve).
• The pipeline — S-S-D-D-I-U-C-S-A (from N02): Sources, Streams, DLO, DMO, Identity, Unified, Calculated insights, Segments, Activation. "Seven Store Dogs Dig In Under Cold Snow Always."
• The staging trio — "Source → Lake → Model = S-L-M": DSO (temporary staging) → DLO (physical landed) → DMO (virtual modeled). Raw gets wetter then smarter: source, lake, model.
• The numbers chant — "41-30 · 25-15 · 50-50 · 12-24": 41 AMPscript functions ≈ 30% coverage · 25 Personalization Points / 15 variations · 50 include + 50 exclude filters · Standard publish every 12–24 h.
• Edition gate — "Fancy = Advanced": Path Experiment, Engagement Scoring + Frequency, Campaign Designer, account scoring, Business Units — the fancy stuff is Advanced-only.
• Consent — "no yes means no": implicit opt-out; without a recorded opt-in on that contact point + subscription, promotional sends skip the person.

---

🛠️ In practice (what you would actually click)

Where each vocabulary cluster lives (App Launcher = the waffle grid, top-left):

The 60-second org tour (rehearse this before any hands-on interview):

1. Log in — you land in Lightning (core Salesforce), not a separate SFMC login. Note the gear (Setup) and waffle (App Launcher).
2. App Launcher → "Marketing Cloud" — open the marketing app; walk the tabs: Campaigns · Content · Segments (+ Analytics/Flows depending on release).
3. Segments → New — point out Segment On: Unified Individual, the Include/Exclude containers, and the publish schedule picker (Standard vs Rapid).
4. Campaigns → New — show where the brief lives and where you'd add a Segment-Triggered flow with Send Email Message → Wait → Decision.
5. Content → workspace → New → Email — drag a component, insert a {{ }} Handlebars merge field, add a Personalization Point; mention fields only appear if they're in the Data Graph.
6. App Launcher → "Data Cloud" (may read Data 360) — walk the pipeline tabs in order: Data Streams → Data Lake Objects → Data Model → Identity Resolutions → Calculated Insights → Segments.
7. Setup → Permission Sets — show Marketing Cloud Admin / Marketing Cloud Manager (+ Data 360 sets) as how users get access.
8. App Launcher → Agentforce Studio — where the Campaign Creation Agent and other agents are configured (Agentforce Builder); Setup → Prompt Builder for templates. ⚠️ Agent features and tab names are edition- and release-fluid — say "in the org I practiced in" and verify per org.

---

📋 The one-page cheat sheet

The 3 big shifts (D.O.A.)

Classic → Next mapping (the Rosetta row-by-row)

Numbers & facts worth quoting (as of Summer '26)

---

🎤 Rapid-fire (the 10 one-liners)

1. Q: Is "Marketing Cloud Next" a product you buy? A: No — it's the vision name; you buy the Growth or Advanced edition. …and in practice: the org just shows a Marketing Cloud app in the App Launcher.

2. Q: What replaced Data Extensions? A: DMOs in Data 360 — raw data lands in a DLO, then maps onto the canonical DMO. …and in practice: Data Cloud app → Data Model tab is where you do the mapping.

3. Q: Where did my SQL Query Activities go? A: Split into Calculated Insights (metrics), Segments (audiences), and Data Transforms (reshaping). …and in practice: each is its own tab in the Data Cloud (Data 360) app.

4. Q: What builds journeys now? A: Salesforce Flow — typically a Segment-Triggered Marketing Flow inside a Campaign; no Journey Builder app. …and in practice: Campaigns tab → New → add a flow → Send Email Message → Wait → Decision.

5. Q: Does AMPscript still work? A: Yes, but only a 41-function (~30%) display-only subset since Summer '26 — Handlebars {{ }} is the native language. …and in practice: both validate right inside the email editor; no DE writes or HTTPGet anywhere.

6. Q: What's the one-row-per-person object? A: The Unified Individual, produced by Identity Resolution match rules. …and in practice: it's the mandatory Segment On object for campaign segments.

7. Q: How is an email personalized? A: Handlebars merge fields (incl. cross-object) sourced through a Data Graph, plus Personalization Points for dynamic blocks. …and in practice: if a field isn't in the Data Graph, it simply won't appear in the picker — model the graph first.

8. Q: What does the Campaign Creation Agent actually do? A: Drafts brief → segment → email/SMS content → campaign flow → summary, with a human accepting or refining each step. …and in practice: you type a goal in the campaign screen and approve its proposals — never claim it ships unsupervised.

9. Q: Growth vs Advanced in one breath? A: Same Data 360 + Core + Flow foundation; Advanced adds Path Experiments, Engagement Scoring/Frequency, account scoring, Business Units, and bigger channel/credit allotments. …and in practice: check the org's edition before promising any of the "fancy" features.

10. Q: Is consent opt-in by default? A: No — MC Next assumes implicit opt-out; promotional email/SMS/WhatsApp require an opt-in per contact point + communication subscription. …and in practice: the consent check runs at send time and silently skips non-opted-in contact points.

---

⚠️ Gotchas / currency notes

• Names churn constantly — date-stamp your claims. Data Cloud → Data 360 (Oct 2025), Agent Builder → Agentforce Builder (Feb 2026), "Einstein GPT/Marketing GPT" = legacy branding. Both old and new names coexist in docs; say "as of Summer '26" and you're safe.
• Never quote the numbers as permanent. The 41-function AMPscript list, 25/15 personalization limits, and publish cadences are release-versioned — re-verify against current release notes before an interview.
• GA vs roadmap discipline. Agent autonomy, image generation, and Brand Center maturity are the classic overclaim traps — generative text and the Campaign Creation Agent are GA; anything beyond, verify per org/edition.
• Edition gating trips people. Path Experiment, Engagement Scoring/Frequency, Campaign Designer, account scoring, Business Units = Advanced. Saying "we'll use Scoring in Growth" is a fail.
• DSO is an architecture word, not a daily UI object. In the UI you mostly see DLOs (first inspectable object) and DMOs; keep DSO for "explain the ingestion internals" questions.
• Vocabulary slips mark you as classic-only. "Journey," "DE," "publication list" are fine as bridges — but translate in the same breath ("…which here is a Flow / DMO / communication subscription").
• When in doubt, the canonical reference is Salesforce's own Data 360 Glossary + current release notes — not blog posts, and not this sheet if it's more than one release old.

---

Sources

• Salesforce Help — Marketing Cloud Next (product home)
• Salesforce Help — Data 360 Glossary of Terms
• Salesforce Help — User Permissions in Marketing Cloud Next
• Salesforce Help — Assign Permission Sets for Marketing Cloud Next
• Salesforce Help — Understanding Consent Concepts in Marketing Cloud Next
• Salesforce Help — Segmentation in Marketing Cloud Next
• Salesforce Developers — Handlebars for Marketing Cloud Next
• Salesforce Ben — Data Cloud Renamed to "Data 360"
• Salesforce Ben — Marketing Cloud Growth vs. Advanced Editions
• Salesforce Ben — Top 9 Summer '26 Updates for Salesforce Marketers
• SFMC Tips #280 — MC Next Summer '26: AMPscript Support Has Arrived
• SFMC Tips #285 — MC Next Summer '26 Release Highlights
• Salesforce Admins — Inside the New Agentforce Builder (2026)
• Trailhead — Explore Agentforce Builder
• Trailhead — Segment Creation and Activation in Marketing Cloud Next
• Jayanth Thathapudi — Understanding DSOs, DLOs, and DMOs in Salesforce Data Cloud
• The Agentic Marketer — Consent Management in Marketing Cloud Next
• The Agentic Marketer — Marketing Cloud Next: from Zero to First Email
• Salesforce Blog — Next-Gen Marketing Cloud: Details, Availability and Pricing

---

➡️ Next: (final — re-skim this sheet before any MC-Next conversation. You made the pivot, Akash 🚀)

★ Marked for Review

Sections you flagged with the ☆ Mark button in the bar above (or the M key) while studying. Click any item to jump straight back to it. This list is saved in your browser and updates automatically.