Full Answer

Edge's Tracking Prevention is enabled out of the box and set to Balanced, which is more aggressive than many marketers assume. It draws on categorised tracker lists and blocks trackers from sites the user hasn't visited, along with trackers flagged as malicious or fingerprinting. Switching to Strict blocks most third-party trackers and is the level most likely to interfere with conventional pixels and tag managers.

Because Edge is built on Chromium, two things are true at once. It inherits Chrome's underlying cookie handling, so changes Google makes to the engine affect Edge too. But Tracking Prevention is Microsoft's own addition, operating independently of Chrome's settings, which means a visit from Edge can behave differently from the same visit in Chrome.

For a WooCommerce store the practical point is that Edge is not a safe haven for client-side tracking. Its default settings already interfere with third-party scripts, and you have no control over which level a visitor chooses. Edge is one more browser in a landscape where Safari, Firefox, and Brave together remove a fifth to a quarter of conventional tracking signal. The durable answer is the same across all of them: collect events server-side from your own origin, where browser tracking-prevention rules don't decide whether your conversion is recorded.