FIELD FEATURES

Use merge tags in messages and redirects

Insert form, entry, site and field values into Logical Forms notifications and confirmations, with compound parts and audience-aware answer summaries.

3 min read · Updated November 19, 2026

Merge tags insert values into settings that support them, including notification recipients, sender, subject and body, confirmation messages, and redirect query-parameter values. Use the picker beside the relevant control to choose tags available for that destination.

Form, entry and site tags

Tag Meaning
{form_title} / {form_id} The form's title and numeric identity.
{entry_id} The saved entry identity.
{entry_date} The saved submission time in the site's date/time format.
{entry_admin_url} A link to the protected administration entry screen; offered in notification subject/body. It still requires entry-management access.
{site_name} / {site_url} The current site's name and home URL.
{admin_email} The site's configured WordPress administrator email address.

Insert a field or compound part

{field:5} inserts the formatted answer for field 5. A declared compound part uses syntax such as {field:5.first}. Pick your actual field and part instead of assuming the example IDs match your form.

Field IDs remain stable when labels change. Whole Name values and choices use their providers' readable formatting; a choice normally displays its label rather than a raw saved identity. A missing field answer can resolve empty. Unknown or unsupported tag names remain literal, so check the result after changing extensions or templates.

Use the automatic answer summary

{all_fields} is supported in notification bodies and confirmation messages. In HTML it produces a label/value table; a plain-text confirmation uses readable lines. Zero answers are included, while unanswered and display-only fields are omitted.

Notification summaries omit Internal fields but can include Hidden answers. Visitor confirmation summaries additionally omit dedicated Hidden fields, fields set to Hidden and uploaded files. Repeater children are grouped under their parent, with the same audience exclusions inside rows.

An explicit field tag can deliberately include a value that the automatic summary excludes. Review the intended audience rather than treating the summary policy as a general access rule for every template.

Formatting and redirects

Ordinary values are escaped appropriately for the destination. In HTML messages, blank lines make paragraphs and single line breaks remain visible. Put an all-fields summary on its own line when you want a clear separation from surrounding text.

Redirect query parameters can use tags in values, for example reference={entry_id}. The value is URL-encoded. The destination URL remains static; see confirmations and redirects for replacement behavior and examples.

Defaults and testing

Field default values use Dynamic population for dynamic initial sources. Typing a message tag into an arbitrary field setting does not make that setting a supported merge surface.

Test with both completed and optional blank answers. Send deliberate receipt tests only to an address you control, and inspect both the rendered message and the saved entry. Queued notifications retain the prepared output from their original planning; editing a template later does not rewrite that queued message.