Marketing Cloud Engagement | Email Studio: Common Causes and Solutions for Failed or Undelivered Test Sends

When the email content includes AMPscript or personalization strings, a test send fails if you enter the email address directly in the Individual tab under Preview and Test. This happens because the subscriber whose data the AMPscript or personalization strings reference has not been determined. An error message such as "Emails containing subscriber specific AMPscript cannot be sent without selecting a subscriber in Test Send." appears. You must select a target subscriber in advance so that variable values can be resolved.

To specify a test subscriber, follow these steps:

To isolate the cause, you can also verify whether the email sends successfully after temporarily removing the relevant AMPscript, or confirm the subscriber by sending through a regular data extension — not a test — so that the subscriber is fully resolved.

The following are the most common causes seen in cases where test send emails are not delivered. Note that some of these causes can also occur during regular production sends.

Cause 1: The selected subscriber's status is Held or Unsubscribed
Test sends apply the same delivery exclusions as actual sends. If the selected subscriber's status is Held or Unsubscribed, the email is not delivered. Select a subscriber with an Active status and run the test again.

Cause 2: The data extension has multiple EmailAddress-type fields
When a data extension contains more than one EmailAddress-type field, MCE cannot determine which field to use as the email address, and sends to new subscribers not yet registered in All Subscribers are automatically skipped. Configure the data extension so that it has exactly one EmailAddress-type field, then run the test send again.

Cause 3: The email address field is a Text type
If the email address field in the sending data extension is a Text type, MCE cannot correctly recognize it as a send target. In some cases this causes the test send to fail for new subscribers. Use a data extension where the email address field is set to EmailAddress type.

Cause 4: CAN-SPAM validation is not passing (missing physical mailing address or profile center in the email)
In environments where CAN-SPAM validation is enabled, errors such as "A profile center link is missing from this email..." or "The email is missing a valid physical mailing address..." indicate that the email is not passing CAN-SPAM validation. In environments where this setting is active, the send is blocked and fails if the email body or footer does not correctly include a link to the profile center (such as %%profile_center_url%%) and the sender's physical mailing address.

 

Q) I selected a test data extension under the recipient options, but the desired data extension does not appear in the list.
A) Only data extensions that have both Sendable and Testable checked (that is, "Use for Testing" is set to Yes) are available. Check the data extension properties to confirm whether it is a testable data extension. Note that filtered data extensions have this setting turned off by default, so you must enable it manually.