Email personalization basics for outreach

Start with a reason, not a field

The most effective personalization reflects why you're contacting this person in particular: an article they published, a topic their site covers or a gap your resource fills. Decide on that reason before choosing merge fields.

If the only personal detail in a message is a name, the message isn't really personalized.

Choose a small set of reliable fields

Every merge field is a promise that the data behind it is accurate. Start with a few fields you can fill for nearly every recipient, and add others only when you can fill them consistently.

{first_name}

From a named contact page, byline or team page—not guessed from an address.

{website}

The site's own name, written the way the site writes it.

{topic}

A specific article or theme you've actually read.

Avoid putting a field you rarely have in the subject line, where a gap is most visible.

Write fallbacks that read naturally

A fallback is the text used when a recipient's value is empty. Write it so the sentence still works. “Hi {first_name},” with the fallback “there” becomes “Hi there,” when no name is available.

Read each sentence aloud with the fallback in place. If it sounds awkward, rewrite the sentence rather than forcing the field.

Preview the awkward records

Templates usually look fine for the first recipient. Problems hide in the others: missing names, website titles written in capitals, long brand names or topics that don't fit the sentence.

Step through several previews—especially records with missing fields—before you send anything. If a required field is missing and there's no sensible fallback, remove that recipient or complete the data first.

Keep details accurate and professional

A wrong name or a misremembered article does more harm than no personalization at all. Check the data you merge, and keep to details related to the recipient's public work. Avoid references to personal information that has nothing to do with why you're writing.

Stay consistent across follow-ups

Use the same fields and tone in follow-ups as in the first message, and make sure each step adds something: useful context, a shorter request or a polite close. A follow-up that only repeats the first email adds little.

A quick personalization checklist