Overview

Recipient fields let you automatically insert personalised information, such as a recipient's name, organisation name, or the send date, directly into your newsletter content. Instead of sending a generic message to everyone, you can make each recipient feel like the newsletter was written just for them, without any extra effort.

1. Where recipient fields can be used

Recipient fields are supported in two primary locations within the newsletter editor interface:

• Text blocks: insert dynamic fields anywhere within the body copy of your newsletter layout.

• Subject line: personalise the email subject line that recipients see first in their inbox.

2. Available recipient fields

The following system fields can be dynamically inserted into your campaign:

3. Step-by-step implementation workflows

How to use recipient fields in the newsletter body

1. Select a text block: block canvas placement. In the newsletter editor workspace, add a new Text block or click inside an existing one to activate the cursor.

2. Access recipient fields menu: toolbar interaction. Look at the rich text editor toolbar menu overlay and locate the Recipient fields dropdown option.

1. Select your field tag: placeholder injection. Select the specific field you would like to insert (e.g. first name, app name, or send date). The field will immediately appear as a raw template placeholder tag in the editor, for example, {{first_name}}.

Example application: if you compose the string: "Hi {{first_name}}, check out the latest from {{app_name}}!", a recipient named John Smith will see: "Hi John, check out the latest from GoodCo!"

How to use recipient fields in the subject line

1. Navigate to Details step: campaign progress. When sending or scheduling your newsletter campaign, proceed forward to the Details step configuration panel.

2. Insert subject fields: subject mapping. Locate the Subject line field and click the recipient fields selector option to insert a dynamic placeholder tag such as first name or full name.

3. Define fallback strings: fail-safe configuration. Add a dedicated fallback text value inside the field properties prompt. This value acts as the backup string if a specific recipient profile field happens to be empty or missing.

Technical logic for fallback text

Always set a fallback value when using recipient fields in the subject line. This ensures a seamless, professional experience for recipients whose profile data may be incomplete or missing.

• Field mapping: {{first_name}}

• Fallback entry: there

• System result for incomplete profiles: "Hi there, here's your weekly update!" (instead of leaving a broken, empty space like "Hi , here's your weekly update!").

Compatibility with AI features & limitations

• AI subject line integration: when utilising the built-in AI subject line generator, personalisation fields such as first name and full name are fully supported within the AI suggestions. The system-mandated 140-character limit applies strictly to the generated text copy itself; the system-parsed personalisation tags are entirely excluded from this character count.

• Send-time resolution: recipient fields are resolved exclusively during the live high-speed send pipeline, each recipient sees their own personal data, not a shared value.

• Testing limitations: recipient fields do not render as live user data inside the editor preview canvas or via the "Send Test Email" utility. They will intentionally appear as structural placeholder tags (e.g. {{first_name}}) until the newsletter is officially dispatched to the live distribution list.

Strategic best practices

• Boost open rates: use the first name field in the subject line to increase open rates — personalised subject lines feel more direct, human, and relevant to the recipient.

• Always set backups: ensure a fallback value is defined for every recipient field you implement, especially when designing critical subject lines.

• Contextual timing: use the send date field for newsletters that are time-sensitive or recurring, so readers instantly recognise the chronological recency of the edition.

• Maintain subtlety: keep personalisation subtle. Incorporating one or two dynamic fields per newsletter layout is usually enough to feel personal without feeling intrusive.

Frequently asked questions

Q: Where can I insert recipient fields in my newsletter?

Ans: Recipient fields can be inserted in two places: within text blocks in the body of your newsletter, and in the subject line.

Q: What happens if a recipient's profile is missing the data for a field I've used?

Ans: If you've set a fallback value, the system will display that instead. For example, if {{first_name}} has a fallback of "there," a recipient with no first name on file will see "Hi there" rather than a blank space.

Q: Will recipient fields show real names when I preview my newsletter or send a test email?

Ans: No. Recipient fields only resolve to real data during the actual send. In previews and test emails, they'll appear as placeholder tags, such as {{first_name}}, rather than live recipient data.

Q: Can I use recipient fields together with the AI subject line generator?

Ans: Yes. Personalisation fields like first name and full name are fully supported in AI-generated suggestions, and they don't count towards the 140-character limit applied to the generated text.

Q: How many recipient fields should I use in one newsletter?

Ans: It's best to keep it subtle, one or two dynamic fields per newsletter is usually enough to feel personal without feeling intrusive.

Q: Does every recipient see the same send date, or is it personalised too?

Ans: The send date field reflects the exact date the newsletter is dispatched, and like all recipient fields, it's resolved individually for each recipient during the send.

Q: Is it mandatory to set a fallback value for recipient fields?

Ans: It isn't strictly mandatory, but it's strongly recommended, especially for subject lines, so recipients with incomplete profile data still see a polished message instead of a broken or empty space.