Consent in Marketing Cloud Next is a rules engine most teams can’t hold in their head. Get it wrong during an MCE migration and you get one of two incidents: a send to people who opted out, or a dead list on day one. This is the working reference: the model, a live “will it send?” simulator, the MCE→MC Next mapping, the traps, the audit SQL, and a checklist you tick off before go-live.
● Last verified: September 2026 (Summer ’26 and Winter ’26 features). MC Next changes every release; re-check before you rely on it.
Opt-out
Default in Growth & Advanced
Email / Phone
Consent keys here, not Subscriber Key
Data 360
Where consent now lives (Data Cloud)
Test sends
Do not check consent
The consent model
Consent leaves MCE’s subscriber model entirely. In MC Next it lives in Data 360 (Data Cloud) DMOs and is keyed to the contact point value: the email address or phone number itself. Not the Subscriber Key, not the Individual ID. Click each object to see what it holds and the MCE thing it replaces.
Implicit opt-out. In Marketing Cloud Growth & Advanced, no consent record means the recipient is treated as Opt-Out. Migrate without seeding Opt-In and every contact is silently opted out.
Consent check on send. You select a Communication Subscription when you send, and every recipient must be opted in. Required for promotional email and all SMS / WhatsApp. Transactional-email checks are off by default. Test sends skip the check entirely.
The send check doesn’t query your DMO live. Practitioner testing shows it checks consent against a cache that only updates through certain write paths: the Consent tab / UI, CSV consent import, the Create Consent flow action, unsubscribe links and preference centers. Consent pushed into the DMO any other way (e.g. a raw data stream) can look correct in Data 360 and still be ignored at send time. Validate your seeding method in a sandbox before production.
“Will it send?” The consent simulator
The part nobody can keep straight. Pick a scenario and see whether MC Next sends, blocks, or is at risk, and exactly why.
Build a send scenario
Choose one option in each row. The verdict updates live.
MCE → Marketing Cloud Next: what maps to what
Most rows are a deliberate build. The one exception: since Summer ’26, Consent Synchronization can create Communication Subscriptions from MCE Publication Lists for you (see Coexistence).
Marketing Cloud Engagement
Marketing Cloud Next
The migration traps
Each one passes a test migration and detonates in production. Red border = the ones that cause a compliance incident or a dead list. Click to expand.
Audit SQL: run before you migrate or send
Data 360 Query Editor. ssot__ContactPointEmail__dlm is a standard DMO. The consent DMO and your MCE extract have org-specific API names, so they are marked as {{PLACEHOLDERS}}. Replace them from Data 360 → Data Model before running.
A clean query is not proof. SQL shows what’s in Data 360, not what the send-time consent cache holds. The only real proof is a real (non-test) send to seed addresses you own: one opted in, one opted out, one with no record. Only the first should arrive.
Preference & subscription management
How subscribers actually opt in, opt out, and manage preferences in MC Next.
Communication Subscriptions are your topics. Model each MCE Publication List (Newsletter, Promotions, Product updates…) as a Communication Subscription, each with its channel type(s). A preference center then surfaces those subscriptions so a person can toggle each one, per channel.
Unsubscribe links and preference centers. MC Next unsubscribe and preference links write an Opt-Out against the right contact point and Communication Subscription. They are also supported write paths for the send-time consent cache, so opt-outs taken this way are honoured on the next send.
Surface consent where agents & reps see it. Subscription consents can be surfaced on the Person Account / Contact record so service and sales see the same opt-in state marketing sends against. One source of truth, no “but the CRM checkbox said…” confusion.
Coexistence & consent sync
Most orgs run MCE and MC Next side by side for a while. Consent has to stay in lock-step across both, or a person opts out in one system and keeps getting emailed from the other.
Consent Synchronization, MCE ↔ MC Next (Summer ’26). Two-way sync between MCE Publication Lists / standard lists and MC Next Communication Subscriptions, matched on email address. Set it up before you run parallel sends. Know the catches:
It creates a new Communication Subscription per mapped list. You can’t link a subscription you already built.
An All Subscribers Unsubscribed in MCE opts the address out of every MC Next subscription, including unmapped ones.
Resubscribing in MCE does not restore MC Next consent. There is no universal resubscribe.
Where one email maps to several Subscriber Keys, only one subscriber is used.
Changes take roughly 5 to 10 minutes to appear in the consent DMO.
Consent Matching, Account Engagement ↔ MC Next (Winter ’26). Enabled from the Account Engagement (Pardot) Optimizer. It creates a “B2B Email Consent” subscription in MC Next with Opt-In / Opt-Out from each prospect’s Opted Out field, and keeps the two in sync on email address. It works in one Pardot business unit only, and restarting a stopped sync means removing that subscription and reconfiguring.
The coexistence trap: two systems, two opt-out stores, no sync = you email a person who unsubscribed in the other tool. Sync (or a single source of truth in Data 360) is not optional.
The pre-migration consent checklist
Tick every box before your first production send. Progress saves in your browser.
Migrating MCE to Marketing Cloud Next?
Consent is where these migrations quietly go wrong. Genetrix maps, seeds, and validates consent in Data 360, and rebuilds subscription & preference management, so your first send lands clean and compliant.