# Personalization With Merge Fields and Custom Fields

> Email personalization with merge fields and custom fields: clean contact data first, plan for blank values, and go beyond first names with segments and history.

Canonical: https://www.cresca.xyz/blog/personalization-tokens-in-cresca
Author: Lalit Kumar Jangid
Published: 2026-09-02
Last updated: 2026-10-28

Personalization usually fails for a boring reason: the data underneath it is messy. "Hi JOHN," "Hi ," and "Hi Test User" all come from the same place, a spreadsheet nobody cleaned before import. This post starts with the data, because that is where good personalization is won, and then shows how to use merge fields and custom fields in ways readers actually notice.

## What is the difference between merge fields and custom fields?

A merge field is a placeholder in your email that is replaced with a value from each contact's record at send time, such as a first name. A custom field is any extra information you store about a contact, like plan, city or join date, and it can be used both as a merge field and as a segment filter.

A **merge field** is a placeholder in your email that gets replaced with a value from each contact's record at send time. The classic example is a first name in the greeting.

A **custom field** is any extra piece of information you store about a contact beyond the basics: the plan they are on, the city they live in, the product they bought, the date they joined. Once a custom field exists, it can be used as a merge field in the message and as a filter when building a segment.

That second use is the one most teams underrate. Inserting a value into a sentence is nice. Sending a different email to people based on that value is where relevance comes from. Our guide to [email segmentation strategies](https://www.cresca.xyz/blog/advanced-email-segmentation-strategies) covers how to plan those groups.

## Decide what to store before you import

Resist the urge to import every column you have. Each field should earn its place by answering yes to at least one of these:

- Will I mention this value in an email?
- Will I send different content to people based on it?
- Will it decide when someone gets a message, for example a renewal date?

A short list for a typical small business:

| Field | Example value | Typical use |
| --- | --- | --- |
| first\_name | Priya | Greeting, sign-off |
| company | Northwind Studio | B2B subject lines, body copy |
| plan | Starter | Upgrade prompts only for Starter |
| city | Pune | Event invitations by location |
| last\_product | Ceramic pour-over | Accessory or refill suggestions |
| signup\_source | Workshop | Follow-ups tied to how they found you |

Anything sensitive, such as health details or financial information, deserves extra thought about whether you should be storing it at all, let alone quoting it back to someone in an inbox.

## Clean the spreadsheet first

Most contact lists start life as a CSV export. The format is simple but strict; [RFC 4180](https://www.rfc-editor.org/rfc/rfc4180) describes the common conventions, including that fields containing commas, quotes or line breaks should be wrapped in double quotes. A company name like `Smith, Jones & Co` without quotes will split into two columns and shift everything after it.

Before importing, work through this list:

1. **Fix capitalisation.** Convert ALL CAPS and all-lowercase names to normal case, but spot-check the result. Automated title-casing mangles names like "McAllister" or "de la Cruz."
2. **Remove placeholder values.** Search for "test", "asdf", "N/A", "-" and single letters in name columns. Blank is better than wrong.
3. **Split combined fields.** If you have a single "Name" column, decide whether splitting it is reliable. For many international names it is not, and using the full name or no name is safer.
4. **Standardise categories.** "Starter", "starter" and "Starter plan" should be one value, or your segments will miss people.
5. **Save as UTF-8.** Otherwise accented and non-Latin names can turn into garbled characters.

In Cresca, you [import contacts from a CSV](https://www.cresca.xyz/contact-management), map columns to standard or custom fields, and add tags as you go. A cleaned file means that mapping step takes minutes instead of an afternoon of fixes. For what to set up after the import, see [email marketing with Cresca](https://www.cresca.xyz/blog/email-marketing-with-cresca).

## How should you handle a merge field with a missing value?

Give every merge field a plan for the blank that suits the sentence. Use a natural fallback such as "Hi there", write around the value by opening with the point of the email, or send sentences that need the value only to contacts where the field is filled in. Then check the fallback in a test send.

Some contacts will be missing some values. Every merge field needs a plan for that case, and the right plan depends on the sentence.

- **Use a fallback word.** "Hi there" reads naturally when the name is missing. "Hi friend" can feel forced; test it on yourself.
- **Write around it.** Instead of opening with a name and a comma, start with the point of the email. Many good emails do not need a greeting at all.
- **Segment it out.** If a sentence only works with the value present, such as "Your Starter plan renews on…", send that email only to contacts where the field is filled in.

Whichever you choose, check the actual fallback behaviour in a test send rather than assuming it.

## How can you use personalization beyond the first name?

Use values that reflect something the reader actually did or chose. Reference how they joined, recommend a product based on what they last bought, swap whole paragraphs by segment, and use join or renewal dates to time messages as scheduled campaigns, or through an automation workflow once Cresca's workflows launch. These feel more personal than a first name, which no longer signals much.

Most readers have seen their own first name in subject lines many times over. It no longer signals much on its own. These approaches tend to feel more personal because they reflect something the reader actually did or chose.

### Reference the relationship

"Since you joined at the Bangalore workshop…" uses a signup source field to explain why this email exists. It also reminds people why they are on your list, which is good for complaint rates.

### Change the recommendation, not just the greeting

If you store the last product bought, a follow-up can suggest the matching refill instead of your full catalogue. That is one field, used once, doing far more work than a name.

### Swap whole sections by segment

Rather than one email with many merge fields, create two or three versions of a key paragraph and send each to a segment. Customers on a paid plan get a "what's new for you" paragraph; trial users get a "here's how to get started" one. Our walk-through on [building an email campaign](https://www.cresca.xyz/blog/how-to-create-an-email-marketing-campaign) covers setting up the audience step.

### Use dates to time, not to decorate

A join date or renewal date is most valuable when it times a message to the right moment, as a scheduled campaign today or an automation workflow once workflows launch, rather than being printed in the body.

## Examples: weak versus strong

| Weak | Stronger | Why |
| --- | --- | --- |
| "Priya, check out our new arrivals!" | "New filters for your ceramic pour-over" | Uses purchase history instead of a name |
| "Hi \[Company\] team" | "Three ways studios like yours are using the new export" | Uses the segment, avoids awkward phrasing if the value is odd |
| Same event email to everyone | Only contacts with city = Pune get the Pune invite | Removes irrelevant mail entirely |

## Pre-send checks for personalised campaigns

- Preview the email as at least three real contacts: one with every field filled in, one with blanks, and one with an unusually long value.
- Read the subject line with the longest likely value inserted. Does it still fit on a phone?
- Confirm segment counts look plausible. A segment of zero, or of your entire list, usually means a filter is wrong.
- Send a test to yourself and read it start to finish as if you were the recipient.

## A note on restraint

Personalization can tip into feeling watched. Mentioning someone's city to invite them to a local event is helpful. Mentioning which pages they browsed last night, when they never knowingly shared that, is not something most people welcome. A good test: would the reader remember giving you this information? If not, use it to choose what to send, not to quote it back at them.
