# Third-Party Cookies

> How to ensure that Sisense is not considered 3rd party cookies and is therefore not blocked.

*Source: https://docs.sisense.com/main/SisenseLinux/3rd-party-cookies.htm*

---

Last updated: June 10, 2026

|  |  |
| --- | --- |
| [Tier](https://www.sisense.com/pricing/#pricing) | [Deployment](https://docs.sisense.com/main/SisenseLinux/introduction-to-sisense-cloud-managed-services.md#ComparisonofManagedCloudandSelfHosted) |
| Enterprise | Cloud     On-Prem |

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)](https://docs.sisense.com/main/SisenseLinux/using-web-access-token.md) feature for authentication. Note that WAT requires special licensing.
- Allow third-party cookies via your browser settings:
  - [Google Chrome](#)

    1. At the top right of your Chrome window, click the three-dot menu ![More options (three dots) icon](https://docs.sisense.com/main/Resources/Images/3_dots.png) > **Settings**.
    1. From the left navigation bar, select **Privacy and security**.
    2. Click **Cookies and other site data**.
    3. Select the desired option:

       - Allow all cookies
       - Block third-party cookies in Incognito
       - Block third-party cookies
       - Block all cookies (not recommended)

    For more information about managing cookies in Chrome, see <https://support.google.com/chrome/answer/95647>.
  - [Microsoft Edge](#)

    1. At the top right of your Chrome window, click the three-dot menu ![More options (three dots) icon](https://docs.sisense.com/main/Resources/Images/3_dots.png) > **Settings**.
    1. From the left navigation bar, select **Cookies and site permissions**.
    2. In the Cookies and data stored section, click **Manage and delete cookies and site data**.
    3. Turn off the **Block third-party cookies** toggle.

    For more information about managing cookies in Edge, see <https://cookie-script.com/knowledge-base/enable-cookies-edge>.
  - [Mozilla Firefox](#)

    1. At the top right of your Firefox window, click the three-line menu ![Menu icon](https://docs.sisense.com/main/Resources/Images/ThreeLineMenu.png) > **Settings**.
    1. From the left navigation bar, select **Privacy & Security**.
    2. In the Enhanced Tracking Protection section, select the desired option:

       - Standard
       - Strict
       - Custom

         - If you select **Custom**, you must then select the desired level of cookie blocking from the drop-down list.

    For more information about managing cookies in Firefox, [see https://support.mozilla.org/en-US/kb/third-party-cookies-firefox-tracking-protection](https://support.mozilla.org/en-US/kb/third-party-cookies-firefox-tracking-protection).
  - [Apple Safari](#)

    1. Select **Preferences > Privacy**.
    2. Select the desired option for Cookies and website data:

       - Always block
       - Allow from websites I visit
       - Always allow
       - Allow from current website only

    For more information about managing cookies in Safari, see <https://help.apple.com/safari/mac/8.0/en.lproj/sfri11471.html>.

## Third-Party Cookie Deprecation in Google Chrome and Other Browsers

Some browsers have been disabling, or are planning to disable, third-party cookies. 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)](https://developers.google.com/privacy-sandbox/3pcd/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.

  **Note:**

  Make sure to check if your browser is compatible with CHIPS: [Browser Compatibility with CHIPS](https://developer.mozilla.org/en-US/docs/Web/Privacy/Privacy_sandbox/Partitioned_cookies#browser_compatibility).