Personalization tokens and conditional content

Every campaign can be personalized per-recipient using tokens, and individual blocks can be shown or hidden based on contact tags.

Personalization tokens:
Type {{tokenName}} anywhere in subject, preheader, or text blocks. Tokens are expanded per recipient at send time.

Available tokens:
• {{firstName}}, {{lastName}}, {{email}} — contact fields
• {{firstName|fallback}} — show "fallback" if firstName is missing (e.g. {{firstName|there}} → "Hi there")
• {{accountName}} — primary account name on the contact
• {{org}}, {{orgWebsite}} — your sending org's name and website
• Custom contact fields — anything in the contact's customFields map

Conditional blocks (visibility rules):
Each block in the composer has a "Visibility rules" panel in the inspector:
• Show if tag — block only renders for contacts with this tag
• Hide if tag — block is hidden for contacts with this tag
• Both accept comma-separated lists (any-match)

Use cases:
• Discount block visible only to "VIP" contacts
• "Welcome back" hero only for tag "lapsed"
• Donor-tier-specific text blocks

If/else blocks (advanced):
For inline conditionals inside a text block, use:
{{#if hasTag "donor"}}Thank you for your donation!{{else}}Consider making your first gift today.{{/if}}

Conditions support: hasTag, equals, contains, exists.

Slash commands:
In subject, preheader, or text blocks, type "/" followed by a token name to insert with autocomplete:
• /firstName, /email, /accountName
• /article, /discount, /event, /deck — insert live content references
• /if, /ifelse — drop in {{#if}}…{{/if}} skeletons

The composer automatically renders a per-recipient preview in the test send and the recipient drill-down (analytics) so you can verify personalization looks right.