Zalo
I - Overview
Zalo channel allows you to connect CDP 365 with Zalo Official Account and determine the desired message template to be used in Customer Journey.
To create a destination, follow the step below:
Step 1 - Choose a catalog: There are many vendors which provides the services and CDP 365 could also connect with them. Each vendor is trated as a catalog. When creating a new destination, you are able to choose a type that match your business demand.
Next Steps: Depending on the catalog you choose, the step taken to configure a destination will vary. See more details in the next part.
II - Catalogs
1. Zalo Official Account - Zalo OA
STEP 2 - General Information
Fields that having the red asterisk * are consider required fields, you must fill the information to be able to move to the next step.
Group | Fields | Description |
---|---|---|
General Information | Destination Name * | The name of the destination. You could choose any language you want |
Description | Enter whatever you want to describe the destination | |
Configure fields | App ID * | The ID of your Zalo OA App |
OA ID * | The ID of your Zalo OA Account | |
Secret Key * | The Secret Key of your Zalo OA Account | |
Refresh Token * | The Token of your Zalo OA Account | |
Receiver * |
| |
Is Schedule (true or false) | ||
General Settings | Frequency Capping Delivered rate | See the description of each option here |
STEP 3 - Choose A Template
CDP 365 provides many built-in message templates to help you diversify the content sent to your audience, so in this step, choose any templates you want to be used in Customer Journeys.
<gif chojn template>
2. Zalo Notification Service - ZNS
STEP 2 - General Information
Fields that having the red asterisk * are consider required fields, you must fill the information to be able to move to save the destination.
Field | Description |
---|---|
App ID * | The ID of app |
OA ID * | The ID of your Zalo OA Account |
Secret Key * | A piece of code used to unlock the application |
Refresh Token * | Used to generate new access token |
Country Phone Code (Ex: 84) | Area code for the country |
Is Schedule (true or false) |
After creating ZNS destination, you could use it in Customer Journeys like below picture:
Fields | Description |
---|---|
Variant name | Input the title of the message so that you could differentiate it with the others. |
Phone number | The phone number registered for Zalo Account |
Tracking ID | Allow transmit customized content to ZNS to track a certain type of data according to your demand. For instance, the value here could be Order ID to know which transaction the message sent belongs to. |
Template ID | The ID of the template provided by Zalo |
Template data | The value of the fields that required by the template |
Last updated