Sales rep, Sales manager
Gong Engage*
General guidelines for variables
All variables must use double curly brackets: {{object.field_name}}
Examples:
{{opportunity.created_date}}
{{sender.first_name}}
Custom comments or placeholders should use single curly brackets: {Add your comment here}
You can insert variables:
By typing {{ directly into the subject or body
Or by using the variable button in the email editor
Valid variables are underlined in purple, invalid variables are underlined in red and will block saving
Hyperlink variables
You can hyperlink text with a variable in templates, blocks, or flows in two ways.
Method 1
Highlight the text you want to hyperlink.
Click Insert link.
In the link box:
Text: Confirm the text you want to display.
Link: Enter the variable (e.g., {{sender.primary_scheduling_link}}).
Method 2
Insert the variable (e.g., {{sender.primary_scheduling_link}}) directly into the body of the template.
Highlight the variable.
Click the Insert link.
In the link box:
Text: Confirm the text you want to display.
Link: Enter the variable (e.g., {{sender.primary_scheduling_link}}).
Variables in URL
You can embed variables inside a URL. For example:
https://www.google.com/search?name={{recipient.first_name}}
Formatting dates and numbers
You can use the format_date and format_number functions in variables to control how values appear in your emails, without editing the original CRM field.
format_date function
Use format_date to change how a date field is displayed. The default output is typically ISO format (2025-07-08), but you can make it more readable or conversational.
Format: {{format_date object.field ‘format_string’}}
Supported date formats
Format string | Output example (July 8, 2025) |
---|---|
‘MM/dd/YYYY’ | 07/08/2025 |
‘dd/MM/YYYY’ | 08/07/2025 |
‘MMMM d, YYYY’ | July 8, 2025 |
‘d MMM YYYY’ | 8 Jul 2025 |
‘MMM d’ | Jul 8 |
‘dddd, MMMM d’ | Tuesday, July 8 |
Example usage:
{{format_date opportunity.close_date ‘MMMM d, YYYY’}}
→ July 8, 2025
Date format reference
When using format_date, make sure to match the correct uppercase and lowercase formatting strings. These formatting strings are case-sensitive. For example, writing mm instead of MM will return minutes instead of months.
Format | Example output | Meaning | Notes |
---|---|---|---|
d | 2 | Day of week (0–6) | Lowercase |
dd | Tu | Min day name | Lowercase |
ddd | Tue | Short day name | Lowercase |
dddd | Tuesday | Full day name | Lowercase |
M | 10 | Month number | Uppercase |
MM | 10 | Month number | Uppercase |
MMM | Oct | Short month name | Uppercase |
MMMM | October | Full month name | Uppercase |
YY | 24 | 2-digit year | Uppercase |
YYYY | 2024 | 4-digit year | Uppercase |
format_number function
Use format_number to control how numeric fields appear. You can add commas, decimal points, or currency formatting.
Format: {{format_number object.field ‘format_string’}}
Supported number formats
Format string | Output example (1234567.89) |
---|---|
Example usage:
{{format_number opportunity.amount ‘$0,0.00’}}
→ $1,234,567.89
Using custom variables
If you need to create custom variables:
Email [email protected] with:
Variable name
Description
Each user must go to My Settings > Custom Variables (under Email) to enter values.
Custom sender variables are available under the {{sender.}} object.
Examples:
{{sender.primary_scheduling_link}}
Reviewing migrated content from Outreach or Salesloft
If your team migrated templates or flows into Gong Engage, review each item to ensure variables were converted correctly.
You can only review and update each user’s personal templates and flows if you’re a Gong technical admin. To do this, go to the Team members page and select Log in as for each user.
What Gong auto-converts:
{{recipient.first_name}}
{{recipient.last_name}}
{{recipient.company_name}}
{{recipient.job_title}}
{{sender.first_name}}
{{sender.last_name}}
{{sender.job_title}}
{{sender.phone_number}}
if, if/else, and unless statements
What you need to fix manually:
Variables that couldn't be converted will appear as comments ({...}).
Replace these with the correct variable format:
Contact first name → {{contact.first_name}}
Sender company name → {{sender.company_name}}
Nickname → {{account.nickname}}
Account ID18 → {{account.account_ID18}}
Lead 18 Digit ID → {{lead.lead_18_digit_id}}
Variables in URLs
Before:
https://calendly.com/{sender.custom1}/english-optimization-call
After:
https://calendly.com/{{sender.calendly_username}}/english-optimization-call
Conditional URLs are supported too. For example:
https://calendly.com/{{sender.calendly_username}}/sync?sfid={{#if contact.Contact_18_Id__c}}{{contact.Contact_18_Id__c}}{{else}}{{lead.Lead_18_Digit_ID__c}}{{/if}}
Or outside the URL:
{{#if contact.Contact_18_Id__c}} <Insert link version 1> {{else}} <Insert link version 2> {{/if}}
Replace outdated variable formats in the body:
Recipient first name → {{recipient.first_name}}
Sender company name → {{sender.company_name}}
Nickname → {{account.nickname}}
Account ID18 → {{account.account_ID18}}
Lead 18 Digit ID → {{lead.lead_18_digit_id}}
Replace outdated variable formats in the subject line:
{{RECIPIENT_FIRST_NAME}} → {{recipient.first_name}}
{{SENDER_COMPANY_NAME}} → {{sender.company_name}}
{{ACCOUNT_Nickname__c}} → {{account.nickname}}
{{ACCOUNT_ID18__c}} → {{account.account_ID18}}
{{LEAD_Lead_18_Digit_ID__c}} → {{lead.lead_18_digit_id}}
Update conditional logic
Old format:
If Recipient first name {{Hi}} Else {{Hi there}} Endif
New format:
{{#if recipient.first_name}} Hi {{recipient.first_name}}, {{else}} Hi there, {{/if}}
Other examples:
{{#if recipient.first_name}} Hi {{recipient.first_name}} → “Hi” or “Hi John”
{{#if recipient.first_name = Gal}} Hello Gal {{else}} Hello {{/if}} → “Hello Gal” or “Hello”
Update placeholder text
Old format:
{{Insert some research about the customer}}
New format:
{Insert some research about the customer}
Using day-of-week conditions with variables
You can use {{#is_wednesday}} to conditionally show content when the current date is Wednesday.
Example:
{{#is_wednesday}}
Hope your Wednesday’s going well.
{{/is_wednesday}}
You can also apply this logic to any date field, like the deal close date or a custom event date. For example:
{{#is_wednesday opportunity.close_date}}
Since your deal is closing this Wednesday, here’s everything you need to know.
{{/is_wednesday}}
This is helpful when you want to tailor your messaging based on the day of week of a specific event.
More example use cases:
Current date is Wednesday → {{#is_wednesday}}
Close date is Wednesday → {{#is_wednesday opportunity.close_date}}
Meeting date is Wednesday → {{#is_wednesday meeting.start_time}}
$(document).ready(function() { $('a[href="SLUG NAME"]').parent().css({"display": "none"}); $('a[href="SLUG NAME"]').parent().css({"display": "none"}); });