Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.digifist.com/llms.txt

Use this file to discover all available pages before exploring further.

Campaign messages support dynamic content through template variable mapping. Variables defined in a template at creation time — such as {{1}} or {{2}} — are mapped to real customer or order data fields when a campaign is configured. At send time, Galantis populates each variable with the recipient’s actual data before dispatching the message to the WhatsApp API. Personalized messages perform better than generic broadcasts. Addressing a customer by name, referencing their last order, or surfacing a product they viewed increases relevance and reduces the likelihood of a block or report.

​
What this covers

  • How template variables are defined and mapped
  • Available data sources for variable values
  • How to configure variable mapping in a campaign
  • Fallback behavior when data is missing

​
How variable mapping works

Template variables are positional placeholders — {{1}}, {{2}}, {{3}} — defined in the template body and optionally in the header. When you select a template for a campaign, Galantis presents each variable placeholder and lets you assign it a dynamic value from your customer or order data. The mapping is stored as a template_variables_mapping configuration on the campaign: 
[
  { "initialValue": "{{1}}", "selectedValue": "customer.first_name" },
  { "initialValue": "{{2}}", "selectedValue": "order.total_price" }
]
At send time, each placeholder is replaced with the corresponding value from the recipient’s Shopify profile.

​
Available variable values

The following customer fields are available as variable values:
FieldValue
customer.first_nameCustomer’s first name
customer.last_nameCustomer’s last name
customer.emailCustomer’s email address
customer.phoneCustomer’s phone number
customer.first_name is the most commonly used variable — opening a message with the customer’s name meaningfully increases engagement compared to a generic greeting.

​
Configuring variable mapping in a campaign

1

Select your template

In the campaign builder, choose an approved template. Galantis detects the variable placeholders defined in that template.
2

Map each variable

For each placeholder ({{1}}, {{2}}, etc.), select a value from the available data fields or enter custom static text.
3

Preview the mapping

Review the mapping before proceeding. Confirm that each variable is assigned a value that makes sense in the context of the message body.

​
Best practices

  • Always map {{1}} to customer.first_name when the template opens with a greeting. This is the single highest-impact personalization variable and requires no extra configuration.
  • Use static text for offer codes. Discount codes are the same for all recipients — map them as static text rather than leaving the variable unmapped.
  • Avoid mapping email or phone to visible message body variables. Customers generally do not expect to see their own contact details reflected back to them in a promotional message.
  • Review mappings when reusing templates across campaigns. A variable mapping that worked for a post-purchase send (using order.total_price) will not make sense in a re-engagement campaign where many recipients have no recent order.