Note: this article is only applicable to Marketing Cloud Account Engagement customers who are utilizing the New Campaign Experience with Marketing Cloud Features for Account Engagement.
When sending a Marketing Cloud Next email, you may realize that email are never delivered and encounter flow errors in reporting (see Flow Run Details by Individual type reports).
This can be caused by using Account Engagement specific merge fields within your email content. These merge fields can only be rendered when sending email via Account Engagement on Email Content records. However, these Account Engagement specific merge fields are visible in the content builder when building and sending email via Marketing Cloud (If you do not have Account Engagement, you will not see the merge fields in your content builder).
If you attempt to send Marketing Cloud emails with these Account Engagement specific merge fields, the campaigns will allow you to activate the email send, but the email sends will fail in the backend and not be delivered due to rendering errors.
Below are a list of all Account Engagement specific merge fields categories that will cause rendering issues during email send time. Do not use any of these merge fields for email sends that are triggered from the campaign record.
| Merge Field Category | Examples of Merge Fields (not an exhaustive list) | Exceptions |
| Organization | {!$organization.Name} {!$organization.Phone} | EXCEPTION: the Physical Address field under the Organization category is allowed in Marketing Cloud (also seen as {!$organization.Address} in the content builder) |
| Recipient | {!$recipient.FirstName} {!$recipient.Name} {!$recipient.Company} | none |
| Sender | {!$sender.Email} {!$sender.Name} | none |
| Other | {!$other.Unsubscribe} {!$other.EmailPreferenceCenter} {!$other.View_Online} | none |
For emails sent via Marketing Cloud Next, please utilize any of the following merge fields:
| Merge Field Category | Notes |
Unified Individual | This option will not show up if you have a data graph configured in Marketing Cloud setup. |
Data Graph Attributes (shown as Select Data Graph Attributes) | This is only available if you have a data graph configured in Marketing Cloud Setup. |
Saved Expressions | This is only available if you have saved expressions configured for personalization. |
Select Event | To use event data, you must have first assigned an event to your message on the Data Source tab. This is only available for emails associated with event triggered flows. |
Link | Used for Unsubscribe and Preference Manager links |
Organization | Only the Physical Address field under the Organization category is allowed in Marketing Cloud (also seen as {!$organization.Address} in the content builder) |
004518450

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.