Need a clarity on how the sessions are getting calculated in Metrics.
Are the session calculated in metrics only on the bot load and maybe the user did not interact with it or the sessions in metrics are the ones where user has interacted with the bot?
There is a huge difference in the number of sessions which are stored inside the analytics table and the ones displayed in the overall Bot Metrics. The ones in the overall bot metrics being higher.
We want to understand how the values are calculated for the overall bot metrics.
@Raj_Bhartiya Based on the configurations of the bot, sessions can be bot-session (depends on bot messages only) or user-session (there must be user reply).
You can filter for Event = user-session & bot-session, summarise by count, and group by Event column. Compare both the numbers with the Overview session count.
Can you please elaborate more on when the bot-session and user-session event is inserted inside the user engagement events table?
Will user-session event be fired when user types something/clicks on a button?
And how are these related to sessionId and Uid?
@Shraeyas bot-session if fired when bot sends out the first message in a session, while user-session is fired when the user replies to the bot.
SessionID and UID remains the same as before, and does not impact other two metrics.
So let’s take this scenario. The bot sends the first message to the user, and the user also replies. So we’ll have bot-session and user-session event sent.
Let’s say the user refreshes the page, and we have the enable History flag to true, the bot will resume the conversation from where he left. But will the bot-session and user-session event be sent (again) for this case, given that a new session was not started?
Hi, @Sanskrity How the sessions are getting calculated in the metric section?
As because we are getting different counts in our analytics table.
In the below ss you can see that the count of session id is 2404 but for analytics 24127 and the distinct count is 500.
Also, we have created a report at the bot level where we have summarized the data by profile_device and the Number of distinct values of sessionId, in that the distinct count is 407.
Please note we have added timestamps for 01/12/2022 to 19/12/2022.
@Shraeyas No, the events will not be sent again in the same session.
@AmanKumar For any bot, session may be calculated based on bot-session (bot sent welcome message) or user-session (user replied and it’s a 2-way communication). To check - you can filter for Event = user-session & bot-session, summarise by count, and group by Event column. Compare both the numbers with the Metric sessions count and there should be a match.
A post was split to a new topic: User Engagement Table timestamps
2 posts were merged into an existing topic: User Engagement Table timestamps