Session analytics
Session analytics is an advanced tool for user experience and behavior analytics, designed to help businesses optimize their websites by providing in-depth insights into user interactions. With session recordings, companies can capture and replay user actions, analyze click patterns, and visualize user flows, gaining a comprehensive understanding of user behavior and usability challenges.
In addition to session replays, Session Analytics offers network and console log tracking, delivering detailed information on failed API calls, performance bottlenecks, and error messages. This detailed logging streamlines debugging and accelerates issue resolution.
A key feature is funnel analysis, which enables businesses to track user progression through specific conversion paths. By identifying drop-off points, companies can fine-tune these stages to improve conversion rates.
By leveraging these capabilities, businesses can make data-driven decisions, enhancing the user experience and overall website performance.
Enable session analytics
If you are not on our session recording plan, contact our support team to enable it.
- To begin, you need to install the PLuG SDK on your website.
- The PLuG SDK enables you to identify users, allowing sessions to be tracked at the individual user level. This facilitates easier search and mapping between your system and DevRev, streamlining user management and improving your ability to analyze user-specific behavior. For detailed instructions on identifying users with the PLuG SDK, refer to Identify your users with PLuG.
- Once the initialization is complete, session recording for users will automatically begin. For detailed instructions on session recording options, refer to Session recording options and data masking.
Session calculation
-
Session duration: A session begins when a user first interacts with your site or app and continues until the user closes the tab, navigates away, or if there is a period of inactivity.
-
Single session across tabs: Interactions across multiple tabs or windows are treated as part of a single session for the same user. We consolidate these interactions to provide a unified view of user behavior.
-
Session timeout: If a user remains inactive for 30 minutes, the current session ends, and a new session starts when the user becomes active again. This can result in multiple sessions for a single user if they return after a break.
Track events
For detailed information about Track events, refer to Track events.
