Major browsers like Safari, Firefox, and Chrome (including Chromium-based browsers like Edge) have added or are planning to add restrictions to third-party cookie usage. This change entails replacing third-party cookie usage patterns by web browsers with a new partitioned cookie type or blocking them entirely.

Google Chrome has announced plans to move towards a more privacy-focused web environment with initiatives like the Privacy Sandbox, which aims to provide personalization while protecting user privacy. Google is planning to introduce a new experience in Chrome that lets people make an informed choice that applies across their web browsing, including (but not limited to) third-party cookie usage.

Mozilla Firefox and Apple’s Safari have already implemented strict third-party cookie blocking by default:

  • Safari uses Intelligent Tracking Prevention (ITP) to block cookies used by advertisers to track users across sites
  • Firefox uses Enhanced Tracking Protection (ETP) for similar functionality
  • Other Chromium-based browsers, like Microsoft Edge, are expected to follow Chrome’s implementation

​
Impact on Glean Functionality

Since Glean is embedded on customers’ websites, it is classified as a third-party and this change can have an impact on critical workflows. Glean’s embedded widgets and other functionalities rely on third-party cookies for authenticating users and these would be affected if third-party cookies are blocked.

Glean has an inbuilt flow that requests users for third-party cookie access if needed. After login, you will see the following screen:

To grant access:

  1. Click on “Allow Cookies”
  2. You will see a browser prompt:

Browser prompt for third-party cookie access

  1. Click on “Allow” to grant Glean access to third-party cookies
  2. Glean will complete the login process successfully

​
Frequently Asked Questions

Was this page helpful?

Suggest editsRaise issue