Fullstory Detector

How can you detect if a website uses Fullstory?

Detecting whether a website uses Fullstory involves checking the page source for specific indicators and patterns that are characteristic of Fullstory’s implementation.

Here’s a step-by-step guide on how to do it:

1. Open the Page Source: Right-click on the webpage and select “View Page Source” or press Ctrl+U (Windows) or Cmd+Option+U (Mac) to open the page’s source code.
2. Search for Fullstory Codes: Use Ctrl+F (Windows) or Cmd+F (Mac) to open the search function and look for the following keywords:
   • fullstory.com: This indicates the presence of Fullstory’s scripts or tracking events. For example, it might appear as a script tag: <script src="https://fullstory.com/path/to/script.js"></script>
   • FS.FS: This is a common keyword in Fullstory’s JavaScript. You can search for the term to find references throughout the code.
3. Look for Fullstory Initialization Code: Check for the Fullstory initialization code snippet. It typically looks something like:window['_fs_debug'] = false; window['_fs_host'] = 'fullstory.com'; window['_fs_org'] = 'YOUR_ORG_ID'; window['_fs_namespace'] = 'FS'; (function(m,n,e,t,l,o,g,y){ ... })(document,window,document.createElement('script'),'https://fullstory.com/path/to/script.js');
4. Check for Tracking Events: Examine the page source for additional tracking events that might be related to Fullstory. Look for functions such as FS.event('event-name') which indicate that user interactions are being captured.
5. Review Network Requests: Open the Developer Tools (F12) and navigate to the “Network” tab. Look for network requests to fullstory.com or any subdomains associated with it. This indicates that Fullstory’s tracking scripts are actively running.
6. Examine Cookies: Check the cookies stored on your browser for any related to Fullstory. Look for cookies named like _fs_uid or other similar prefixes that reference Fullstory tracking.