Add Personalization into your Email - Legacy Composer

  • Updated

This article walks through how to add personalization fields in the Legacy Email Composer. Use this version if you're working in an older message editor or legacy template.

Quick Reference (Advanced Users) - Click to Expand
  • Insert personalization: Click into Rich Text Block → click Personalization in toolbar
  • Field types supported: Standard Fields, List Fields, CRM Fields*, Sender Fields*
  • Fallback syntax: {{={{First Name}}|Friend}}
  • Manual entry: {{Field Name}} (must match list)
  • *CRM and Sender fields require setup
Try it like this: Insert Hi {{={{First Name}}|there}} in your message body to personalize the greeting, even when names are missing.

How to Add Personalization (Legacy Composer)

  1. Open the legacy email you want to edit.
  2. Go to the Design tab and either create or edit a Rich Text Block.
  3. Click the pencil icon to edit the content block.
  4. From the formatting toolbar, click Personalization.

Legacy Composer Personalization Button

  1. Select a Personalization Field Type (e.g. Standard, List, CRM).
  2. Choose the field you wish to insert.
  3. Optional but recommended: Enter fallback text for contacts who don’t have a value in that field.
  4. Click Insert. The personalization variable will appear in your message.

Fallback field example

Manual Syntax (Advanced)

  • {{First Name}} – Basic syntax
  • {{={{First Name}}|Friend}} – Adds fallback text "Friend" if the field is blank
Important: The field name must exactly match what appears in your list or CRM. If it doesn't match, the message will fail to send.

Preview Personalizations

  1. Go to the Address tab and add your recipient list(s).

Add list to legacy message

  1. Click the Review tab to view your message.
  2. Under Sample Preview, use the dropdown to select a contact from your list.

Legacy sample preview dropdown

  1. Check that each field displays properly for your chosen sample contact.

Using the new Email Composer? Follow this guide instead.

Was this article helpful?

Have more questions? Submit a request