Personalization & Variables

Templates use numbered placeholders like {{1}}, {{2}}to personalize messages. In Socialone, you map each variable to a contact field, a custom field, or a static value before sending a broadcast.

Overview links: Documentation Home · Settings Overview

Where to Find This

• This step appears during Broadcast setup when a template has variables. Templates without variables skip the mapping step automatically.

Settings Quick Map

• Settings → Contact Custom Fields: define extra contact fields available for variable mapping.
• Settings Overview

Variable Basics

• Variables appear in the template body and optionally in the header.
• Numbering is positional: {{1}} maps to variable 1, {{2}} to variable 2, and so on.
• Every variable must be mapped before sending. The send button stays disabled until all are resolved.

Mapping Options

Contact Field Reference

Standard contact fields use dot notation. Custom fields extend the path with custom_field:

• Standard fields: contact.first_name, contact.last_name, contact.phone, contact.email, contact.city, contact.state, contact.country, contact.company.
• Custom fields: contact.custom_field.field_name — replace field_name with the exact slug of your custom field (e.g., contact.custom_field.order_id, contact.custom_field.loyalty_points). Custom fields are defined in Settings → Custom Fields.
• Static inline prefix: prefix a value with static: to use it directly without contact lookup (e.g., static:Hello). Useful in API or workflow integrations.

Contacts Mapping (Filter Contacts)

1. Choose recipients using Filter Contacts.
2. Click Check Selection to preview the matched recipients.
3. Map each variable to a Contact Field, Custom Field, or Static Value.
4. Proceed to send or schedule.

CSV Mapping

• CSV requires columns: name, country_code, phone_number.
• Add numbered columns 1, 2, 3 to match template variable positions.

Variables in Downstream Templates (Flow Builder)

When a contact taps a button and a downstream template is sent automatically, variables in that template are resolved from the same contact record — no extra mapping is required. The same dot-notation paths apply.

Tips

• Double‑check variable order before sending. {{1}} maps to position 1, not by name.
• Use static values for shared info like campaign names, offer codes, or dates.
• For order-specific data, store it as a custom field (e.g., contact.custom_field.last_order_id) so broadcasts can reference it per contact.
• Templates without variables skip the mapping step entirely.

Next Steps

• Contacts
• Broadcasts Overview
• Template Setup

Common Blockers & Fixes

• Next button disabled: map every variable or remove unused variables from the template before sending.
• Contact field missing: update the contact schema in Settings → Custom Fields, or choose a static value as fallback.
• CSV variables not filling: add numbered columns 1, 2, 3 to the CSV, matching the variable positions in the template.
• Custom field not resolving: check the field slug exactly matches the path used (e.g., contact.custom_field.order_id vs contact.custom_field.orderid).