Code File Library - Hosting the Code from a Third Party Domain

To save the files under the domain being measured there are some things to be aware of:

  1. All the files may be hosted on a third-party domain except for the HTML files. HTML files must be hosted ON the domain being measured, allowing them to properly access the ForeSee cookies.
  2. Split up the .html files (see Separating Trigger Code files by type). The .html path must be an absolute path in the ‘files’ path. (Change in foresee-alive.js, foresee-test.js, foresee- tracker.js, foresee-trigger.js, and foresee-qualifier.js).
  3. Modify all paths in the tracker.html file by changing the location of the JavaScript and the image path references to be to absolute paths to the file location of server.
  4. Turn off the ForeSee call to load the CSS (instructions below).**
  5. Load the content of foresee-dhtml.css within the global CSS or add a separate call to the foresee-dhtml.css on the client’s pages.

**To turn off the ForeSee invitation CSS, in foresee-survyedef.js, find and change:

CSS: 'foresee-dhtml.css',

Replace with:

CSS: false,

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
  6. Separating Files by Environment
  7. Hosting the Code from a Third Party Domain (current article)
  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