Merge Tag
A placeholder in email content that is replaced with personalized subscriber data when the email is sent.
Definition
A merge tag is a placeholder variable in email content that gets replaced with subscriber-specific data when the email is sent. Common merge tags include first name, company, location, or custom fields. Merge tags enable personalization at scale, making each email feel individual despite being sent to many recipients.
Why It Matters
Personalized emails perform significantly better than generic ones. Using merge tags for names, preferences, and other data makes emails feel personal and relevant. Even simple personalization like using the subscriber's name improves open and click rates.
How It Works
You insert merge tag syntax (varies by ESP, often {{first_name}} or |FIRST_NAME|) into your email template. When the email is sent, the ESP replaces each tag with the corresponding data from the subscriber's record. Fallback values can be set for missing data.
Best Practices
- 1Always set fallback values for merge tags in case data is missing
- 2Use personalization beyond just first name for more impact
- 3Preview emails to verify merge tags render correctly
- 4Keep subscriber data clean to ensure accurate personalization
Merge Tag Example Table
| Merge tag | Output example | Good fallback |
|---|---|---|
{{first_name}} |
Sarah | there |
{{company}} |
Acme Inc. | your team |
{{plan_name}} |
Pro | your plan |
{{renewal_date}} |
July 1 | your renewal date |
Merge Tag Risk Table
| Risk | What recipient sees | Prevention |
|---|---|---|
| Missing value | "Hi ," | Always set fallback text |
| Wrong field mapping | Incorrect name or company | Test with real sample records |
| Sensitive field | Overly personal or private detail | Use only data that adds clear value |
| Long value | Layout breaks or subject truncates | Preview with maximum-length examples |
Merge Tag Placement Table
| Placement | Good use | Caution |
|---|---|---|
| Subject line | Relevant account or company context | Missing fallback is highly visible |
| Greeting | Light personalization | Do not rely on it as the only personalization |
| CTA copy | Plan or goal-specific action | Keep button text short |
| Body copy | Specific usage or milestone detail | Avoid sounding invasive |