DOCUMENTATION

Personalization variables

Last updated Aug 2026
Email
All plans

Anywhere you write email copy — templates, campaigns, welcome emails, automations — you can drop in a variable like {{firstName}} and each recipient sees their own name instead of the literal text. This page covers which variables exist, where you can use them, and what happens when a contact is missing the data a variable needs.

Available variables

VariableResolves to
{{firstName}}The first word of the contact’s saved name. Blank if they never gave a name (e.g. an email-only signup).
{{name}}Their full saved name. Blank under the same conditions as above.
{{email}}The address you’re sending to. Always present — this is how the contact ended up in your list.
{{unsubscribeUrl}}A real, working unsubscribe link unique to that contact. See below — this one behaves differently from the others.
{{company}}The contact’s saved company/organization. Blank unless you’ve set one — see the callout below.
Unlike name/email, {{company}} is never filled in automatically — nothing in BlnkSpace collects a company name on its own (not the signup form, not order checkout). Set it yourself: open a contact in the Contacts tab and fill in the Company field when adding one manually, or include a company (or organization) column when importing a CSV — it’s auto-detected the same way the name/email columns are.

Where you can use them

Variables work the same way — literal {{...}} text you either type or insert from a picker — in every email surface:

SurfaceHow to insert
Template editor (classic)Click a block, open the variable picker in the settings panel, click a token to insert it at your cursor.
Template editor (new, beta)A row of clickable variable chips sits above the canvas — click one to insert it wherever your cursor is.
AI panel (new editor only)Just ask naturally — e.g. “personalize the greeting” — the AI knows about all the working variables and uses them appropriately instead of inventing its own placeholder text.
Campaigns composerPick a saved template that already has variables in it, or type {{firstName}} etc. directly — both editors are available here too.
Before / after — a welcome email
What you write
Hey {{firstName}}, welcome aboard!
What a recipient named Alex sees
Hey Alex, welcome aboard!

When a contact is missing the data

If a contact has no saved name, {{firstName}} and {{name}} both resolve to an empty string — not the literal {{firstName}}text, and not an error. “Hey {{firstName}},” becomes “Hey ,” with a trailing space where the name would have been. Write copy that still reads acceptably without a name if you expect a meaningful share of email-only signups, or avoid opening directly with the variable.

Any variable-looking text that isn’t one of the real ones above (a typo, or something you made up) gets silently stripped from the final email rather than sent literally — so a typo like {{fristName}}won’t show up as broken-looking text to recipients, it’ll just vanish. That’s convenient for not leaking broken placeholders, but it also means a typo’d variable fails silently — double-check the spelling against the table above if personalization isn’t showing up as expected.

{{unsubscribeUrl}} is different

Every other variable is optional flavor text. {{unsubscribeUrl}}is the one that matters for deliverability and compliance — it’s a real, per-contact link that actually unsubscribes them when clicked. Campaign sends already include a working unsubscribe link in the email headers regardless of whether you use this variable in the body, but including it visibly in your footer text (e.g. “{{unsubscribeUrl}}to stop receiving these emails”) is good practice and is required by some regions’ email regulations.

Campaigns
Fully supported — this is the original, most-tested path.
Welcome emails & automations
Also supported — each one looks up (or generates on the spot, if the contact somehow doesn’t have one yet) that contact’s real unsubscribe token before sending, same as campaigns.