You are here:
Email Send Validations in Unified Messaging
Unified Messaging automatically performs several validation checks during the email send process. These checks help protect sender reputation, ensure compliance, and reduce the likelihood of sends with rendering errors.
To make sure your sends pass the validation checks, review these recommendations.
Platform-Managed Validations
These validations are automatically enforced on every send, regardless of the makeup of the email content. They make sure that your email send meets system and compliance requirements.
| Send validation | Details |
|---|---|
| From Address Authorization | Unified Messaging verifies that the sending email address is authorized for use. Sends from unapproved addresses are blocked. Not_Sent Engagement Action reason
How to pass validation Set up and verify authenticated From Addresses to use for your messages. |
| Sending Allowance Limits | Unified Messaging tracks your contractual send allowance and stops sends that exceed your limit. (Applicable only in Starter, Pro Suite, and Foundations editions) Not_Sent Engagement Action reason
How to pass validation Before executing a campaign, check Usage-Based Entitlements in Setup (Company Information page) for remaining available Marketing Email Sends per Day/Month resources. For more information, see Marketing Considerations for Salesforce Starter and Pro Suite |
| Recipient Consent Status | For promotional messages, Unified Messaging automatically suppresses sends to recipients who haven’t provided opt-in consent to the Communication Subscription applied to the send. If the email isn't sent to the primary recipient, it won't be sent to CC recipients. Not_Sent Engagement Action reason
How to pass validation Ensure recipients have an explicit OptIn consent value before sending For more information, see |
| Hard Bounce Suppression | Unified Messaging prevents sends to email addresses that previously resulted in a hard bounce. If the email isn't sent to the primary recipient, it won't be sent to CC recipients. Not_Sent Engagement Action reason
How to pass validation Update or remove invalid email addresses from your subscriber list For more information, see Marketing Cloud Email Bounce Management |
| Recipient Address Validation | Unified Messaging validates that the recipient includes an email address before attempting a send. Not_Sent Engagement Action reason
How to pass validation Ensure targeted individuals have a Contact Point Email For more information, see Customer 360 Data Model: Individual and Contact Points. |
| Preference Center Configuration | If your transactional messages include merge fields for a preference center (such as PCToken or UnsubUrl), Unified Messaging requires that this feature be enabled for your account. If it isn't, the send will fail. Not_Sent Engagement Action reason
How to pass validation Make sure you have a published preference center page. For more information, see Edit a Default Preference Page in Marketing Cloud Next. |
CC Recipient Validations
These validations apply when CC recipients are included in a Send Email Message action.
| Send validation | Details |
|---|---|
| Primary Recipient Send Gate | If the primary recipient isn't sent, CC recipients aren't sent for that message attempt. This behavior applies to validation failures such as missing consent or hard bounce suppression. Not_Sent Engagement Action reason
How to pass validation Resolve the primary recipient send issue and try again. |
| Synthetic CC Internal Domain Suppression | When synthetic CC behavior is enabled for replies only, internal CC addresses are skipped for the outbound CC send. Not_Sent Engagement Action reason
How to pass validation Remove internal addresses from CC, or turn off synthetic CC for this send. |
Content-Dependent Validations
Unified Messaging also checks for email content and data validity at send time. The success of these validations depends on the accuracy and completeness of your content and data.
