Variables allow you to personalize your email content and subject lines for each subscriber.

## Syntax

Use double curly braces to insert variables:

```
{{variableName}}
```

### With Default Value

Add a fallback value when the variable is empty:

```
{{variableName | 'Default Value'}}
```

Or with double pipe:

```
{{variableName || 'Default Value'}}
```

## Examples

### Subject Line

```
{{name | 'Hey'}}, voici ton guide LinkedIn
```

**Result:**

- If subscriber has name "Marie" → `Marie, voici ton guide LinkedIn`
- If subscriber has no name → `Hey, voici ton guide LinkedIn`

### Email Content

```
Hello {{name | 'there'}},

Your email is {{email}}.
```

## Available Variables

### Built-in Variables

| Variable             | Description                                        |
| -------------------- | -------------------------------------------------- |
| `{{name}}`           | Subscriber's name                                  |
| `{{email}}`          | Subscriber's email address                         |
| `{{phone}}`          | Subscriber's phone number                          |
| `{{ipAddress}}`      | Subscriber's IP address (captured at signup)       |
| `{{country}}`        | Subscriber's country code (e.g., "US", "FR", "CH") |
| `{{unsubscribeUrl}}` | Unsubscribe link                                   |
| `{{onlineUrl}}`      | View in browser link                               |

### Organization Variables

| Variable          | Description           |
| ----------------- | --------------------- |
| `{{org-name}}`    | Organization name     |
| `{{org-adresse}}` | Organization address  |
| `{{org-logo}}`    | Organization logo URL |

### Global Organization Variables

In **Settings → Configuration → Variables**, add a shared value such as
`number_member_editing_ai` = `1250`. Insert it with `@` in the editor (the globe
icon identifies global variables), or use `{{global-number_member_editing_ai}}`
in subjects, previews, HTML and links. Rich email content uses a variable node
with `attrs.id: "global-number_member_editing_ai"`.

Global variables belong to the organization, so every recipient sees the same
value. Subscriber fields and per-email payloads cannot override them. An inline
fallback is used only if the global variable has been deleted or is missing.
The `global-` prefix is reserved: subscriber fields cannot be created or renamed
with it, including through the API or imports. If an older subscriber field
already uses a global key, rename that field before creating the global variable.
Values are read when an email is prepared: previously prepared or sent emails
keep their values. These are stored values, not automatically calculated counts.

Names start with a lowercase letter and contain up to 64 lowercase letters,
digits, underscores or hyphens. An organization can store up to 100 variables,
with at most 2,000 characters per value. Use `"0"` for zero; blank values delete
the variable.

API and AI agents use the same organization-scoped tools (API token permission:
`settings`):

```http
POST /api/v2/tools/get_organization_variables
Content-Type: application/json
Authorization: Bearer YOUR_API_TOKEN

{}
```

```http
POST /api/v2/tools/update_organization_variables
Content-Type: application/json
Authorization: Bearer YOUR_API_TOKEN

{"changes":{"global-number_member_editing_ai":"1250"}}
```

Only supplied keys change. Send `null` to delete a key. The `name` key is reserved
for the existing subscriber-name fallback. Use `get_available_variables` to
discover global variables alongside built-ins and subscriber fields.

### Subscriber Custom Fields

Any custom field you create for subscribers can be used as a variable:

```
{{customFieldName | 'default'}}
```

## Using Variables in Editor

1. Type `@` in the editor to open the variable menu
2. Select or type your variable name
3. Click on the variable to edit the default value

## Tag Action Links

Tag action links use variable-like syntax only in a link's URL; they are not content or subject-line variables.

```
{{addTag:interested}}
{{removeTag:promo}}
```

For the editor flow, delivery restrictions, success page, and workflow use cases, see [Tag Action Links](/docs/features/tag-action-links).

## Best Practices

- Always provide default values for optional fields like `name`
- Use descriptive default values that make sense in context
- Test your emails with subscribers who have missing data

## Related Documentation

- [Tag Action Links](/docs/features/tag-action-links) - Let subscribers add or remove tags by clicking a link
- [Send Email API](/docs/api-reference/api-emails-send) - Use variables in transactional emails
- [Workflows](/docs/workflows) - Use variables in workflow email steps
- [Language](/docs/features/language) - Recipient-page language vs email footer copy
- [Content Deliverability](/docs/features/content-deliverability) - Required variables like `{{unsubscribeUrl}}`
- [Create Subscriber](/docs/api-reference/api-subscribers-post) - Add custom fields for personalization