A merge tag is a placeholder in an email that is replaced with each recipient’s own data when the email is sent. Write “Hi {{first_name}},” and Priya sees “Hi Priya,” while Arjun sees “Hi Arjun,”. Merge tags can pull in any field you store: city, company, plan, last order date, loyalty points or a personal referral code.
The most important companion to a merge tag is a fallback value: what to show when the field is empty. Without one, a contact with no first name receives “Hi ,” which looks careless and signals that the email was automated. A sensible fallback, such as “there” or “friend”, reads naturally either way. Check how many contacts actually have each field before relying on it.
Merge tags go beyond greetings. In subject lines, a city or product name often works better than a first name, which people have grown used to seeing. In the body, numbers like “You have 340 points” or dates like “Your plan renews on 12 March” make an email genuinely useful rather than merely personal.
Data quality is the usual weak point. Names imported in capitals (“RAHUL”), placeholder names like “test” or “abc”, and fields filled with the wrong data all show up in personalised emails. Clean the most-used fields before a big send, and preview the email as a few real contacts, including someone with missing data.
A Kolkata bookshop sends “{{first_name|Reader}}, your Durga Puja reading list is here”. Subscribers with a first name see “Ananya, your Durga Puja reading list is here”, while those without one see “Reader, your Durga Puja reading list is here”.
MailNesto merge tags take a fallback after a vertical bar, as in {{first_name|friend}}, so contacts with an empty field still get a natural sentence.