Customers are more likely to engage with your messaging when it’s personalized. Use
Handlebars merge fields to personalize content you create in Account Engagement with information from your prospect records. You can also insert information about your
company, like your business address, and create defaults to use when prospect records don’t
contain certain values.
Required Editions
Available in: All Account
Engagement Editions
Note Handlebars Merge Language (HML) is on by default in business units created after June 12,
2020. If your business unit was created before that date, we recommend upgrading to HML for
the latest functionality.
Handlebars Merge Fields in Account Engagement Handlebars Merge Language (HML) offers fields that represent business unit information, user information, and data from prospect records. To further personalize your content, create merge fields for any custom prospect or prospect account field not set to record multiple responses.
Use HML Conditional Merge Fields You can use Handlebars merge fields to create simple conditional logic statements in your Account Engagement content. These statements render default content when prospect records don’t contain a value for certain fields.
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.
HML Merge Field Modifiers in Account Engagement The merge field values you embed in your content can vary in format and use. Modifiers are strings added to merge fields that tell the system how to format the output. Handlebars Merge Language (HML) supports modifiers that protect sensitive information and keeps your embedded data clean for people to read.
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.
