How to Block Third-Party Cookies and Enable Tracking Protection in Google Chrome

Modern web browsing demands a careful balance between site functionality and user privacy. For years, third-party cookies served as the primary mechanism for advertisers and data brokers to monitor browsing behaviour across multiple domains. Google Chrome includes robust privacy settings and Tracking Protection controls designed to limit cross-site tracking, restrict third-party storage access, and grant you granular control over cookie permissions across your desktop and mobile devices.

Understanding Third-Party Cookies and Tracking Protection

First-party cookies are created directly by the website you visit, storing essential session data such as your shopping basket contents, display preferences, or active authentication credentials. Conversely, third-party cookies originate from external domains embedded within the page—such as advertising networks, analytics providers, and social media widgets. These external cookies track your digital footprint across disparate websites to build detailed behavioural profiles.

Chrome’s Tracking Protection initiative actively restricts these trackers by default, limiting cross-site cookies whilst providing fallback mechanisms for legitimate web applications. Learning how to configure these controls ensures you can eliminate persistent surveillance without breaking essential services, like institutional single sign-on (SSO) portals or embedded payment gateways.

How to Block Third-Party Cookies in Google Chrome on Desktop

Managing your cookie preferences on Windows, macOS, or ChromeOS requires navigating Chrome’s core privacy settings:

1. Launch Google Chrome on your computer.
2. Click the three vertical dots (Menu) in the top-right corner and select Settings. Alternatively, enter chrome://settings/cookies into the Omnibox.
3. From the left-hand navigation menu, click Privacy and security.
4. Select Third-party cookies (or Tracking Protection depending on your Chrome build).
5. Select the option labelled Block third-party cookies.
6. Ensure the toggle for Send a “Do Not Track” request with your browsing traffic is switched to On for added privacy.

Once enabled, Chrome automatically intercepts and blocks scripts attempting to read or write cross-site cookies during your standard browsing sessions.

Configuring Exceptions for Specific Websites

Completely blocking third-party cookies can occasionally disrupt complex web platforms that rely on cross-domain authentication or embedded iframe components. Chrome allows you to define granular exceptions:

• Allowing Cookies for a Domain: Under chrome://settings/cookies, scroll down to the Customised behaviours section. Next to Sites allowed to use third-party cookies, click Add, enter the specific domain pattern (e.g. [*.]example.com), and click Add.
• Per-Site Address Bar Control: When visiting a site that encounters functionality issues, look for the eye icon or lock/tune icon on the left side of the address bar. Click it and toggle Third-party cookies to allow temporary access for that specific domain.

Enabling Tracking Protection in Chrome on Android and iOS

Mobile browsers are equally susceptible to cross-site tracking scripts. You can harden your mobile security settings with a few quick adjustments:

On Android

1. Open the Chrome app on your Android device.
2. Tap the three dots in the upper-right corner and select Settings.
3. Under the Advanced section, tap Site settings.
4. Select Third-party cookies.
5. Choose Block third-party cookies or enable Tracking Protection.

On iPhone and iPad (iOS)

On Apple devices, iOS mandates that all third-party browsers use the WebKit rendering engine. In addition to Chrome’s in-app privacy toggles, cross-site tracking is governed by system-level permissions:

1. Open the iOS Settings application.
2. Scroll down and select Chrome.
3. Toggle off Allow Cross-Website Tracking to enforce Apple’s native WebKit tracking restrictions.

Verifying Blocked Trackers Using Chrome DevTools

Advanced users and web developers can inspect exactly which cookies and storage requests are blocked in real time:

1. Navigate to any web page and press F12 (or right-click and select Inspect) to open Chrome DevTools.
2. Select the Application tab from the top toolbar.
3. In the left sidebar, expand the Storage tree and click on Cookies.
4. Review the listed domains. Blocked cross-site cookies will display a yellow warning triangle or be flagged with a tooltip explaining that third-party cookie access was blocked by user preferences.
5. Open the Console tab to observe detailed warnings regarding partition keys and rejected storage access requests.

Frequently Asked Questions

Will blocking third-party cookies log me out of my accounts?

No. Your active login credentials and session tokens are preserved in first-party cookies created by the primary website domain. Blocking third-party cookies only affects external scripts embedded from secondary domains.

What is the difference between Incognito mode and blocking third-party cookies?

Blocking third-party cookies prevents cross-site tracking continuously across all standard browsing sessions without discarding your browsing history or first-party saved logins. Incognito mode blocks third-party cookies temporarily whilst also purging all cookies, local cache, and history the moment you close the private window.

Why do some payment processors fail when third-party cookies are disabled?

Certain older merchant payment gateways load within an iframe hosted on an external banking domain. If the gateway requires cross-site cookie verification to authenticate the transaction, blocking third-party cookies may cause an error. In such cases, temporarily allowing cookies for that merchant resolves the issue.