Using Merge Fields in Emails

Merge fields let you personalize Guided Selling emails with values from Salesforce records. You can use merge fields in Sequence emails, reusable Email Templates, and standalone emails.

The records available to a merge field depend on how the email is being sent. Sequence emails can use the additional record context provided by the Sequence Association. Standalone emails are not associated with a Sequence, so related-record merge fields are limited to relationships available directly from the Lead or Contact receiving the email.

Add a merge field

When composing an email, click Merge Field { } in the Rich Text Editor to insert an available merge field.

Common merge field types include:

• Participant: Values from the Lead or Contact receiving the email, such as name, title, or email address.
• Sender: Values from the Salesforce User sending or owning the email action.

For example:

{{{Participant.FirstName}}}
{{{Sender.Name}}}

Guided Selling uses its own merge field syntax. Salesforce Email Template merge syntax cannot be copied directly into a Guided Selling email without updating the field references.

Use fields from related records

You can also manually enter merge field references for supported related Salesforce records. The relationships available depend on whether the email is part of a Sequence.

Sequence emails

Sequence emails can resolve fields using both the participant and the additional Salesforce record context associated with the participant’s Sequence Association.

This allows you to reference fields from related records such as Accounts, Opportunities, Users, and custom objects through standard or custom parent relationships.

For example:

{{{Participant.Account.Name}}}
{{{Participant.Account.Owner.Email}}}
{{{Opportunity.SyncedQuote.Account.Id}}}

Sequence email merge fields support relationship paths up to four relationship levels.

This is useful for Sequences based on records such as Opportunities or Campaigns because the Sequence Association identifies the record related to that participant’s enrollment. Guided Selling can therefore resolve a relationship path using the specific record associated with that Sequence.

Standalone emails

Standalone emails are sent directly from a Lead or Contact and do not have a Sequence Association. Guided Selling therefore resolves merge fields from:

• The Lead or Contact receiving the email
• The sender
• Supported parent records directly related to that Lead or Contact

For example, when sending to a Contact you can reference a field on its Account:

{{{Account.Name}}}

You can also reference a field through a supported custom lookup directly on the Lead or Contact.

Standalone emails do not support the multi-level Sequence relationship paths used to retrieve values from records whose context comes from a Sequence Association. For example, a standalone email cannot determine which Opportunity should be used for a merge field simply because the Contact may be related to one or more Opportunities.

Sequence emails compared with standalone emails

Custom relationship examples

When using a custom Salesforce relationship, enter the relationship using its API name.

For Sequence emails, a relationship path can continue through additional parent records when required:

{{{Participant.Custom_Account__r.Owner.Email}}}

For a standalone email, the related record must be directly reachable from the Lead or Contact. For example:

{{{Custom_Account__c.Name}}}

The exact relationship and field names depend on your Salesforce configuration.

Test merge fields

When working with reusable Email Templates or Sequence emails, use Send Test Email when available to verify that merge fields resolve with representative Salesforce data.

For manually entered relationship paths, test records that contain the relationships and values you expect to use.