How User Merge Fields Populate in Account Engagement Emails
When sending an email, the way your user Handlebars Merge Language (HML) fields
populate depends on a few factors. Is the recipient assigned to a user? Is the email sent from a
user or from a general name and address? When choosing a From address sender, the email send
logic cascades to the next specified sender.
Required Editions
Available in: All Account
Engagement Editions
Note If you’re using legacy variable tags, they populate in emails the same way that HML
merge fields do.
User merge fields populate in an email based on these settings.
Sender Setting
Description
Sender is Prospect CRM User Custom Field
Name and email populate from the value stored in the Prospect CRM User custom
field.
Other user fields populate from the Prospect CRM User’s record.
If the prospect has no value for the Prospect CRM User field, the email
appears to come from the account owner. If there’s no account owner, the email
appears to come from the prospect’s lead or contact owner in the CRM.
If the prospect has no assigned user, the From Sender is the selected general
user or specific user.
Sender is Account Owner
Name and email populate from the prospect’s assigned user.
Other user fields populate from the prospect’s assigned user’s record.
If the prospect has no assigned user, the From Sender is the selected general
user or specific user.
Sender is Specific User
Name and email populate from the selected user’s record.
Other user fields populate from the selected user’s record.
Sender is General User
Name and email populate from the specified information.
Other user fields are replaced with blank values.
Sending Account Engagement Email in Salesforce
Name and email populate from the connected Account Engagement user.
Other user fields populate from the connected Account Engagement user’s
record, even if the user is different from the lead or contact owner.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
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
Always Active
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
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
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.