Third-Party Cookies

Most modern browsers block third-party cookies.

Therefore, the best practice is to:

  • Use the same domain for the different apps and put it behind a specific path. This prevents Sisense cookies from being third-party cookies.
    For example: companyA.com/analytics

If you do not want, or are unable, to use the solution above, you can use one of the following options instead:

  • Leverage the Web Access Tokens (WAT) feature for authentication. Note that WAT requires special licensing.
  • Allow third-party cookies via your browser settings:

Third-Party Cookie Deprecation in Google Chrome and Other Browsers

Google Chrome is planning to disable third-party cookies during 2024. Other browsers may potentially do the same. Since Sisense uses cookies for authentication, this deprecation may cause a breaking change in your solutions with embedded Sisense analytics, such as the user being redirected to the login page and the embedded solution not being loaded.

To avoid this breaking change, use one of the following approaches:

  • Use the same domain for the different apps and put it behind a specific path - this prevents Sisense cookies from being third party cookies.
    For example: companyA.com/analytics

  • For IFrame-based embedding methods (IFrame and Embed SDK): enable Cookies Having Independent Partitioned State (CHIPS) – a mechanism that allows cookies to be partitioned based on the top-level site, meaning that cookies set by one website cannot be accessed by another.
    To enable CHIPS, open Admin > Security Settings > General and toggle on Enable CHIPS for IFrame-based Embedding.

    IMPORTANT:

    The CHIPS solution is not compatible with script-based embedding methods, such as Sisense.js or Compose SDK.