Considerations for Using Merge Fields for Person Accounts
A merge field is a field you can put in an email, an email template, a mail merge
template, a custom link, or a formula to incorporate values from a record. You can use merge
fields in the subject and body of custom HTML templates. When using merge fields, it’s a good
idea to understand how they work and what to expect in your merged documents and
emails.
Required Editions
Business accounts available in: both Salesforce Classic and Lightning
Experience
Business accounts available in: All Editions
Person accounts available in: Both Salesforce Classic and Lightning
Experience
Person accounts available in Professional, Enterprise,
Performance, Unlimited, and Developer Editions
If your organization uses person accounts, business account and person account fields
are available as account merge fields. Account fields exclusive to person accounts, such
as Birthdate, Email, and
Title have “Account.Person” in their merge field
names. For example, {!Account.PersonBirthdate}.
You can use the merge field {!Account.IsPersonAccount} to determine whether you are
working with a person account or a business account.
Account fields that previously had unique names and labels are no longer unique because
some contact fields are displayed as part of the account object. Look for the person
account icon () to
identify these fields. Ensure that all custom account fields have field names and labels
unique to your organization so that the merge field references the correct field.
Important
If two or more custom objects have
matching names or labels, only one of the objects appears when you select from
available merge fields. Make sure that all custom objects have unique names and labels
so that you can select merge fields from any of the objects.
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.