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

# Personalization & Merge Tags

> Use Jinja merge tags to personalize email templates and survey invitations for every recipient.

Statisfy personalizes email with **merge tags** — placeholders that are replaced with each recipient's real data when an email is sent. Under the hood Statisfy uses the [Jinja](https://jinja.palletsprojects.com/) templating syntax, so a tag looks like this:

```text theme={null}
Hi {{ contact.name }}, thanks for being a customer of {{ account.name }}.
```

When the email goes out, `{{ contact.name }}` becomes *"Jane Smith"*, `{{ account.name }}` becomes the recipient's account, and so on — one personalized copy per recipient.

Merge tags work anywhere personalization is supported: [email template](/campaigns/email_templates) subject lines and bodies, [survey](/campaigns/surveys) invitations, and [Agent Studio email actions](/agent-studio/automations/actions).

### Syntax

| Syntax                         | Meaning                      | Example                                 |
| ------------------------------ | ---------------------------- | --------------------------------------- |
| `{{ group.field }}`            | Insert a field's value       | `{{ account.name }}`                    |
| `{{ group.field }}` in subject | Personalize the subject line | `A quick update for {{ account.name }}` |

<Note>
  Use double curly braces: `{{ ... }}`. Spaces inside the braces are optional — `{{contact.name}}` and `{{ contact.name }}` behave the same. Statisfy validates merge-tag syntax before a template can be published, so a malformed tag is caught early.
</Note>

### Inserting tags with the picker

You don't need to memorize tag names. In the email editor, open the **Insert Merge Tag** picker to browse every tag available in your workspace, grouped by entity. Search by name, expand a group, and click a tag to insert it. Each entry shows the tag's name, its `{{ ... }}` value, and a sample value so you know what it will resolve to.

### Merge tag groups

The tags available to you depend on your workspace's data model. They are organized into the following groups:

| Group       | Prefix     | What it contains                                               |
| ----------- | ---------- | -------------------------------------------------------------- |
| **Special** | —          | Built-in links (see below)                                     |
| **Account** | `account.` | Fields from the recipient's account                            |
| **Contact** | `contact.` | Fields about the individual recipient                          |
| **User**    | `user.`    | Fields about the Statisfy user (e.g. the assigned CSM / owner) |

Each of the Account, Contact, and User groups exposes both the **standard fields** Statisfy ships with **and** any **custom fields** your team has defined for that entity. Because custom fields differ per workspace, the picker is always the source of truth for exactly which tags you can use — for example `{{ account.name }}`, `{{ contact.name }}`, or a custom field like `{{ account.your_custom_field }}`.

### Special tags

Two built-in tags handle links that Statisfy generates per recipient:

| Tag                      | What it does                                                                                                                                                                                     |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `{{ unsubscribe_this }}` | Inserts the recipient's [unsubscribe link](/campaigns/campaign_unsubscribe). Required in Promotion, Newsletter, and Custom email templates. The **Unsubscribe** editor block inserts it for you. |
| `{{ survey_url }}`       | Inserts the link to the recipient's [survey](/campaigns/surveys). Used in survey invitations. The **Begin Survey** editor block inserts it for you.                                              |

<Tip>
  You rarely need to type `{{ unsubscribe_this }}` or `{{ survey_url }}` by hand — drag in the **Unsubscribe** or **Begin Survey** block in the visual editor and Statisfy wires up the correct link.
</Tip>

### Tips for reliable personalization

* **Send a test first.** Use a campaign test send to confirm every tag resolves to a real value before a large send. See [Creating Campaigns](/campaigns/creating_campaigns#test-before-publishing).
* **Watch for empty values.** If a recipient is missing data for a field, that tag may render blank. Keep critical sentences readable even if a value is missing.
* **Use the picker, not guesswork.** Custom fields are workspace-specific — insert from the picker so the tag name matches your data exactly.
* **Personalize the subject too.** Subject-line tags (e.g. `{{ account.name }}`) can lift open rates.

### Related

<CardGroup cols={2}>
  <Card title="Email Templates" icon="envelope" href="/campaigns/email_templates">
    Build the templates where merge tags live.
  </Card>

  <Card title="Surveys" icon="clipboard-list" href="/campaigns/surveys">
    Personalize survey invitations.
  </Card>

  <Card title="Agent Studio Actions" icon="diagram-project" href="/agent-studio/automations/actions">
    Send personalized email from automations.
  </Card>

  <Card title="Unsubscribe" icon="ban" href="/campaigns/campaign_unsubscribe">
    How the unsubscribe link works.
  </Card>
</CardGroup>