Web SDK - The ForeSee Cookies

We use cookies for two major reasons in our JavaScript code. Firstly, we use so-called performance cookies to track website visitors over time to have access to information like:

  • to know if they have been invited to complete our survey or not
  • what pages they visited on your website and in what sequence
  • store unique ID’s that connect our product to other products on your site (like Google Analytics, Adobe Marketing Cloud, etc)
  • track special values that you may elect to set (shopping cart ID’s, etc)

Under no circumstances do we knowingly tracking PII (Personally Identifiable Information). We work with customers who use our cookie to track their own values to avoid this kind of data.

We also use so-called functionality cookies to make certain features possible in our code. These cookies are short-lived and are not absolutely necessary for the general functioning of our product. The main ways we use functionality cookies are:

  • to enable communication between our tracker window and the main page
  • to enable communication between multiple open tabs
  • to communicate between the main page and any open survey windows

First vs Third-Party Cookies

We use both first and third party cookies depending on the circumstance. First party cookies (set in the origin of your website) are used mainly for performance cookies, and third-party cookies are only used for functionality cookies, when needed.

Secure (HTTPS) Cookies:

ForeSee is able to utilize secure cookies ONLY if the entire site being measured is secure (all https). The secure attribute for the ForeSee cookies keeps the cookie communication limited to SSL/encrypted transmission for HTTP-requests, so this can be used only if the entire website being measured is https. If this setting is enabled when non-https pages are available the code is unable to work on these pages. Please contact the Implementation Team for more details.

HTTPOnly attribute:

The purpose of the HttpOnly attribute in a cookie is to disallow client-side code from reading cookie information. The ForeSee scripts are client-side JavaScript code that require access to its cookie to function. Therefore ForeSee cookies do not use the HttpOnly attribute.

What Cookies are Set?

In modern code versions, the following cookies are used:

Cookie Name First or 3rd Party Type Notes
_4c_ First Performance For Code Version 19.3.0+
_fsspl_ First Performance For Code Version 19.1.x and 19.2.x
fsice 3P Functionality For Code Version 19.1.x+
_fsspl_ 3P Functionality For Code Version 19.1.x+

Code Version 19.0.x and Below

Prior to v19.1.x client code, ForeSee utilized three cookies. Two session cookies (fsr.s and fsr.a) which store information relating to the survey control and operation, as well as some basic information such as the number of pages a user has viewed, and the URL’s the user was on when they entered and left the site.

In addition to the items mentioned in the prior paragraph, the ForeSee cookie can contain Customer Passed Parameters (CPPs). This data can range from values stored within a variable, cookie, or URL parameter. To pass CPPs, special coding needs to be programmed into the survey configuration file in order to pass any additional data. This code is client controlled so they know what data is being passed when the code is implemented.

ForeSee also has a persistent cookie (fsr.r) which contains information indicating when a user has received a survey invitation in order to prevent the same user from being presented with another invitation for a specified period of time.

ForeSee Cookies

Cookieless Options

As of v19.2.0, customers will have the option of a pure-cookieless and micro-cookie tracking option. Contact your implementation team for details.

Other articles in this section:

  1. Frequently Asked Questions
  2. Testing
  3. Replay Masking
  4. Custom Survey Invitations
  5. Legacy Trigger Code (<18x)
  6. Mobile Invite
  7. The ForeSee Cookies (current article)