All Collections
Troubleshooting
Managing third-party browser cookies for SnapCall app
Managing third-party browser cookies for SnapCall app
Guillaume Chauviere avatar
Written by Guillaume Chauviere
Updated over a week ago

Depending on your browser security settings, you might see the following error message when launching SnapCall from within LiveChat, Zendesk, or Intercom integrations.

This is because SnapCall runs partially at your Livechat, Zendesk or Intercom domain (visible in the address bar) and partially at snapcall.io. Depending on your browser, you can edit the settings to allow this. SnapCall uses cookies for authentication purposes only.

Editing third-party settings for Chrome

The simplest solution is to change the browser setting back to the default. However, keep in mind that this is a browser-wide setting and could have security implications. Alternatively, can also set up your browser to make an exception for SnapCall.

Below are instructions for both options.

Option 1: Allowing all cookies

To allow all cookies across the whole web, including on SnapCall:

  1. Open Google Chrome’s settings page (chrome://settings).

  2. Click on Privacy and Security.

  3. Under Privacy, click Cookies and other site data.

  4. Under Cookies, select the Allow all cookies option.

Option 2: Adding an exception

  1. Open Google Chrome’s settings page (chrome://settings).

  2. Click on Privacy and Security.

  3. Under Privacy, click Cookies and other site data.

  4. Under Site that can always use cookies, click Add (depending on your Chrome version).

  5. Enter [*.]snapcall. io to allow cookies for the SnapCall app.

Editing third-party settings for Safari

Unfortunately, Safari currently doesn’t allow exceptions by website at this time. To allow cookies on third-party websites, follow these steps:

  1. Open Safari’s preferences: Safari > Preferences.

  2. Go to the Privacy tab.

  3. Uncheck Prevent cross-site tracking.

Safari iOS :

  1. Open Safari’s preferences: settings > safari.

  2. Disable Prevent cross-site tracking.

Did this answer your question?