Curator Blog

Curator 101: Third-Party Cookies

Matthew Orr
Experience Engineer
November 12, 2020


Tableau Server uses special browser cookies when dashboards are embedded within Curator. Since these cookies aren’t baked by Curator or by you, these are known as third-party cookies. Most of the time, these cookies are calorie-free and completely invisible to you. However, as browsers try to do more and more to protect users (like an overbearing fitness coach), these cookies are sometimes blocked, and dashboards fail to load properly. This post is all about detecting when this happens and the steps to take to fix it.

Detecting Blocked Cookies

Curator provides a setting that can check to see if third-party cookies are being blocked by users’ browsers. If it determines that they are being blocked, it will display a notice at the top to alert the user. To turn on this setting, navigate to Backend > Settings > Portal Settings > Features tab, scroll to the bottom, and look for the 3rd Party Cookies Enabled Check setting:

Getting Your Fix

Tableau Server Domain

One way to trick browsers into thinking the cookies aren’t bad for you is if Tableau Server and Curator use the same domain name. If possible, it is recommended to set up your environment to use subdomains under your domain name for each system. An example would look like this:

Tableau Server: https://tableau.yourcompany.com

Curator: https://curator.yourcompany.com

Browser Settings

If you are unable to change the URL Tableau Server uses or if some users are still experiencing issues, the only solution left is for each user experiencing issues to change their own browser settings. Here are the steps they’ll need to take.

Google Chrome

Take these steps to enable third-party cookies within Google Chrome:

  • Click on the three dots in the top-right corner and select Settings.
  • Scroll to the bottom and select Advanced.
  • In the left navigation, click on Privacy and Security.
  • Click on Site Settings.
  • Scroll down a little and click on Cookies.
  • Select Allow All Cookies. Optionally, you may also select to block 3rd party cookies in incognito instead.

If this still doesn’t solve the issue, see the section titled Still Not Working? below.

Apple Safari on MacOS

Take these steps to enable third-party cookies within Apple Safari:

  • Navigate to Safari > Preferences.
  • Click on Privacy.
  • Under Website tracking, uncheck Prevent cross-site tracking.

Apple Safari on iOS

Take these steps to enable third-party cookies on an iPhone or iPad:

  • Navigate to Settings > Safari.
  • Scroll to the Privacy & Security heading.
  • Uncheck the Prevent Cross-Site Tracking and Block All Cookies settings.

Mozilla Firefox

Take these steps to enable third-party cookies within Mozilla Firefox:

  • Click on the menu button and select Options.
  • Select Privacy & Security.
  • Under the Enhanced Tracking Protection heading, select the Custom option.
  • Under the Cookies setting, select Don’t block cookies.

Microsoft Edge

Take these steps to enable third-party cookies within Microsoft Edge:

  • Click on the three dots in the top-right corner and select Settings.
  • Select Site Permissions in the left navigation.
  • Click on Cookies and Site Data.
  • Uncheck the Block Third-Party Cookies setting.

Microsoft Internet Explorer

Note: Support for Internet Explorer will end soon. Please consider switching to a different browser.

Take these steps to enable third-party cookies within Microsoft Internet Explorer:

  • Click on the gear icon at the top right and select Internet Options.
  • Click on the Privacy tab.
  • Click on the Advanced button.
  • Select Accept under the Third-Party Cookies heading and click OK.

Still Not Working?

As of Google Chrome version 80, Chrome started enforcing an additional level of browser security. If your Curator instance and Tableau Server are on different domains (e.g. curator.yourcompany.com vs. tableau.someotherdomain.com), you’ll need to upgrade your Tableau Server in order for dashboards to support embedding. For more information on this patch, see:

https://kb.tableau.com/articles/issue/embedded-views-fail-to-load-after-updating-to-chrome-80

The Latest