Sign inGet your API key
ProductDocsPricingCompareBlogSign in

Glossary

What Is Email Personalization?

How outbound teams tailor each message to one recipient, and which data fields make it possible.

Get your free API key →Free to start. No credit card. 1,000 records to spend whenever you like.

Email personalization is the practice of changing parts of an email, such as the greeting, the opening line or the offer, so they match facts about the one person who receives it.

Why it matters for outbound

A cold email has seconds to prove it was written for the reader. A message that names the right role and the right problem gets read. A generic one gets deleted.

Personalization only works when the data under it is correct. A wrong first name or an outdated job title is worse than no personalization, because it shows the sender did not check.

There are two levels. Merge fields insert stored values such as first name and company. Custom lines add a sentence about the person or the account, written by hand or by a model. Merge fields scale. Custom lines cost more time per email, so reserve them for small, high-value lists.

Example

Start with a record for a placeholder prospect:

code
first_name:  Jane
job_title:   VP of Sales
company:     Acme
industry:    Software
city:        Austin

A merge-field template reads:

code
Hi {first_name},

Teams selling into {industry} usually hit the same wall at your stage: reps
spend more time finding contacts than writing to them. Is that true at {company}?

Rendered for Jane Doe, it opens "Hi Jane" and refers to Acme and software. Add one custom line, such as a reference to a post she wrote, and the email moves from segment-level to person-level.

Keep the rule simple. Every variable must be filled for every row, or the send breaks. Drop rows with empty fields before you send, or give each variable a fallback.

In LeadOcean data

LeadOcean does not write or send emails. It supplies the fields you merge into them.

These export columns come from the search row, so you do not need an enrichment call to get them (GET /v1/exports/columns, September 2026):

  • profile_first_name for the greeting.
  • current_job_title for role-specific wording.
  • current_company_name for the account.
  • current_company_industry for segment language.
  • city for local references.
  • profile_headline for a hook in the opening line.

Pick them in the column picker on the Exports page of the app, or list them in columns on POST /v1/exports. The same search row is what /v1/people/search and the MCP tool search_leads return.

The email address itself comes from the export or GET /v2/people/email/work, with an email_status you can filter on. See the exports docs (September 2026).

For the practical side, read personalizing emails. If you build addresses from a pattern, see what is an email pattern. Pricing is on /pricing. More definitions sit in the glossary hub.

Start with a list that has the fields to personalize each email

Free to start. No credit card. 1,000 records to spend whenever you like.

Get your free API key →