Mastering Dynamic Template Variables: How to Personalize Mass Broadcasts in Patify

The Power of Dynamic Personalization

Generic mass messages get ignored. Messages personalized with the customer's name, order ID, or account status command immediate attention. In Meta WhatsApp Business API, placeholders like {{1}}, {{2}}, and {{3}} are used to inject dynamic variables into pre-approved message templates.

For a detailed walkthrough on setting up compliant templates without rejections, check our step-by-step guide on Submitting WhatsApp Templates to Meta.

How TemplateVariableSource Works in Patify

Patify simplifies template parameter mapping through the TemplateVariableSource Backed Enum inside the Campaign Builder:

• CONTACT_NAME: Hydrates {{1}} with the recipient's full name (e.g., "Hi Rahul Kumar").
• CONTACT_PHONE: Hydrates {{2}} with the recipient's E.164 phone number.
• TENANT_NAME: Hydrates {{3}} with your brand's official organization name.

This dynamic hydration also integrates natively into multi-day campaigns. See our guide on Automated WhatsApp Drip Sequences to learn how personalized variables persist across message steps.

Dynamic Variable Hydration Matrix

The table below shows how raw template code is dynamically converted at dispatch runtime:

Meta Sample Value Rules

When submitting a new template to Meta for approval, you must provide realistic sample values for every variable placeholder. For example, if your template reads "Hi {{1}}, your booking {{2}} is confirmed", you must submit sample values like {{1}} = "Amit Sharma" and {{2}} = "BK-9082". Templates submitted without valid sample values are automatically rejected by Meta AI filters.