ForeSee Developer Portal

Everything you need to configure and optimize your ForeSee products. Home of developer documentation, implementation guides, and release notes.

Blueprint

ForeSee uses cookies for two major reasons in our JavaScript code. Firstly, a so-called performance cookies is used to track website visitors over time, which provides information like:

  • If they have been invited to complete a survey or not.
  • What pages they visited on your website and in what sequence.
  • Store unique ID's that connect ForeSee products 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 does ForeSee knowingly tracking Personally Identifiable Information (PII). ForeSee works with customers who use ForeSee's cookie to track their own values and wish to avoid this kind of data.

ForeSee also uses so-called functionality cookies to make certain features possible in the ForeSee code. These cookies are short-lived and are not absolutely necessary for the general functioning of ForeSee products. The main purposes for using functionality cookies are:

  • To enable communication between ForeSee's 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-Party versus Third-Party Cookies

ForeSee uses both first-party and third-party cookies depending on the following circumstances: 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.

**Note:** CX Measurement survey invitations do not appear when third-party cookies are blocked (this applies to Web SDK 19.0.0+). At this time, none of the supported browsers block third-party cookies by default.
###Secure (HTTPS) Cookies:

Secure cookies can be enabled on Web SDK 19.4.0+ from within CX Suite. However, the entire site must be on HTTPS (otherwise functionality could be impacted).

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 Name1st/3rdTypeNotes
_4c_mc_FirstPerformanceFor Code Version 19.4.0+ (Micro-cookie option)
_4c_FirstPerformanceFor Code Version 19.3.0+
_fsspl_FirstPerformanceFor Code Version 19.1.x and 19.2.x
fsiceThirdFunctionalityFor Code Version 19.1.x+
_fsspl_ThirdFunctionalityFor Code Version 19.1.x+
acs.tFirstFunctionalityFor Code Version 19.0.x+

Updated about a year ago

Cookies


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.