How to Configure and Customise Tracking Prevention Levels and Exceptions in Microsoft Edge

Modern commercial websites and advertising networks routinely deploy third-party trackers, supercookies, cryptomining scripts, and fingerprinting APIs to build comprehensive behavioural profiles across your browsing sessions. While some tracking scripts facilitate essential site analytics or single sign-on functionality, excessive third-party scripts introduce privacy risks and degrade page load performance. Microsoft Edge mitigates these risks natively through its built-in Tracking Prevention engine.

Powered by the open-source Disconnect tracking protection lists, Edge automatically detects and blocks invasive cross-site trackers across three configurable enforcement levels: Basic, Balanced, and Strict. This tutorial details how each tracking tier functions, how to manage site exceptions for trusted services that require third-party cookies, and how to inspect blocked trackers directly from the Edge address bar.

---

Understanding Edge Tracking Prevention Levels

Microsoft Edge categorizes tracking protection into three tiers. Understanding the technical distinctions helps you balance privacy protection against website functionality:

Enforcement Level	Trackers Blocked	Impact on Web Compatibility	Recommended Usage
Basic	Blocks known malicious cryptominers and fingerprinters only. Allows commercial cross-site trackers.	Minimal. Websites function with zero breakage; personalized ads persist.	Environments where legacy corporate intranets break under standard cookie restrictions.
Balanced (Default)	Blocks cryptominers, fingerprinters, and cross-site trackers from sites you haven’t visited.	Low. Most websites render and function normally with reduced cross-site profiling.	Everyday consumer and enterprise browsing; balances privacy and functionality.
Strict	Blocks cryptominers, fingerprinters, and the vast majority of cross-site trackers across all sites.	Moderate to High. Some embedded videos, login widgets, and dynamic forms may not load.	Maximum privacy, privacy-sensitive workflows, and banking sessions.

---

Step 1: Navigating to Tracking Prevention Settings

To configure your global tracking prevention rules in Microsoft Edge:

1. Launch Microsoft Edge on your PC or Mac.
2. Click the Settings and more (…) three-dot menu icon in the upper-right corner of the browser window.
3. Select Settings from the drop-down menu.
4. In the left-hand navigation pane, click Privacy, search, and services.
5. At the top of the privacy page, locate the Tracking prevention section. Ensure the master toggle switch is turned On.

---

Step 2: Selecting Your Desired Protection Level

Within the Tracking prevention category, you will see three interactive cards representing the three enforcement tiers:

1. Click on Balanced (the recommended default) or Strict (for maximum privacy protection).
2. Observe the operational checkbox immediately below the tiers: Always use “Strict” tracking prevention when browsing InPrivate.
   • Ensure this option is ticked. This guarantees that whenever you open a private browsing window (Ctrl + Shift + N), Edge automatically elevates protection to the Strict tier, even if your everyday browsing remains set to Balanced.

---

Step 3: Inspecting and Clearing Blocked Trackers

Edge keeps a detailed running ledger of blocked tracking requests:

1. Click on Blocked trackers located directly beneath the three enforcement cards.
2. Edge displays a comprehensive list of every tracking organization and analytics domain blocked during your browsing history (e.g., DoubleVerify, Google Tag Manager, Criteo, or Scorecard Research).
3. The list displays the number of times each tracker was intercepted and indicates when it was last blocked.
4. To reset this operational log, click Clear tracking data at the top-right corner of the list.

---

Step 4: Configuring Site-Specific Exceptions

When operating under Strict tracking prevention, certain complex web applications—such as university portals, embedded third-party payment gateways, or multi-domain corporate dashboards—may fail to authenticate or load interactive components. Rather than lowering your browser-wide privacy level, configure targeted site exceptions:

1. Navigate back to Settings > Privacy, search, and services > Tracking prevention.
2. Click Exceptions.
3. Click the Add a site button in the upper-right corner.
4. Enter the domain name of the trusted site (e.g., [*.]example.com or https://app.workplace.com).
5. Click Add.

Edge will disable aggressive tracker blocking exclusively on the specified domain, allowing necessary cross-origin cookies and scripts to execute while maintaining strict protection across the remainder of the web.

---

Step 5: Managing Tracking Prevention via the Address Bar

You can quickly adjust tracking prevention settings on a per-page basis without leaving your active tab:

1. Visit the website you wish to inspect or adjust.
2. Click the View site information (padlock/tune) icon located on the far left side of the address bar.
3. In the flyout security panel, locate Tracking prevention:
   • Edge indicates whether tracking prevention is active and displays the count of blocked trackers on the current page.
   • To allow full tracking on this site temporarily (for example, if a checkout form is stuck), toggle the Tracking prevention switch to Off.
4. Click Trackers to inspect the specific domain names and script sources blocked on that specific page.

---

Edge Tracking Prevention vs Ad Blockers

It is important to understand how Edge’s native Tracking Prevention interacts with third-party content blockers:

• Tracking Prevention: Targets privacy-invasive data collectors, device fingerprinting, and tracking cookies across domains. It does not deliberately attempt to remove display ad units unless those units rely entirely on blocked tracking scripts.
• Ad Blockers (e.g., uBlock Origin): Target cosmetic elements, ad banners, pre-roll video ads, and sponsored links based on visual cosmetic rules and network filters.

Using Microsoft Edge’s Balanced or Strict tracking prevention in combination with a trusted lightweight content blocker provides layered defence against profiling and intrusive advertising.

---

Troubleshooting Common Tracking Prevention Issues

Issue	Underlying Cause	Recommended Fix
“Third-party cookie required” login loop	Strict tier blocking authentication token	Click the address bar padlock icon and add an exception for the login domain, or switch from Strict to Balanced.
Embedded social media videos do not display	Cross-site social trackers blocked	Check Exceptions and add the hosting site, or interact with the native player prompt to unblock the frame.
Tracking prevention toggle is greyed out	Managed by corporate Group Policy / Intune	If using an enterprise or school-managed laptop, tracking policies are enforced centrally by IT administrators via MDM.