> ## Documentation Index
> Fetch the complete documentation index at: https://partner-help.letsdothis.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Email personalization

> Insert participant-specific data into your emails using dynamic content variables.

Email personalization lets you include data about each recipient directly in the email — for example, addressing every participant by first name, or referencing the event they registered for. Each recipient sees a version of the email tailored to them, even though you only compose it once.

Personalization is available in both marketing and transactional email campaigns:

* In **marketing emails**, you add fields with **Insert a field** in the email builder. See [Inserting a field in a marketing email](#inserting-a-field-in-a-marketing-email).
* In **transactional emails**, you add fields with the snippet builder. See [Using the snippet builder in a transactional email](#using-the-snippet-builder-in-a-transactional-email).

## Personalization variables

Variables use a double-curly-brace syntax: `{{ variable_name }}`. When the email is delivered, the platform replaces each variable with the actual value for that recipient. If no value is available for a recipient, the variable renders as blank — or as a fallback you specify.

A variable with a fallback looks like this:

```
{{ first_name | default: "there" }}
```

If a participant's first name is not recorded, the email renders "there" instead — so "Hi \{\{ first\_name | default: "there" }}" becomes "Hi Sarah" or "Hi there" depending on the data available.

## Inserting a field in a marketing email

In the email builder, a field shows on the canvas by its name, such as **First Name**, and is filled in for each participant when the email is sent.

**1. Open Insert a field**

Click where you want the field to go, then click **Merge tags** in the format bar above the text. You can also add fields to the subject line, and to an image's or button's link and image URL fields, using the merge tag button next to the field.

**2. Choose the field**

Browse the field groups, or search for a field by name.

**3. Insert it**

Click **Insert field**. The field is added at your cursor, or into the field you opened it from.

The fields are grouped by where the data comes from:

| Group | What it contains |
| - | - |
| **About this person** | First name, last name, full name, email address, city, and gender. These work for any audience. |
| **Event and registration** and the registration field groups | Details from a participant's registration, such as add-ons and answers to your custom questions |
| **From this audience** | The extra columns in an imported audience's file. Shown only when the email's audience is an imported audience. |
| **Links** | The unsubscribe link and a link to Let's Do This. Shown in link fields only. |

### Registration fields

Registration fields are only available in an email about a registration, such as a triggered email that sends when someone **registers** or **checks in**. When they aren't available, for example in an email scheduled for a set date, registration fields show a padlock and can't be inserted.

### Fallbacks in marketing emails

**Insert a field** doesn't add a fallback. If a participant has no value for a field, that part of the email is blank. Before using a field such as first name, check that most of your audience has it, or write the text so it still reads well without it.

## Using the snippet builder in a transactional email

The snippet builder is the easiest way to insert a variable in a transactional email without typing it by hand. It is available on the Builder step of the campaign wizard, in both the Basic Builder and the Advanced Builder.

**1. Open the personalization panel**

In the Builder step, look for the **Personalization** or **Dynamic variables** panel. In the Basic Builder this appears in a sidebar or below the section controls. In the Advanced Builder, open it from within a text block.

**2. Select an attribute**

Choose the piece of data you want to insert from the attribute list. Available options include things like participant name, email address, event name, and registration-specific fields.

**3. Set a fallback (optional)**

In the **Fallback** field, enter the text that should appear when the attribute has no value for a particular recipient. Providing a fallback is recommended — it prevents blank spots in your email.

**4. Copy and paste the snippet**

The generated snippet appears in the output box. Click **Copy** to copy it to your clipboard, then paste it into the text or HTML section of your email where you want it to appear.

For conditional logic — showing or hiding content based on whether a value exists — click **Copy for logic** to get the variable identifier without the full snippet wrapper. You can then build `{% if %}` conditions around it in an HTML section.

## Validation

The platform checks your personalization syntax before an email is sent. If a variable name is not recognized, or the syntax is malformed, you'll see a validation warning highlighting the problem. Fix the variable before continuing to avoid delivery errors.

In a marketing email, an invalid field stops the email sending, and the problem is listed under **This email can't be sent yet**. See [Emails that can't be sent](https://partner-help.letsdothis.com/docs/email-communications/marketing-emails.md#emails-that-cant-be-sent).

## Tips for reliable personalization

**Plan for missing values.** Not every participant's profile includes a first name. In a transactional email, set a fallback like "there". In a marketing email, write the text so it reads well if the name is missing.

**Preview with real data.** In a marketing email, use **See what email looks like for** in the **Audience** tab to see the email as a participant in your audience, with their details filled in. In a transactional email, use **Send Test** on the Launch step.

**Check your data source.** Variables only contain values that exist in your participant records. If a field such as bib number is not filled in yet, wait until data is available before sending an email that references it.

**Keep conditions simple.** Conditional blocks (`{% if %}`) are powerful but harder to debug. If you need conditional content, test it thoroughly before sending to your full audience.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.