How do I know that FullStory is deployed successfully?

If you want to verify that FullStory has been deployed successfully on your website, there are a few methods you can use to confirm this. We’ll start with the easiest option and dive in deeper from there. 

 

Method 1: Call FS.getCurrentSessionURL in the Console

*Note: This feature is only available on FullStory Pro plans*

First, let’s start by calling FS.getCurrentSessionURL in the console of your browser’s developer tools. This allows you to easily retrieve your session link at the time of recording.

In order to do this, simply follow the steps below:

  1. Go to a page where you’d expect FullStory to be recording and open the Console in your browser's developer tools

  2. Call FS.getCurrentSessionURL(true) in the Console and hit enter

As long as FullStory is properly recording, you’ll be able to see the link for your current session.

direct_1559663860017-1559663860017.jpeg

If you’re seeing an error in the console, these errors can provide context about why recording isn’t taking place. For example, some of the common errors and reasons are listed below:

  • Null typically means that recording has been blocked or turned off. Head on over to Settings > Recording to see what settings are preventing your session from recording.

  • FS is undefined means that FullStory is loading on the page, but not recording.

  • FS is not defined means that FS has not yet been defined on this page.

 

Method 2: Check the Network Tab

If you aren’t able to retrieve your session link by calling FS.getCurrentSessionURL, you’ll want to check the Network tab in your browser’s developer tools to confirm whether Javascript bundles are being sent by following the steps below:

  1. Click on the Network tab in your browser’s developer tools

  2. Refresh the page (this step is important!)

  3. Search for ‘fullstory’ in the textbox near the top left of the window. This allows you to see all of the calls related to FullStory

  1. Confirm that the call to fs.js has a status of 200. If not, this is a sign that FullStory was not properly deployed on this page.

  2. Check for subsequent calls to “bundle” as you should see multiple “bundle” calls over time.

  3. Confirm that the call to page has a status of 200. If you’re seeing a status of 202, this means that recording has been blocked. To find out why, you’ll want to check the Response tab (see screenshot below) which should display a reason_code. You can then refer to this help article to find out what this reason_code means.

If everything looks good, this means that FullStory is successfully recording on this page.

 

Method 3: Confirm that the Snippet was Pasted Correctly

If you’ve completed the above steps but still have not identified if FullStory is deployed correctly, this likely means there is a problem with the snippet. There are two ways to find our recording snippet on your website. 

Option 1: Check the Page Source

  1. Right click on the page and select ‘View Page Source’

direct_1559663937420-1559663937420.jpeg

  1. Search for “fullstory”

Occasionally, FullStory will not load correctly based on how our recording snippet was pasted. If you’re able to see ‘fullstory’ in the source code but you weren’t able to see any sign of FullStory recording when using Method 1 and Method 2, there is likely a problem with your recording snippet.

 

Option 2: Search the Console tab 

  1. Open your browser’s developer tools

  2. Navigate to the Console tab and search for ‘fullstory’

If the recording snippet has been manipulated in any way, it can be difficult to locate. Sometimes it means that the snippet is not in plain view on the main page of your website. If you’ve completed all of the steps above and can’t find any presence of FullStory on your website, this means that FullStory was either never deployed on this page or recently removed.

Need to get in touch with us?

The FullStory Team awaits your every question.

Contact us