Merge tags reference
Every merge tag available in notification emails and confirmations.
Merge tags are placeholders replaced with real values when an email is sent. They work in both the subject and the body.
Submission tags
| Tag | Inserts |
|---|---|
{all_fields} |
The whole submission as a formatted list |
{form_title} |
The form’s name |
{entry_id} |
The entry’s numeric ID |
Attribution tags
| Tag | Inserts | Example |
|---|---|---|
{traffic_source} |
How the visitor arrived | organic |
{utm_source} |
UTM source parameter | google |
{utm_medium} |
UTM medium parameter | cpc |
{utm_campaign} |
UTM campaign parameter | spring-sale |
{source_url} |
The page the form was submitted from | /contact/ |
{device_type} |
Device category | Mobile |
{browser} |
Browser name and version | Safari 17 |
{ip_address} |
Visitor IP, anonymised if that setting is on | 203.0.113.0 |
Individual field tags
Each field produces two tags.
By label — take the field’s label, lowercase it and replace spaces with hyphens, then prefix with field_:
| Field label | Tag |
|---|---|
{field_email} |
|
| Phone Number | {field_phone-number} |
| Company Name | {field_company-name} |
By ID — every field also has an internal ID usable directly as {field_id}. Label-based tags are easier to read, but they change if you rename the label. If you rename a field, update any tags referring to it.
The email shortcut
Whatever its label, the first Email field on a form is always available as {field_email}. This is the tag to use for Reply-To and for confirmation emails to the submitter.
Checkbox values
A Checkboxes field with several selections is inserted as a comma-separated list, for example Newsletter, Product updates.
Unrecognised tags
A tag that does not match anything is left in the message exactly as written. If an email arrives containing a literal {field_nmae}, that is a typo in the template rather than a bug.