FAQ - Session Recordings
Find everything regarding session recordings and replays in this section.
This happens because every tool uses a different methodology to count user activity and user inactivity and hence often the overall numbers tend to differ a bit.
GA for example depends on page views or tracked events. So for example if a user keeps browsing your home page leaves without changing the page. GA may not know how long the user interacted with your site (unless you have also setup Scroll Tracking), while Browsee automatically tracks mouse and scroll movements and understands the session interaction in more depth.
This also impacts the inactivity length when a session is expired and therefore some sessions may be counted as two in GA while it maybe just one session in Browsee. Hence the sessions counts can differ. More on this topic here.
I can see N number of recordings on my dashboard but there were more sessions on my website. Where are those recordings ?
In addition, depending on your pricing plan, if your site has more sessions than plan's quota we may use random sampling to record a subset of sessions.
To check total tracked sessions on your site instead of just recordings you may toggle the "Recordings Only" button on the session listing screen.
Toggle Reocrdings Only to see all sessions tracked by Browsee
Yes, Browsee gives you a lot of flexibility around the sessions that you want to record. This means that you get more valuable recordings at the same price.
- 1.Landing URLs like "contains /app" or "contains /product/".
- 2.UTM source like "cpc", "ads", etc.
- 3.Country like "USA", "India", "France", etc.
Yes, you get complete flexibility around what not to record.
- 1.Landing URLs like "contains /blog" or "contains /article/".
- 2.Devices like "Mobile", "Desktop", etc.
- 3.IP addresses for your team or company like "192.168.32.12", etc.
- 4.Total session time < "2 secs"
These ignored session recordings will not be counted in your quota then. Hence, you will get more valuable recordings in the same pricing plan.
Based on your pricing plan, Browsee decides how many sessions will be recorded per project or session quota per project.
For a $100 plan, about 1000 sessions will be recorded for one project every day. If you have 2 projects under the same account, about 500 sessions will be recorded for each project.
Browsee computes the sampling rate based on the previous day's sessions. So, if you are running a heavy campaign for a single day, you may notice a reduced number of recordings on the next day. However, it will get normalized over time and we will record the sessions as per your monthly quota.
Sometimes, you may not be able to see the images and CSS as your website. The reason might be:
- 1.Your website is non-SSL and Browsee will not be able to server non-SSL images and CSS
- 2.Also, sometimes the webservers are configured to not let the images be downloaded under a different domain
This may happen if you have set an option in Browsee where you choose to prioritize or deprioritize recordings for some of your URLs.
You can check the saved sessions later from the dashboard by clicking on the "Favorite Sessions" button in the session listing page as shown below:
Browsee tags your sessions based on the session data when there is a user experience issue. You can find your rage click sessions:
In case there are any irrelevant rage clicks like clicks on image sliders etc, you can mark them resolved and we will not mark them in the future.
Browsee tags the session recordings based on user behavior and emotions like rage, confusion, expectation mismatch, etc. Take advantage of these tags to minimize the human effort of watching sessions.
Yes, you can send any user related information like name, email, database ID or tags like "paid", "unpaid", "in-trial" etc with an API call. Kindly refer to this document to understand how can you send this information to Browsee.
Browsee does not capture native dropdowns like <Select></Select> as the changes in their values do not cause any DOM mutations and hence we don't get to know whether the value has been changed or not. We can only capture the events where a change has been made at the DOM level. Unfortunately, the change in the Dropdown value does not cause any DOM mutations and hence there is no way to record the changed value of the dropdown.