Emails
Workflows

Merge fields & personalisation

Personalise emails using merge fields and preview dynamic content with fallbacks.

July 22, 2026
ID:
76

Use merge fields to personalise subject lines and body content with each contact's own data.

Inserting fields

In a Rich Text block, insert a merge field via the Merge fields option in the block's ⋯ (more options) menu, or by typing @. The Subject line also supports merge fields.

Field categories

  • Basics — first name, last name, email.
  • Custom fields — e.g. member number, BPAY reference, or any custom field held on the contact.
  • Finance fields — membership fees, intervals and amounts.

Fallback values

Every merge field supports a default fallback for contacts who are missing that value. For example, "Hi {{First Name}}" can fall back to "valued customer" so the email never reads "Hi ,".

Check before sending

Use Preview in the builder and select a contact to confirm the fields resolve correctly, then send a test email (choosing a "person for merge") before the real send.

"Merge fields have changed" warning

In the Email Builder you may see the message: "Merge fields have changed. Please check/replace these before sending your email." This means one or more merge fields in the email (or the template it was built from) are no longer valid — usually because a custom field used as a merge field has since been changed or deleted. To resolve it, open the Email Builder and check each merge field, replacing any that are no longer valid. Once they're all valid the warning clears and the fields will merge correctly when you send.