Map Variables & Personalize Messages
Map WhatsApp or email placeholders to Wemblo contact fields and use safe fallback values.
Step-by-step instructions
- Open campaign personalization.
- Select a fictional preview contact.
- Map every variable to the correct contact or custom field.
- Add fallback values where supported.
- Preview the complete message.
- Test empty and malformed fields.
- Save only after the preview is correct.
Who should use it
Marketing users, sales teams, workspace managers and authorized campaign operators.
Where to find it in Wemblo
Wemblo -> Marketing -> Campaigns
Before you begin
- Use the correct workspace and connected channel.
- Confirm audience consent and provider eligibility.
- Prepare fictional test contacts and approved content.
- Assign a person or team to handle replies.
Main concepts and fields
| Concept / Field | Meaning or Use |
|---|---|
| Variable | Placeholder replaced at send time. |
| Field Mapping | Connects a variable to Wemblo contact data. |
| Fallback Value | Used when a field is empty. |
| Preview Contact | Fictional record used for testing. |
| Personalization | Approved contact-specific content. |
Test and verification
- Complete one successful path with fictional data.
- Complete one invalid, failure or permission path.
- Confirm the result appears in the correct workspace and module.
- Confirm the correct person or team can review and continue the work.
Common issues and solutions
| Issue | What to Check |
|---|---|
| Campaign or post cannot start | Sender, destination, audience, consent, schedule and plan limit. |
| Content or variable fails | Template/content status, field mapping and fallback value. |
| Provider reports failure | Authorization, media/content rules and provider response. |
| Replies are missed | Smart Inbox routing, assignment and staffing. |
Security, privacy, consent, cost and provider notes
- Use only data the business is authorized to process.
- External provider charges, policies, approvals, limits and availability remain separate.
- Do not expose passwords, API keys, tokens, webhook secrets, payment credentials or private customer data.
- Use human review for sensitive, regulated, urgent, financial or final decisions.
Last reviewed: