How to send "Zalo Notification Service" using CDP 365
"Zalo Notification Service (ZNS)" is a service that sends customer care notifications via API to phone numbers using Zalo
1. Instruction to get information for using "ZNS" in CDP system
Accessing the link Zalo Developer to log in your account
Selecting existing app or creating a new one
When clicking an app, the screen will be shown as:
We can take the information of "App ID", "App Name" and "Secret key" on this screen
We also need the information of "Refresh token" for using in CDP
We can get "Refresh token" via getting "access token"
Accessing the link API Explorer and selecting "OA Access token" type then clicking "Get access token"
We can click to copy "Refresh token"
With all information above, we have enough data to create "destination" in CDP system
2. Destination ZNS
To create ZNS destination, we need to access Channel Integration.
Hover your mouse over Settings. Choose Channel Integration.
After that, we click + button Create and select Zalo channel
Select Destination catalog as Zalo Notification Service
Fill out Name, required Info and then click Save
"App ID", "Secret Key", "Refresh Token" are information we mentioned in section 1
"Country Phone Code": 84
"Is Scheduled": true
After clicking Save, we have finished creating ZNS destination.
To send ZNS to customer, we need to use Customer Journey
3. Sending ZNS via Customer Journeys
Log into CDP 365 system, hover your mouse over Marketing -> Choose All Channels
We have 2 channels that are supporting to send ZNS
Zalo
Orchestration
Click + button to create a journey.
If you choose the channel as Journey Orchestration then you need to add 1 trigger node first (Action base or schedule trigger).
For this example, we will use Action-based node to send ZNS after the customer purchase.
Add Destination node and select ZNS destination
Choose a ZNS template, fill out necessary information, and Save
Phone number: Phone number of customer
Template data: Information we want to send to customer. Go to the ZNS template to get dynamic parameters, and map them to CDP 365 attributes. It means taking attribute values from CDP 365 and show on ZNS messages with the corresponding params.
Notes: Besides the CDP 365 attribute values, the Template data can be a fixed value.
After finishing the setting of journey, we can activate and send this ZNS to customer.
Last updated
