You can deploy Haptik's bot either with the Haptik UI or as an API. Haptik offers its own UI in the form of an SDK. 

Now users can take numerous actions on this UI (SDK). They can click on a certain button, they can hover over an image, etc., the list is endless. These actions taken on the SDK are termed as Events. You can now find out these events, in other words, listen to these events and use them if required on your website. 

Why listen to SDK Events?

You can listen to SDK Events, for two main use cases.

• You want to track SDK events on your Analytics Tool: By listening to SDK events, you will be notified every time a user performs any action on the SDK. For example, if the user hovered on the Let’s Chat icon, or clicked on the icon to open the SDK, or maybe typed and sent a message through the composer. You can now track these events by dumping them straight into any Analytics Tools like Google Analytics, Mixpanel, etc. that you have integrated on your parent page.
• You want to change things on your website's parent page in response to what happens on the SDK: In a case where a user triggers a flow to see “ROI-Calculator” within the bot and you happen to have an ROI calculator on the website as well, you can now listen to the response the user gets from the bot (which will confirm that the user was looking for ROI-Calculator), and then based on this information showcase the ROI-Calculator on your webpage itself.

How do we subscribe to or listen to these Events?

You can use the HaptikInitSettings property sdkEvents to subscribe to the SDK’s events.

window.haptikInitSettings = {
    ...
  sdkEvents: event => {
          console.log('📣 from SDK: ', JSON.stringify(event));
        }
  };
  ...
};

The event object received will contain all the properties that will help you define which event had occurred and what properties were set.

What are the different Events and their properties?

The following table lists all the events and their corresponding properties.

How can we use these Events for analytics?

Clubbing different events together will help us form funnels.

For example,  

`HAPTIK_APP_LOADED` → `HAPTIK_CHAT_BUTTON_HOVERED` → `HAPTIK_APP_EXPANDED` can form a funnel of:

1. How many times the SDK was loaded and thus the Let’s Chat button was shown on the screen. 
2. Of that, how many times the Let’s Chat button was hovered on.
3. Of that, how many times do users click on the Let’s Chat button to open the SDK.

Few more examples of similar funnels that can be built using events like: 

• `HAPTIK_BOT_PROMPT_SHOWN` → `HAPTIK_BOT_PROMPT_DISMISSED` → `HAPTIK_BOT_PROMPT_CLICKED` can be used to create a Bot prompt usage funnel.
• `HAPTIK_LANGUAGE_ICON_CLICKED` → `HAPTIK_LANGUAGE_SELECTED` can be used to create funnels to see Language change funnels.
• `HAPTIK_MIC_TAPPED` → `HAPTIK_MIC_CLOSED` can show us how many times users clicked on the mic icon but canceled the voice message before it could be sent.