Skip to main content


Add Analytics Tag

Chatbot users come from everywhere but mainly from advertisements you placed. In order to improve the effectiveness of the advertisements, you must first understand your users’ preferences. Toggling on the Analytics on the nodes could help you to track the users’ footprint.

Analytics is a function which counts the number of times when users pass through a node. As a result, by creating analytics with “Category”, “Action” and “Label” on any nodes, you could classify the user journey on WOZTELL and have visualized data on “Dashboard” for your future marketing strategy.

Sample Tree Structure

Imagine you are running a chatbot sales campaign for your fashion store and users would activate the chatbot from an outdoor pop-up store or from your online Facebook ad . As a result, you would like to track down the chatbot users coming from different entry points into your chatbot sales campaign.

  1. Select the nodes where you set the entry points for your outdoor pop-up store or your online Facebook ad.

  2. Toggle the Analytics button and add the “Category”, “Action”, “Label” accordingly.

    Now, whenever a user is activating the chatbot from a specific entry point, WOZTELL will track the user journey of the user accordingly.

  1. On the top panel, select "Dashboard" to enter the dashboard page, which can display visualized analytics data.
  1. In "Analytics Overview", you will be able to know which node and conversation flow the participants had passed through. Using the fashion store as an example, you can track and display the statistics of each conversation flow. It helps with your future marketing campaign development.

You could use the analytics data to discover the user’s preferred experience of the chatbot. For example, you may discover the users are more engaged in “Campaign 1” which is the outdoor pop-up store. You can now have better planning for the next marketing strategy according to the preferences of the users.


In addition, users can also directly apply variable as the analytic tag by selecting the variable options below.


Analytics in the basic version is very useful because you can easily track the total count of interaction in a tree node. However, you can only track the data on a node level. If you want to track the performance based on how the user interacts within the node, then you will need to set the analytics label programmatically.

When a node with analytics toggled on is executed for a member, either from trigger or redirect, an analytics event will be recorded. Advanced analytics is a Promise function. An analytics event is an object consisting of category, action, label and value. value is a number field, and the other 3 are string fields. You can use the resolve callback of the promise function to resolve the analytics event.

The recorded analytics can be found in the Dashboard page. Analytics can be grouped and filtered by category, action and label.

For more details on the advanced chatbot concept & usage, you may visit here.

Sample Tree Structure

Following the below example, as you are tracking the interaction after the users have answered a question, the analytics setup should be done in the next node. (e.g. if your response in Question 1 (Text Input) is a question asking “Are you interested? ”, then the analytics of whether the user is interested or not interested should be tracked on the next node which is Question 2). The system will match the next layer of node after the user answered your question, (i.e. Question 2).

Sample Tree Structure - Advanced Analytics
Sample Tree Structure - Advanced Analytics

Advanced Analytics
Advanced Analytics
  1. Click “Advanced” after toggling the “Analytics”, and input the following script as example:
return new Promise((resolve) => {
category: "Question 1",
action: "User Input",
label: `${}`
  1. In the above example, the label will be generated based on the text that the user has typed. For example, if the user typed “Interested”, then the label will be ”Interested”. You may also customize the category and action based on the message event if needed.

You can always change how you want to save the analytics category/action/label in terms of message event. For more information on message event references, see the reference documentation