Using Revenue Engage Merge Fields️

While creating a mass-sent messages in Revenue Engage, make use of powerful personalization feature - Merge Fields. It automatically inserts recipient-specific piece of data.

Merge field is available when:

- Adding a step to a Sequence,
- Building a template,
- Building a signature
- Building an unsubscribe text


For example this is how merge-fielded email will look when you send it, and how your recipient will see it:


In order to insert such value:

1. Put a cursor where auto-inserted value should appear in the message

2. Click {{ }} icon (insert merge fields) on the text editor toolbar

3. Choose what recipient-specific value you want to auto-insert into a mass email.

The value gets retrieved from Salesforce (recipient-specific data) or Revenue Engage (sender-specific data such as signature, campaign unsubscribe link, and more).

For use simplicity, instead of clicking the icon on the toolbar you may simply type “”{{” in message body and then browse through available merge fields in a picklist automatically brought up by Revenue Engage.

Commonly used merge field examples: Lead/Contact Salutation, Full name and Company name, RE Sequence starter’s (Owner’s) name and RE email signature, sequence unsubscribe link, etc.


Note

When you use {{Sender Phone Number}} type of a merge field, Revenue Engage will pull sender’s mobile number if available. In case if Mobile field is not populated, then it will show number set in Phone field.


Troubleshoot broken merge fields

To check a merge field’s validity, you need to enter preview mode by clicking the (Preview) icon on the left-hand side of the text editing bar and then choosing a recipient from “To:” dropdown (if you haven’t added recipients to the sequence yet, then “To:” field will show John Doe as a placeholder) whom you want to preview end result for. In preview mode, invalid merge fields are highlighted with red color and are not replaced by the needed values.

The best practice is to populate a missing field (highlighted red) on the recipients’ record in Salesforce. Otherwise remove the merge field tag from the message.

Important

While processing an email type of a Step, Revenue Engage checks whether all its merge fields can be filled (that is a corresponding value can be retrieved from Salesforce or RE). If a merge field cannot be filled, the automated email containing it will not be sent, instead it will be moved to Planner‘s To-Dos tab.


Available Merge Field values

Possible recipient-specific values pulled from Salesforce

First Name Mailing City Photo URL Lead Source
Last Name Mailing State/Province Clean Status Status
Full Name Mailing Zip/Postal Code Level Industry
Title Mailing Country Languages Rating
LinkedIn Mailing Latitude Deleted Annual Revenue
Phone Number Mailing Longitude Salutation Employees
Skype Mailing Geocode Accuracy Company Converted
Building Business Phone Street Converted Date
Apartment Business Fax City Unread By Owner
Zip Home Phone State/Province Created Date
TimeZone Other Phone Zip/Postal Code Last Modified Date
Other Street Asst. Phone Country System Modstamp
Other City Department Latitude Last Activity
Other State/Province Assistant’s Name Longitude Last Viewed Date
Other Zip/Postal Code Birth date Geocode Accuracy Last Referenced Date
Other Country Contact Description Phone Company D-U-N-S Number
Other Latitude Last Stay-in-Touch Request Date Mobile Phone Email Bounced Reason
Other Longitude Last Stay-in-Touch Save Date Fax Email Bounced Date
Other Geocode Accuracy Is Email Bounced Email Current Generator(s)
Mailing Street Data.com Key Website
SIC Code Product Interest Primary
Number of Locations Jigsaw Contact ID Description

Possible sender-specific values pulled from Revenue Engage

First Name Sender Email Unsubscribe Text
Sender First Name Sender Title Unsubscribe Link
Sender Last Name Sender Phone Number User Signature
Sender Full Name Org Name User Alternative Signature

Special values

Values Description Example
today Inserts day of the week when an email gets sent out {{today}} → Friday
tomorrow Inserts the following day of the week when an email gets sent out {{tomorrow}} → Saturday
days_from_now N Inserts day of the week N days after the email gets sent out {{days_from_now 2}} → Sunday 
weekdays_from_now N Inserts day of the week N workdays after the email gets sent out {{weekdays_from_now 2}} → Tuesday