Email personalization adapts email content for its recipient using relevant information. A rendered greeting is one concrete place to check what that information produces.
Inspect field values
Mailchimp replaces an audience-field merge tag with its stored value. Read the field beside the intended words.
Choose a fallback for missing data
Mailchimp’s defaults can replace a missing first name in a sent email. The default does not populate the audience field.
Fictional greeting
Fictional ceramics-shop greeting: this chosen rule uses the recorded name, or “there” for a blank field.
| Invented name field | Expected greeting | Check |
|---|---|---|
| Asha | Hello Asha, | Confirm the name. |
| Blank | Hello there, | Inspect the fallback. |
| CUSTOMER | Hello CUSTOMER, | Review the placeholder. |
The placeholder is present, so this illustrative rule keeps it. Check the record rather than expecting the fallback to correct it.
Preview checks
Mailchimp’s contact-specific audience-field tags do not populate ordinary test sends. Its live merge-tag preview is a separate check.
Klaviyo’s guide uses a profile to preview template or campaign personalization, and a relevant event for flow emails that support event data. Check that the selected data contains the field your message uses.
Klaviyo warns that some dynamic and send-time behavior differs in preview. A successful sample does not settle how every message will render.
Keep the expected words with the review
Keep the draft version, selected record or event, expected wording and unresolved issue together. If the wrong greeting appears, inspect the selected data and the field reference before changing the template. Name the next output to check.
Related terms
Customer Segmentation explains group rules. Choosing recipients and checking their message remain separate tasks.