Are you having trouble locating a session within FullStory? This article identifies the most common reasons why.
Reason #1: Your data capture settings prevent capture.
Go to Settings > Data Capture and Privacy > Data Capture to see if you have any settings that would help explain why the session was never captured. From there, ask yourself the following questions:
- Is data capture toggled on?
- Are you capturing the domain this user visited?
- Are you capturing sessions from this geographical region?
- Are you blocking this user's IP address or user agent?
Reason #2: The session falls outside your plan's session replay retention period.
Double-check your plan's session replay retention under Settings > Account Management > Subscription within your FullStory account when searching for older sessions.
If your Session replay retention is set to 1 month, but you are trying to locate a session captured 6 months ago, this would explain why you cannot see this session. Once the Session replay retention period has passed, these sessions are permanently deleted and non-recoverable.
Reason #3: Your account exceeded its monthly session limit during that time frame.
Another possibility is that your FullStory account exceeded its monthly session limit when this user accessed your website or mobile app. When you exceed your monthly session limit, data capture will be paused until the next billing cycle, and all Admins on the account will be notified via email.
To troubleshoot, try searching for all sessions captured in FullStory on that date. If sessions were captured consistently on that date, you can rule this possibility out.
Reason #4: FullStory isn't capturing on that page/screen.
Still no luck? As a next step, confirm that FullStory is correctly deployed on the page/screen. A quick way to do this is to search for other sessions within FullStory where users visited that specific URL during that time.
If you can't confirm this within FullStory, follow the steps outlined in this help article to verify whether FullStory is correctly deployed on the page/screen.
Reason #5: This user has installed a third-party extension or uses strict browser settings that block data capture.
If FullStory has never captured any sessions for a specific user or if you're able to view some older sessions but no recent ones, it's always possible that this user has either installed a third-party extension (such as Ghostery or uBlock) or has strict browser settings in place which can block data capture. The best way to confirm this would be to contact the user directly.
Noticing a good chunk of your users are using a third-party extension to block data capture? You might want to check out the FullStory Relay. The FullStory Relay is an open-source project that points to your first-party domain instead of FullStory's domain, so it should allow you to circumvent script-blocking extensions and capture these users. You can learn more about the FullStory Relay here.
Reason #6: Custom logic is being applied to sample sessions.
It's possible that sampling rules were applied to your account via custom code. This prevents some sessions from being captured.
We explain in more detail here why we do not recommend sampling.
Still have questions? Feel free to contact us here with as much information as possible regarding the missing session, including their IP address, user agent, and specific URL(s) visited.