Skip to main content
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 templating syntax, so a tag looks like this:
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 subject lines and bodies, survey invitations, and Agent Studio email actions.

​
Syntax

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.

​
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: 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:
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.

​
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.
  • 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.

Email Templates

Build the templates where merge tags live.

Surveys

Personalize survey invitations.

Agent Studio Actions

Send personalized email from automations.

Unsubscribe

How the unsubscribe link works.