Personalised campaigns are always very effective in creating an impact on the subscribers and improving the conversions. In this section, you will understand what kind of personalisation WhatsApp campaigns can offer.
ZEPIC provides two different ways to personalise the campaigns:
- Personalise based on the property of the object. For example, in the Contact object, you can personalise the campaigns based on their name, country, language or any property stored in the Contact object's record.
- Personalise based on the events and their properties. For example, if an Order_Placed event happens, you can personalise the campaign with the order value or products in the order.
Personalisation Placeholders:
In one-off campaigns & triggered campaigns, you can personalize messages using the properties in the campaign's base object.
A step-by-step guide to using personalisation placeholders in WhatsApp campaigns
- Create a new WhatsApp campaign, give it a name, and choose a template for the campaign.
- Click on the "Insert Attribute" button, and you will see a menu with two options - "Base Object name" and "Events".
- In the menu, click on the base object option (in this screenshot below, Contact is the base object). You will see all its properties.
- Click on the placeholder and use it in the campaign. You also need to specify the fallback value, which is mandated by WhatsApp/Meta, for the placeholder.
Event Placeholders:
Only in triggered campaigns, you can personalize using event variables/placeholders to create a more tailored and engaging customer experience.
When an event occurs, such as an order confirmed or checkout started, the campaign can automatically include specific event attributes in the message to make it more relevant and meaningful for the recipient, the campaign can automatically include specific event attributes in the message, to make more relevant and meaningful for the recipient.
For example, if a customer completes a purchase, the confirmation message can include details like the order number, items purchased, and estimated delivery date. This personalization makes the communication more relevant and informative, helping customers feel valued and improving overall satisfaction. By leveraging event attributes, you can deliver precise and contextually appropriate messages, enhancing the effectiveness of your campaigns.
A step-by-step guide to using event placeholders in WhatsApp campaigns
- Create a new WhatsApp campaign, give it a name, and choose a template for the campaign.
- Click on the "Insert Attribute" button, and you will see a menu with two options - "Base Object name" and "Events".
- In the menu, click on the "Events" option. You will see a list of custom events available for the base object.
- Click on the event from which you want to use the personalisation placeholders.
- Click on the placeholder (event property) and use it in the campaign. You also need to specify the fallback value, which is mandated by WhatsApp/Meta, for the placeholder.
A key thing to note
In one WhatsApp campaign, you can use the event placeholders of only one single event.
For example, in a campaign, if you have used the event placeholder "order_id" of the "Order Confirmed" event in one variable, let's say {{1}}. You cannot use the "shipment_vendor_name" property of the "Order Shipped" event in another variable {{2}}.
Reason for this restriction: Triggered campaigns are triggered by a specific custom event. In a flow, the event trigger will have a particular event, starting the flow automation and initiating the WhatsApp campaign. If you use any other event not in the trigger, the event placeholder value will be empty and you may send incorrect data to the message receipient.
For example, if a flow trigger is for an order_confirmed event, the WhatsApp campaign can have the event placeholders of the order_confirmed event and the placeholders of the order_shipped event cannot be used as they will be empty (because the trigger is order_confirmed).
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article