Loading

Marketing Cloud Next - Consent Management: Troubleshooting Issues

Julkaisupäivä: Jul 28, 2026
Kuvaus

Note: This article is a companion article for the Consent Management: Frequently Asked Questions resource. Check that article out for additional details and other frequently asked questions.

 

Below are some common issues around consent:

  • "I opted out but I'm still receiving emails."

  • "I imported consent but my segment is still empty."

  • "My opt-out via an external system isn't reflected."

Ratkaisu

Step 1 — Confirm the consent record in the CSC DMO

Open Data Cloud > Data Explorer > Communication Subscription Consent DMO. Filter by contact point value (email or phone) and Communication Subscription Channel Type ID.

 

  • If absent: the upstream write never reached the DMO. Investigate the source (import file, integration, flow).

  • If present with the expected status: continue to Step 2.

 

Step 2 — Compare the DMO to what's honored at send time

Open the Consent Status component on the Lead/Contact record and compare its current opt-in status against the DMO value.

 

  • Match: consent is current. This means the issue is coming from somewhere else. Check items such as audience filter, missing Lead/Contact, or channel mismatch.

  • Mismatch: continue to Step 3.

 

Step 3 — Identify the write path that caused the issue

Check what wrote the most recent value. Common causes, in order:

 

  1. A Flow using MessagingConsent / MessagingConsentV2 actions.

  2. A Data Stream mapped directly to the Consent DLO.

  3. A Batch Data Transform writing to the Consent DLO.

  4. A Data Cloud Ingestion API call writing directly to the Consent DMO.

  5. A custom integration writing consent fields directly.

 

Any of these is an unsupported write path and is the likely cause.

 

Step 4 — Repair

  • Single record / small set: update via the Consent Status Lightning Web Component.

  • Bulk (up to 50k rows): Consent Import CSV.

  • Bulk (over 50k rows): stage into a custom DMO, then run a Data Cloud-Triggered Flow calling Create Consent.

  • Re-run Step 2 to confirm the values now match. Note: expect up to about 15 minutes of latency when reading updated records in Data Cloud.

 

Step 5 — Prevent recurrence

  • Audit Flows for MessagingConsent / MessagingConsentV2 actions; replace with Create Consent.

  • Audit Data Streams and Batch Data Transforms targeting the Consent DLO; reroute through a Data Cloud-Triggered Flow.

  • Audit Ingestion API and custom integrations for direct Consent DMO writes.

 

If consent still isn't honored after re-writing through a supported method, engage Salesforce Support with the details (contact point value, Channel Type ID, DMO value, timestamp of the most recent write, and the write path you identified).

 

Knowledge-artikkelin numero

005389888

 
Ladataan
Salesforce Help | Article