The 5 personalization variables that matter

  1. Recent action. "Saw your comment on X's post yesterday."
  2. Specific topic. Reference a topic from their last post or a session they attended.
  3. Mutual context. Shared connection, school, group, employer.
  4. Time-sensitive event. "Congrats on the new role at X."
  5. Disagreement signal. "Respectfully disagree with your post about X. Here's why..."

Mail-merge fields such as a first name can address the recipient, but they do not explain why you are contacting them. Use verified context to connect the opener to your reason for writing.

Writing a LinkedIn outreach sequence that earns replies
Run LinkedIn sourcing and outreach from one place.

Personalization tiers and context to verify

TierExampleContext to verify
Mail-merge only"Hi {firstName}"Check the recipient's name and preview the greeting.
Industry/role match"Hi {firstName}, fellow {role} here"Check the current role and whether the shared-role claim is true.
Specific signal"Saw your comment on {Author}'s post about {topic}"Read the comment and source post; confirm the author, topic and date.
Custom researched"Loved your point about X in {podcast episode}"Check the episode and the specific point before referring to it.

Choose the context that supports a relevant reason to write. Record its source, verify the detail and review the opener before reuse. The table describes those checks; it does not rank reply-rate performance.

Prepare verified context for a Leadsforlinked campaign

Before using source context in a campaign, review the actual lead record or export. Keep the following as manual research notes where relevant and verified; this checklist does not describe automatic export fields:

  • Post URL they commented on
  • Event name they registered for
  • Group they're a member of
  • Signal date

In the current campaign editor, use only variables it actually supports and confirm how each field is mapped. Preview a record with a value and one without it. If the context cannot be mapped, write and review that opener manually; do not assume a research-note label is a working campaign token.

A repeatable personalization review

  • Filter aggressively before you write any copy.
  • Source from warm signals only (post commenters, event attendees, signals).
  • Use 3-5 templates per signal type, not 100 hand-crafted variants.
  • A/B test the personalization line, not the pitch.

Frequently asked questions

Is mail-merge personalization ({firstName}, {company}) enough on its own?

A name or company field identifies the recipient but does not explain your reason for contacting them. Add a relevant detail you have verified, connect it to the purpose of the message, and preview the result. This guide does not establish a reply-rate lift for either approach.

How can a team reuse personalization without skipping research?

Reuse a structure for each type of context, while checking the source and relevance for each recipient. Keep manual notes when the needed detail is absent from the lead record. Map only variables supported by the current campaign editor, then preview populated and missing values before sending.

What should teams A/B test in a personalized campaign?

The personalization line itself, not the underlying pitch. Testing which signal type (post comment, event attendance, job change) produces the best reply rate for a given audience tells you where to invest sourcing effort, which usually matters more than testing pitch phrasing.

How many message templates does a personalized campaign actually need?

Roughly 3 to 5 templates per signal type is usually enough. The goal isn't a unique message for every prospect, since the signal itself provides the specificity; the template just needs a slot for that signal to plug into.

Build your next outreach workflow.

If your next task is running sequences and handling replies, review Starter for campaigns and the Inbox. Prepare the context for each recipient and check the current plan and campaign fields before choosing your workflow.

Start free