Learn

Merge tags (personalization tokens)

Merge tags, also called personalization tokens or merge fields, are placeholders in a message template — like {{first_name}} or {{company}} — that are automatically replaced with each recipient's data at send time. They let one template produce individually personalized messages at scale without manual editing.

How it works

The template references fields from your CRM or list (first name, company, title, a custom snippet). At send, each tag is swapped for the recipient's value, ideally with a fallback default so a missing field doesn't leave a blank or a raw {{tag}} in the message.

Why it matters

Personalization lifts reply rates, but broken merge tags — an empty value or a visible {{first_name}} — instantly signal automation and damage credibility. Reliable merge requires clean, verified data and sensible fallbacks, which is why enrichment and personalization go together.

How Autocloz handles it

Autocloz feeds verified, enriched contact fields into personalization tokens across every channel's templates, with fallbacks, so merged messages stay accurate and never expose a blank or raw tag to the recipient.

FAQ

What happens if a merge tag has no value?

Without a fallback, you risk sending a blank or a visible raw tag like {{first_name}}, which looks broken and automated. Always set default fallback text (for example, 'there') and verify data quality before sending to avoid embarrassing merges.

Are merge tags the same across channels?

The concept is identical, but the syntax and available fields vary by tool and channel. The key requirement everywhere is clean, populated source data plus fallbacks, so the personalization renders correctly in email, SMS, LinkedIn or WhatsApp.

Related terms