You will be able to personalise the content, timing and offers in your emails, using more than a first name in the greeting.
Set fallback text for every merge field and check your name field before any big send. After that, put your effort into the two kinds of personalisation readers notice: different content for different people, and emails timed to something the person did.
When personalisation is done badly, the reader can tell straight away that a machine sent the email to thousands of people, which is the opposite of what you wanted. The usual failures are in the greeting. A name in capitals gives "Hi JASON". An empty field gives "Hi ," with a stray comma. An unfilled placeholder gives "Hi [FIRST NAME]". Personalisation is worth doing, but the first name in the greeting is the smallest part of it and the riskiest.
Every email tool has merge fields. A merge field is a placeholder that the tool replaces with each subscriber's data when the email goes out. The first-name field is the one most people use, and it causes the most trouble.
The name field is empty for anyone who signed up without giving a name, and for anyone you imported from a list that had no names. Where people did type a name, they typed it in all sorts of ways: all capitals, all lowercase, with a surname, as a nickname, as a business name, or as something rude. Whatever they typed will appear in your greeting.
Two habits fix most first-name problems. The first is to always set fallback text, the word or words the tool uses when a merge field is empty. "Hi there" works, and so does plain "Hi". If you don't set one, the reader gets "Hi ," or worse. Every email tool lets you set a fallback, but the setting is in a different place in each tool, so look for it in yours before you rely on the name field.
The second habit is to sort the name field before a big send and scan it for blanks, odd capitals and obvious junk. You don't need to fix every entry. Tidy the worst of them.
In practice you insert the first-name merge field after "Hi", set the fallback, then sort and check the field and tidy the worst entries before you send. Even when you do all of this well, a first name is a small touch. People know the email is automated. Their name makes it read more like a message, but the content is no more relevant to them than before.
Most email tools can show or hide a block of content depending on a tag or field. This is usually called conditional content, or dynamic content. You send one email, and different readers see different paragraphs. This often works better than writing two separate emails, because you write the shared part once and only change the part that needs to differ.
Priya runs classes for children, and at the end of term she sends one email. The main section, a tip for revising over the holidays, goes to everyone. Families who are enrolled also see a paragraph about next term's timetable and a link to confirm their child's slot. Parents who haven't enrolled see a paragraph inviting them to a trial class in the first week of term instead. It's one email and one send, with two different next steps, and each reader gets the one that fits them.
To set this up, Priya uses the customer tag from Lesson 6.2: show block A if the contact has the tag, and block B if not. You can do the same. Write the shared content first. Decide which part should differ and which tag or field it depends on. Then create block A for contacts who have the tag and block B for those who don't.
Before you send, preview the email as a contact from each segment. Most tools have a "preview as" option. Check that every reader gets a block, and that nobody gets both blocks or neither.
The personalisation people notice most often has no name in it at all. It's an email that arrives at the right moment because of something the person did. Examples are a booking reminder the day before a trial class, a care note on storing leftovers two days after a cake is collected, or a birthday reminder a few weeks before a child's birthday comes round again (sent only if the parent shared the date). None of these needs "Hi Jason" at the top. They feel personal because they're about the reader's own situation and arrive while that situation is still current.
Emails like these are triggered by events instead of going out on your newsletter schedule, and they're called automations. Timing is a form of personalisation, and it's often the strongest kind. Module 7 covers how to build automations.
Mei Ling runs a cake business, and her monthly email uses all three kinds of personalisation together. The greeting is "Hi" plus the first name, with "Hi there" as the fallback. The opening section, about December dates, goes to everyone. In the middle, customers who have ordered before see "Order again with your saved details" and a link to their account. Non-customers see three photos of recent cakes and a line on how ordering works. Everyone gets the same sign-off and the same footer.
Before she sends, Mei Ling previews three versions: as a customer, as a non-customer, and as a contact with no first name. She reads each one through to the footer. She's checking that the fallback appears where it should, and that each reader sees exactly one middle block.
When you write your own customer and non-customer email in the activity below, the trap to watch is the rule behind each block. If block A depends on the customer tag and block B on a different field, such as a purchase date, some contacts may match both rules or neither, so they see two middle paragraphs or none. Base both blocks on the same tag, one shown when the contact has it and one when they don't, as Priya does.
Write one email showing customers one paragraph and offer and non-customers a different one, with fallback text for every merge field. Then name one action a reader takes that should set off a separate timed email, and when it should arrive.
Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).