A first name works best in an email when it shows up once or twice: in the greeting, and maybe in the subject line or a sign-off. Repeating it all through the copy reads like a mail-merge template, not like attention. Real personalization in November 2026 means content picked from what subscribers tell you and what they do, such as the products they browse, their preferences and the topics they click. Since this post was first written, Apple Mail Privacy Protection has made open rates unreliable for judging whether a name “worked,” and the Gmail and Yahoo bulk sender rules from 2024 mean that annoyed readers who hit “report spam” can now hurt your delivery directly.
The email that used one name 13 times
The first email from the pop-up sign-up form mentioned the other day has arrived, and it used the subscriber’s name 13 times. Every paragraph either started or ended with the name. If your email platform can personalize messages, that’s great. Abusing the feature is not.
Emma’s sixth trend in Emma’s Top Ten Email Trends fits this case. The list is from years ago, but the point still holds: a message should be more personal than “Dear Name.” That doesn’t mean you should drop the person’s name into the copy wherever it will fit.
An easy way to go further is to use the preference information and other customer data stored in your CRM. Send people content that matches their interests, and they will read your emails instead of counting how many times their name appears. For the record, this email also used the subscriber’s last name twice. And one last question: why 13 times? Isn’t that bad luck?
What good personalization looks like now
Good personalization changes what the email says, not just who it’s addressed to. The name is the smallest part of it. The parts that matter come from data the subscriber gave you or behavior they showed you.
| Personalization type | Example | Where the data comes from |
|---|---|---|
| Name in greeting | “Hi Dana,” once at the top | Sign-up form field |
| Preference-based content | Only running gear for a subscriber who chose “running” | Preference center or sign-up questions |
| Behavior-based content | Reminder about a category the subscriber browsed | Website or app activity synced to your ESP or CRM |
| Lifecycle timing | Welcome series, renewal reminder, win-back | Sign-up date, purchase history |
| Location | Store events or shipping cutoffs for their region | Address or stated location |
A few rules keep personalization from turning creepy or broken:
- Use the first name once or twice per email at most. The greeting is the natural place.
- Set a fallback value for every merge tag. In Mailchimp, for example, you set a default for the
*|FNAME|*tag in the audience’s merge tag settings, so a contact with no first name gets “Hi there” or “Hi Friend” instead of an empty space. - Skip the last name in marketing copy. It sounds formal and makes the mail-merge obvious.
- Only personalize on data the subscriber would expect you to have. “Since you signed up for the running newsletter” feels fine. Mentioning something they never shared with you does not.
- Send a test to a contact record with real data before every campaign. Test sends to addresses your platform has no data for often show the raw tag or a blank.
Overdoing it costs you more than an eye-roll now. Google’s email sender guidelines ask bulk senders (more than 5,000 messages a day to Gmail addresses) to keep user-reported spam below 0.1% and never let it reach 0.3%. Yahoo enforces similar rules, and since May 5, 2025 Microsoft has required SPF, DKIM and DMARC from domains sending more than 5,000 emails a day to Outlook.com. An email that feels fake to the people reading it pushes complaints toward those limits.
FAQ
How many times should you use a subscriber’s name in one email?
Once is usually enough, twice at most. The greeting is the standard spot, and a name in the subject line works now and then if you don’t do it in every send. Beyond that, the name reads as filler and draws attention to the template.
Does putting the first name in the subject line still raise open rates?
It’s hard to tell from open rates alone. Apple Mail Privacy Protection, introduced with iOS 15 in 2021, preloads images and logs an “open” whether or not anyone reads the email, which inflates opens for any audience heavy on Apple Mail. Judge personalization tests on clicks, conversions and unsubscribes instead.
What happens if a contact’s first name field is blank?
Without a fallback value, the greeting renders as “Hi,” or shows the raw merge tag, which looks careless. Most ESPs, Mailchimp included, let you set a default value for each field, such as “there” or “Friend.” Cleaning up obviously bad name data at sign-up helps too, since a name typed in all caps or as “asdf” will show up exactly as entered.
Can over-personalization hurt deliverability?
Not directly. Mailbox providers don’t filter mail based on how often a name appears. They do filter on spam complaints, though, and Gmail and Yahoo treat a complaint rate approaching 0.3% as a serious problem for bulk senders. Copy that feels fake or intrusive gets reported more often, so overdoing it can hurt your delivery indirectly.
Is it legal to personalize emails with CRM data?
In the US, CAN-SPAM regulates honest headers and subject lines, a physical address and a working opt-out honored within 10 business days, not personalization itself. Violations can cost more than $53,000 per email under the FTC’s current penalty figures. If you email people in the EU or UK, GDPR also requires a lawful basis for processing the personal data you use, so only personalize with data you collected properly.
Sources
- Google Workspace Admin Help: Email sender guidelines and the sender guidelines FAQ (support.google.com)
- Yahoo Sender Hub: Sender best practices (senders.yahooinc.com)
- Microsoft Tech Community: Outlook’s new requirements for high-volume senders, April 2025 (techcommunity.microsoft.com)
- Federal Trade Commission: CAN-SPAM Act, A Compliance Guide for Business (ftc.gov)
- Mailchimp Help: Getting started with merge tags and setting default merge values (mailchimp.com)
- Twilio SendGrid Docs: Understanding Apple Mail Privacy Protection and open events (docs.sendgrid.com)