Code File Library - Separating Files by Type

If there is a need to separate the code files into different directories, a ‘files’ path can be defined for the different types of files. The code example below shows how this can be done. Two important things to note if this is being done:

  1. There may be paths within the HTML files that need to be adjusted as well (e.g., tracker.html).
  2. The HTML files, especially the tracker.html, need to be hosted on the domain being measured.

Reminder: The paths below must be modified in each of the following files:

  • foresee-alive.js
  • foresee-test.js
  • foresee-tracker.js
  • foresee-trigger.js
  • foresee-qualifier.js (if applicable)
var $$FSR = {
'timestamp': '__buildtimestamp__',
'version': '__version__',
'build': '__buildnumber__',
'enabled': true,
'frames' : false,
'sessionreplay': true,
'auto' : true,
'encode' : true,
//'files': '/foresee/',
'js_files': '/foresee/js/',
'image_files': '/foresee/images/',
'html_files': '/foresee/html/',
'css_files': '/foresee/css/',

Other articles in this section:

  1. Explanation of Files
  2. Code Switches
  3. Disabling the Code
  4. Alternate Directory Structures
  5. Separating Files by Type (current article)
  6. Separating Files by Environment
  7. Hosting the Code from a Third Party Domain
  8. Changing Survey Behavior
  9. Using Tag Managers
  10. Replay Sampling & Pooling
  11. Testing Outside Production
  12. Flash and DHTML
  13. Customer Passed Parameters (CPPs)
  14. Minimizing Cookie Size