Next-Gen App & Browser Testing Cloud

Trusted by 2 Mn+ QAs & Devs to accelerate their release cycles

How to Disable Cross-Site Tracking

To disable cross-site tracking, open your browser's privacy settings and turn on its tracking-prevention control. Safari has Prevent Cross-Site Tracking, Chrome lets you block third-party cookies (and offers Tracking Protection), Firefox uses Enhanced Tracking Protection, and Edge has Tracking Prevention with Basic, Balanced, and Strict levels. Each one is a single toggle or radio option you flip on to stop third-party trackers from following you across sites.

Below is a complete, browser-by-browser walkthrough for desktop and mobile, plus what these settings mean for web testing, analytics, and privacy verification.

What Is Cross-Site Tracking?

Cross-site tracking is the practice of following a user's activity across multiple, unrelated websites to build a behavioral profile, usually for advertising. It works mainly through third-party cookies and embedded trackers: when site A loads a script, pixel, or iframe from an ad or analytics network, that same network is also embedded on sites B and C. Because the network's cookie is shared everywhere it appears, it can recognize you on each site and stitch your visits together.

A simple example: you look at a pair of shoes on a shopping site, then see ads for those same shoes on a news site minutes later. That hand-off is cross-site tracking. The mechanisms involved include:

Third-party cookies — small files set by a domain other than the one in your address bar, readable each time that domain reappears elsewhere.
Tracking pixels and scripts — invisible images or JavaScript from ad networks that report your page visit back to the tracker.
Fingerprinting — combining browser, device, and configuration details to identify you even without cookies.
Social widgets and embeds — like buttons, comment boxes, and embedded videos that load third-party code able to recognize you.

Disabling cross-site tracking blocks or partitions these third-party cookies and trackers so a network embedded on many sites can no longer link your activity into one profile. Crucially, it does not block first-party cookies from the site you actually chose to visit, so logins, carts, and saved preferences on that site keep working. The boundary between first- and third-party is governed largely by the cookie's SameSite attribute, which controls whether a cookie is sent on cross-site requests at all.

Method 1 - Disable in Safari (macOS and iOS)

Safari has the most user-friendly control of any browser: a single Prevent Cross-Site Tracking checkbox that is enabled by default. Apple's Intelligent Tracking Prevention (ITP) does the heavy lifting behind it, automatically isolating and expiring third-party cookies.

On macOS:

Open Safari, then click Safari > Settings (older versions say Preferences) in the top menu bar.
Select the Privacy tab.
Find the checkbox labeled Prevent cross-site tracking.
Check it to block tracking, or uncheck it to allow tracking. Changes apply immediately, no restart needed.

On iOS / iPadOS:

Open the Settings app (not Safari itself).
Scroll down and tap Safari.
Under the Privacy & Security section, find Prevent Cross-Site Tracking.
Toggle it on (green) to block trackers, or off to allow them.

Bonus (iOS app tracking): Safari's toggle stops cross-site tracking in the browser, but iOS also has a separate cross-app control. Go to Settings > Privacy & Security > Tracking and turn off Allow Apps to Request to Track so native apps cannot ask for your advertising identifier. The two settings are independent, so turn on both for full coverage.

Because changing Safari's settings differs between desktop and a physical iPhone or iPad, testers often confirm the exact toggle path on real hardware. See changing Safari settings on real iOS devices for the device-level walkthrough.

Method 2 - Disable in Chrome

Chrome does not use the phrase "cross-site tracking" directly. Instead, you control it by blocking third-party cookies and, in newer builds, by enabling Tracking Protection. Here is the standard path on desktop:

Click the three-dot menu in the top-right corner and choose Settings.
Select Privacy and security from the left sidebar.
Click Third-party cookies (older versions show this under Cookies and other site data).
Choose Block third-party cookies to stop cross-site tracking, or Block third-party cookies in Incognito for a lighter option.
If your build shows a Tracking Protection panel, toggle it on to limit trackers even where some cookies are allowed.

On Android, the steps mirror the desktop flow: tap the three-dot menu, go to Settings > Privacy and security > Third-party cookies, and select Block third-party cookies. Note that blocking all third-party cookies in Chrome is stricter than Safari's approach and is more likely to affect embedded logins or shared carts.

Method 3 - Disable in Firefox

Firefox bundles tracker blocking into a feature called Enhanced Tracking Protection (ETP), which is on by default. It offers three levels so you can balance privacy against site compatibility:

Standard — the default; blocks known cross-site trackers and social trackers while keeping most sites working.
Strict — blocks more trackers, third-party cookies, and fingerprinters, but may break some sites.
Custom — lets you individually choose cookies, trackers, cryptominers, and fingerprinters to block.

To change the level on desktop:

Click the hamburger menu (three horizontal lines) and choose Settings.
Select Privacy & Security in the left sidebar.
Under Enhanced Tracking Protection, pick Standard, Strict, or Custom.
For Custom, tick Cookies and set it to Cross-site tracking cookies or All third-party cookies, then reload affected tabs.

Method 4 - Disable in Edge

Microsoft Edge uses a feature named Tracking Prevention, set to Balanced out of the box. Like Firefox, it offers tiered levels:

Basic — blocks only malicious trackers; allows most personalization and ads.
Balanced — the default; blocks trackers from sites you have not visited while keeping content mostly intact.
Strict — blocks the majority of trackers across all sites, offering the strongest protection.

To set the level:

Click the three-dot menu in the top-right corner and choose Settings.
Select Privacy, search, and services from the left sidebar.
Under Tracking prevention, make sure the feature is toggled on.
Choose Basic, Balanced, or Strict. Select Strict for the closest equivalent to fully disabling cross-site tracking.

