Inbenta tracks the actions that users perform with every product (Chatbot, Knowledge Management and Search). There are two categories of tracking: Atomic and Sessions tracking. This data is logged separately, and it is used to generate the reports that you see in the product app's Dashboards section.
Events are any interaction between the user and the interface. Note that not all data is the result of user actions. Because product configurations and implementations are extremely varied, an event could be almost anything: send an input in a chatbot conversation, clicking on a result, sending a contact form, etc.
Here is a short list of some of the events that Inbenta usually takes into account:
In atomic logs, actions are listed according to a log type. Session logs actions use data keys. This table shows all log types and data keys that come predefined in a new instance.
If an action has a log type, it can be tracked in Atomic logs. If it has a Data key, it can be tracked in Session logs. If it has both, it can be tracked in both. Here are a few examples:
|-||START||Marks the start of the session.|
|-||USER_BROWSER||Stores the browser information of the user.|
|-||MY_CUSTOM_KEY||Custom data key to track user actions.|
|SEARCH||SEARCH||Indicates the user performed a search.|
|MATCH||CLICK_MATCH||Indicates a user clicked on a result.|
|INSTANT_MATCH||INSTANT_CLICK||Indicates a user clicked on an instant result.|
A data key also has a priority level that is given to its action. The session reports use the priority of an action to decide the most important action performed by the user. This most important action becomes the result of the session. Here are a few examples:
|Priority level||Data Key|
|0 (no priority)||USER_INFO|