Mailchimp merge tags are placeholders like *|FNAME|* that Mailchimp swaps for each contact's own data when the email goes out. Type Hi *|FNAME|*, and Anna reads "Hi Anna,". Every field in your audience has a tag, and Mailchimp adds system tags for the unsubscribe link, the date, the subject line and your address.
TLDR: Use
*|FNAME|*for names, set a default value so empty names don't leave you with "Hi ,", and test in Preview mode, because conditional tags never fill in test emails.
How Mailchimp merge tags work
Each merge tag sits between *| and |*. When Mailchimp sends, it reads the contact's record and replaces the tag with what it finds.
- Audience field tags come from your contacts:
*|FNAME|*,*|LNAME|*,*|EMAIL|*, plus any field you create. - System tags come from Mailchimp:
*|UNSUB|*,*|ARCHIVE|*,*|CURRENT_YEAR|*and so on.
To see the tag for each field in your audience, go to Audience, open More options, then Audience fields and merge tags. The tag name is listed next to each field. A custom field like "Plan" gets its own tag, for example *|PLAN|*.
The merge tags you'll actually use
Mailchimp lists over 100 tags. These are the ones that turn up in almost every newsletter.
About the contact:
*|FNAME|*: first name. Greeting and subject line.*|LNAME|*: last name. Formal greetings.*|EMAIL|*: email address. Footer ("sent to...").
About the email:
*|MC:SUBJECT|*: the subject line, often used as the page title in custom code.*|MC_PREVIEW_TEXT|*: preview text in custom-coded emails.*|ARCHIVE|*: a "view in browser" link, usually at the top.*|DATE:d/m/y|*: the send date, in the format you write after the colon.*|CURRENT_YEAR|*: the current year, for the copyright line.
For the footer:
*|UNSUB|*: the unsubscribe link (required).*|UPDATE_PROFILE|*: the update preferences link.*|LIST:COMPANY|*: your company name from the audience footer settings. Works in subject lines too.*|HTML:LIST_ADDRESS_HTML|*: your mailing address plus an "add us to your address book" link.*|FORWARD|*: the Forward to a Friend link.*|LIST:SUBSCRIBERS|*: your contact count as text, for a social proof line.
*|UNSUB|* and *|UPDATE_PROFILE|* must be turned into links with the link tool, or they show as plain text.
Copy-paste examples
A greeting:
Hi *|FNAME|*, here's what we shipped this week.
A subject line:
*|FNAME|*, your November picks from *|LIST:COMPANY|*
A footer:
You're getting this because you signed up at *|LIST:COMPANY|*. Sent to *|EMAIL|*. Unsubscribe | Update preferences
(Link "Unsubscribe" to *|UNSUB|* and "Update preferences" to *|UPDATE_PROFILE|*.)
A copyright line:
© *|CURRENT_YEAR|* *|LIST:COMPANY|*
What happens when a contact has no first name
If a contact never filled in their name, Hi *|FNAME|*, becomes "Hi ,". There are two fixes.
Fix 1: a default merge tag value
This works everywhere, subject lines included.
- Click Audience and pick the right audience.
- Open More options, then Audience fields and merge tags.
- Click the three dots next to FNAME, then Edit.
- Type your fallback in Default merge tag value, for example "there" or "friend".
- Click Save.
The default only shows in sent emails. It is never saved into the contact's record. You can't set one for the Email Address or Address fields.
Fix 2: an IF/ELSE block
This gives you a different sentence, not just a different word:
*|IF:FNAME|*Hi *|FNAME|*,*|ELSE:|*Hi there,*|END:IF|*
Conditional merge tags (IF, ELSE, IFNOT)
Conditional tags show a block only to the contacts who match. Every block ends with *|END:IF|*, in the same content block as the opening tag.
*|IF:FIELD|*: shows the content if the field has a value (or matches).*|ELSE:|*: shows the content when the condition is false.*|ELSEIF:FIELD|*: checks another field if the first test failed.*|IFNOT:FIELD|*: shows the content when the field is empty or false.*|END:IF|*: closes the block.
You can compare with =, !=, >, <, >= and <=. An example with a custom "Plan" field:
*|IF:PLAN=Pro|*Your Pro report is attached.*|ELSE:|*Upgrade to Pro to get the full report.*|END:IF|*
Know the limits before you build anything clever:
- No conditional tags in subject lines. Use a default value there.
- They don't fill in test emails. Use Preview mode.
- They read audience fields and groups, not Mailchimp tags.
- No AND or OR. Nest blocks or create a field that holds the combined value.
Change how a value looks
Wrap any field tag to change its format:
*|TITLE:FNAME|*turns "anna" into "Anna"*|UPPER:FNAME|*gives "ANNA",*|LOWER:FNAME|*gives "anna"*|URL:FNAME|*encodes the value for use inside a link*|HTML:FIELD|*outputs the value as raw HTML
*|TITLE:FNAME|* is the quiet fix for lists where people typed their name in lowercase.
How to test merge tags before you send
- Open Preview mode and check the email as a real contact, not just as the template.
- Check one contact with no first name to see your fallback.
- Read the subject line out loud with the tag filled in. "Anna, your November picks" works; a tag mid-sentence often doesn't.
- Send a test for layout, but remember conditional blocks stay empty there.
Personal greetings don't help if the email lands in spam. If your open rate has dropped, check your sender domain first with our Mailchimp spam fix guide.
Keeping merge tags when you write the email in another tool
Lots of teams write the newsletter somewhere else and send it with Mailchimp. That is where tags break: in Markdown, the asterisks in *|FNAME|* read as italics, so a tool can strip them and Mailchimp receives |FNAME| as plain text.
Mydrop keeps them. Mydrop is the social media OS for agencies and multi-brand teams, managing 70,000+ posts, and its Mailchimp integration sends your newsletter as a campaign to your own audience:
- Write the email in the same composer as your social posts.
*|FNAME|*and other merge tags stay exactly as you typed them, and Mailchimp fills them in. - Schedule it on the content calendar next to the posts it promotes, send it now, or save it as a Mailchimp draft.
- A warning shows before sending if your sender domain isn't authenticated in Mailchimp.
Your contacts and their fields stay in Mailchimp, so every tag above keeps working. For a weekly format that fits, see how to turn your social posts into a newsletter, and for other tools that connect to Mailchimp, our list of Mailchimp integrations.
Your next step
Open your next newsletter, add *|FNAME|* to the greeting and the subject line, then set a default value on FNAME so nobody gets "Hi ,". Preview it as a contact with no name before you schedule it.













































Google review
Trustpilot review