Merge Tags & Personalization
Merge tags let you personalize every email for each prospect automatically.
Built-in Tags:
- {{firstName}} — Prospect's first name
- {{lastName}} — Prospect's last name
- {{email}} — Prospect's email address
- {{company}} — Company name
- {{role}} — Job title / role
- {{city}} — City
- {{country}} — Country
- {{industry}} — Industry
- {{website}} — Company website
- {{phone}} — Phone number
- {{linkedinUrl}} — LinkedIn profile URL
LinkedIn-Specific Tags (in LinkedIn campaigns):
- {{headline}} — LinkedIn headline
- {{location}} — LinkedIn location
- {{jobTitle}} — Job title from LinkedIn profile
- {{sender_name}} — Your name (the sender)
Sender Tags:
- {{sender_name}} — Your display name
- {{sender_email}} — Your email address
- {{sender_company}} — Your company name
Custom Fields:
When importing prospects via CSV, any column not matching a built-in field becomes a custom field. For example, a CSV column 'department' maps to custom:department, and you can use it as {{custom.department}} or {{department}} in your emails. The {{custom.department}} syntax is recommended (and what the variable picker inserts), but the bare {{department}} shorthand also works.
Custom Fields in Subject Lines:
Custom fields from your CSV work everywhere — including the subject line. If you import a CSV with a custom:subject_line column, you can set your entire subject to {{custom.subject_line}} or {{subject_line}}. For fully pre-written emails, your subject line could be just {{custom.subject_line | default: 'Quick question'}} — each prospect gets their own unique subject.
Fallback Values:
Use the Liquid-style syntax for defaults: {{firstName | default: 'there'}} renders as 'there' if firstName is empty.
Best Practices:
- Always preview your email before sending to check how merge tags render
- Use merge tags in subject lines for higher open rates
- Keep personalization natural — don't over-stuff with tags
- Test with a small batch first to catch any empty fields