Extra Tools Beyond Browser Settings

Built-in toggles handle most cross-site tracking, but two add-on layers go further when you want stronger or more consistent blocking across browsers:

Privacy extensions — tools like uBlock Origin and Privacy Badger block tracker scripts and pixels as a page loads, catching trackers that survive cookie settings (including some fingerprinting). They apply the same rules in every browser that supports them, so behavior is more uniform than per-browser toggles.
VPNs — a VPN encrypts your traffic and masks your IP address, which limits IP-based and network-level tracking. It does not stop cookie- or script-based cross-site tracking on its own, so treat it as a complement to browser settings and extensions, not a replacement.

Browser-by-Browser Summary

Each browser names and defaults the feature differently. The list below maps the control you need, where to find it, and its default state:

Safari: Feature — Prevent Cross-Site Tracking. Where to find it — Settings > Privacy (macOS) / Settings > Safari (iOS). Default state — On.
Chrome: Feature — Block third-party cookies / Tracking Protection. Where to find it — Settings > Privacy and security > Third-party cookies. Default state — Allowed (rolling out).
Firefox: Feature — Enhanced Tracking Protection. Where to find it — Settings > Privacy & Security. Default state — On (Standard).
Edge: Feature — Tracking Prevention. Where to find it — Settings > Privacy, search, and services. Default state — On (Balanced).

Because each engine implements protection differently, the same website can behave inconsistently from one browser to the next. That variance is exactly why web browsers do not always show the same websites identically.

Impact on Web Testing and Analytics

For testers and developers, cross-site tracking prevention is not just a privacy toggle, it changes how your application behaves. Anything that depends on third-party cookies can silently break, so you need to test with these protections both on and off. Watch for:

Single sign-on and embedded logins — federated auth that relies on a third-party cookie or an iframe can fail when the cookie is partitioned or blocked.
Analytics and attribution — cross-domain tracking, conversion pixels, and remarketing tags may under-report or stop firing entirely.
Embedded content — payment widgets, chat tools, maps, and social embeds that set third-party cookies can lose state.
A/B testing and personalization — tools that store an identifier in a third-party context may treat returning users as new.

The takeaway: validate critical flows under the strictest common configuration (Safari ITP, Firefox Strict, Edge Strict, Chrome with third-party cookies blocked), not just under a permissive default, so real users with privacy protections on do not hit broken paths.

Common Mistakes and Troubleshooting

Confusing it with blocking all cookies — disabling cross-site tracking only targets third-party cookies. Blocking all cookies also kills first-party logins and carts, which you usually do not want.
Looking in the wrong menu on iOS — Safari's toggle lives in the system Settings > Safari app, not inside Safari's own UI. Many users hunt in the browser and give up.
Expecting it to stop all ads — tracking prevention reduces personalized ads and profiling, but you will still see contextual ads. It is a privacy tool, not an ad blocker.
Forgetting to reload tabs — cookie and tracker settings often apply only to newly loaded pages. Refresh open tabs (or restart the browser) before testing the effect.
Per-site exceptions overriding the global setting — a site you previously allowed can keep tracking. Clear site permissions or check the per-site shield icon if blocking does not seem to work.

Conclusion

Disabling cross-site tracking comes down to one privacy control per browser: Safari's Prevent Cross-Site Tracking, Chrome's block-third-party-cookies and Tracking Protection options, Firefox's Enhanced Tracking Protection, and Edge's Tracking Prevention. Flip the toggle or pick the Strict level, reload your tabs, and third-party trackers can no longer stitch your activity across sites. For developers, remember that these same settings change how your application behaves, so test critical flows across multiple real browsers to make sure privacy and functionality both hold up.

Frequently Asked Questions

What does disabling cross-site tracking actually do?

It stops third-party cookies and trackers embedded on one site from following you across other sites. Advertisers and analytics networks can no longer stitch your activity into a single profile, so you see fewer personalized ads and share less behavioral data across unrelated domains.

Does blocking cross-site tracking break websites?

Mostly no. Core browsing works fine, but some features that rely on third-party cookies, such as embedded logins, social widgets, or shared carts across domains, may stop working. Browsers like Safari and Firefox add smart exceptions to limit breakage while still blocking trackers.

Is preventing cross-site tracking the same as blocking all cookies?

No. Cross-site tracking prevention targets third-party cookies and trackers from other domains, while first-party cookies from the site you are visiting still work. Blocking all cookies is stricter and far more likely to break logins, carts, and saved preferences.

Is cross-site tracking disabled by default in any browser?

Yes. Safari enables Prevent Cross-Site Tracking by default, Firefox ships with Enhanced Tracking Protection on Standard, and Edge defaults Tracking Prevention to Balanced. Chrome historically allowed third-party cookies by default and has been rolling out Tracking Protection more gradually.

How do I verify that cross-site tracking is actually blocked?

Open the browser's developer tools, load a page with third-party embeds, and check the Application or Storage tab for blocked third-party cookies. Privacy report panels in Safari and Firefox also list the trackers they have prevented from loading on the current page.

Does a VPN stop cross-site tracking?

Not by itself. A VPN encrypts your traffic and hides your IP address, which limits IP-based and network-level tracking, but it does not block the third-party cookies, scripts, and pixels that drive most cross-site tracking. Use a VPN alongside your browser's tracking prevention and a privacy extension, not as a replacement.

How do I stop cross-app tracking on my iPhone?

Cross-app tracking is separate from Safari's cross-site setting. Open Settings > Privacy & Security > Tracking and turn off Allow Apps to Request to Track. This blocks native apps from accessing your advertising identifier, while Safari's Prevent Cross-Site Tracking handles trackers inside the browser.