Session Analytics provides an understanding of session usage patterns by the bots. With Session Usage reports you can :
Dig deeper into every bot session with your customers and understand how exactly you are charged for it
Effectively monitor how each of your bots is performing across various channels
Reduce your Admin’s effort to manually keep track of the number of sessions consumed on a periodical basis
Gain insights on the historical consumption of your bot to create or edit your existing bot flows
Easily analyze the tickets associated with every logged session and know the trend of the issues your customers are facing
How to access the session usage report?
You can access the report from three places:
Click on Admin->Billing-> Session Usage reports
Go to on Reports->and click on the card ‘Bot session consumption’
The session usage report, by default, has data filtered for the past 30 days, you can change the report filters to see data beyond the 30-day timeframe. The report has the below-mentioned widgets -
Sessions consumed: Total count of consumed sessions for the time period selected on the report
Session consumption trend: Daily count of consumed sessions as a trend line
Bot based session consumption volume: Count of sessions consumed split by the different bots available in the account
Channel-based session consumption volume: Count of sessions consumed split by the different channels on which bots are deployed
Monthly session consumption volume: count of sessions consumed on a monthly level ( depends on the date filter applied for the report)
Metrics :
Sessions count: provides the count of all the unique sessions corresponding to all the filters/aggregations applied on the report
Sessions: count of all the different tickets that were a part of any of the sessions
Filters/Aggregations/Underlying data columns :
Bot name: Bot name as available on the bots UI,
Bot version: Bot version corresponding to each bot in the bot builder UI
Channel: Channel on which a conversation was triggered, one session can have conversations spanning across multiple channels
Conversation ID: Unique id corresponding to a conversation with a bot
Customer: Unique identifier for a customer interacting with a bot
Session start time: The timestamp at which the session was initiated (Timezone:UTC)
Conversation created at The timestamp at which the conversation was initiated (Timezone :UTC )
Conversation updated: The timestamp at which the conversation was last updated (Timezone :UTC )
Session ID: The unique id corresponding to every session consumed by an account
Note:
The data in this report is available from 4th February 2022 onwards
Check the underlying data on the ‘Sessions consumed’ widget, to get a session- conversation mapping - one session can have multiple corresponding conversations.