Upcoming Mandatory Changes to Public Key Infrastructure (PKI)

Salesforce Enforces New Security Requirements in Summer 2026

Extend Salesforce with Clicks, Not Code

Table of Contents

No results

Here are some search tips

Check the spelling of your keywords.
Use more general search terms.
Select fewer filters to broaden your search.

Search all of Salesforce Help

Merge Field Tips

You are here:

Merge Field Tips

Here are a few pointers for getting the most out of merge fields.

Available in: both Salesforce Classic and Lightning Experience

The available merge fields vary according to which Salesforce edition you have.

To make sure you’re using the correct syntax, select merge fields from the merge field picker.

To use a merge field as the destination of a link, insert the merge field after http://.
Salesforce rounds decimal values referenced in merge fields on email templates to three digits regardless of locale.
You can store the name of an account, contact, or lead in your organization’s default language (the local name), in addition to the account or user’s default language (the standard name). If the local name is blank, the standard merge field name is used.
To reference a standalone file, use $Resource.<resource_name>, where <resource_name> is the name you specified when you uploaded the resource.
If you're using the Translation Workbench to translate custom field names, users can look up merge fields in their chosen language.
You can’t use a lookup field as a merge field in an email template. You can, however, create a hidden formula field on the page layout that pulls the value from the lookup field. Then include the hidden field in the email template.