Microsoft Edge is moving toward blocking unpartitioned third-party cookies by default, but it has not published a universal shutdown date. Its proposed replacement is the browser-mediated Ad Selection API, which is intended to keep ads relevant without unrestricted cross-site identifiers. Microsoft has tested the approach with a small user experiment and a limited developer preview; websites should begin auditing cookie dependencies and strengthening first-party measurement now.
What Microsoft is changing
Microsoft’s stated direction is a staged transition away from third-party cookies rather than an immediate, one-day cutoff. In its March 5, 2024 announcement, the Microsoft Edge Team said Edge would begin experimenting with third-party-cookie deprecation, targeting less than 1% of users on non-managed devices and continuing the experiments during 2024. Managed commercial devices were excluded from that test.
The same announcement says Edge will “generally block third-party cookies by default” in the future. That wording describes the intended end state, not a confirmed completion date. The announcements and previews available for this article do not establish when a universal default block will be finished.
Partitioned storage remains a separate option
Microsoft says explicitly partitioned cookies will remain available. Other browser storage is intended to be partitioned automatically, meaning data stored by an embedded service is separated by the top-level website and is not shared across unrelated sites. This is different from an unpartitioned third-party cookie that can recognize a browser across many domains.
#1 Best Overall
What the Ad Selection API is
The Ad Selection API is Microsoft’s central proposal for privacy-preserving advertising in Edge. Microsoft describes it as a browser platform feature that lets advertisers and publishers show relevant ads without third-party cookies or other cross-site tracking identifiers.
Instead of giving an advertising service a general-purpose identifier that works across the web, the browser mediates the selection process. Sellers and buyers use JavaScript on participating sites, and Edge applies the rules for which information can be used and what result can be exposed. The Microsoft Learn documentation states that the API provides user-relevant ads without using third-party cookies.
Safeguards Microsoft says it will use
| Safeguard | Intended purpose |
|---|---|
| K-anonymity constraints | Prevent an audience, ad request, or result from being so unique that it could identify a small group or individual. |
| Differential privacy | Add statistical noise or protection to released information so individual activity is harder to infer from aggregate results. |
| Trusted execution environments (TEEs) | Allow more complex auction computation to run in a protected environment while limiting direct observation of the underlying data. |
These are Microsoft’s design claims in its launch material. The cited announcements and documentation do not constitute an independent privacy or performance audit, so advertisers should treat the protections as the proposed architecture rather than a proven outcome.
How far the Edge preview went
Microsoft’s October 8, 2024 announcement described a limited, developer opt-in preview of the Ad Selection API. It ran in Edge Canary and Dev channels for versions 130.0.2808.0 and later. The preview was unavailable in the European Economic Area and the United Kingdom, operated through a limited Origin Trial, and required durable developer attestation for participating domains.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors| Preview detail | What Microsoft documented |
|---|---|
| Channels | Edge Canary and Dev |
| Minimum version | 130.0.2808.0 |
| Participation | Developer opt-in through a limited Origin Trial |
| Domain requirement | Durable developer attestation |
| Geographic exclusions | European Economic Area and United Kingdom |
| Cookie experiment labels | control_1.1: third-party cookies enabled by default; treatment_1.1: third-party cookies disabled by default |
A preview assignment or an Origin Trial is not evidence that the same behavior is enabled for every Edge user. Availability, experiment enrollment, supported versions, and geographic scope can change as Microsoft adjusts the implementation.
What advertisers and publishers need to change
1. Find every third-party-cookie dependency
Inventory code and vendors that assume a cookie set in one site can be read in another. Pay particular attention to:
- Embedded video, payment, chat, identity, and other iframe-based services
- Cross-site login and account linking
- Conversion measurement and attribution
- Frequency capping
- Retargeting and audience membership
- Fraud controls and analytics that depend on a shared cross-site identifier
For each dependency, record the owning vendor, the user journey it supports, whether the cookie is partitionable, and what happens when the browser blocks it. Test both ordinary navigation and embedded-content flows; a site can appear healthy until a user reaches an iframe, checkout, or sign-in prompt.
2. Test partitioned storage
Run production-like tests in Edge channels that expose the privacy changes. Confirm whether each embedded component can work with storage partitioned by the top-level site. If a service genuinely needs access across sites, document that requirement rather than silently assuming an unpartitioned cookie will continue to work.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #2
- Please update the firmware upon initial setup of the router, as it greatly enhances the device's performance and ensures a superior user experience.*** 【WiFi 6 Standard with ultra-low latency】Wi-Fi 6 speeds up to 6 Gbps to let you enjoy smoother 4K streaming, gaming, video calls and more, DDR4 1GB / eMMC 8GB
- 【High Speed Gaming Router】Dominate with uninterrupted performance with the ultimate MT6000 gaming internet router, equipped with 8-stream Wi-Fi 6 technology, the Flint 2 delivers blazing speeds, ensuring a stable and high-speed connection during intense multiplayer battles.
- 【Rapid OpenVPN & Wireguard speed】Wireguard VPN and OpenVPN speeds up to 900Mbps and 880Mbps respectively, giving you complete control over your gaming, streaming and working bandwidth. Actual speed may differ depending on internet service provider, network environment, VPN server location, VPN service provider, etc.
- 【AdGuard Home Supported】Enabling the use of a DNS server for blocking unwanted tracking and offers a convenient web interface for filtering selected digital advertisements. Users can take full control of their online experience and enjoy a clutter-free browsing environment with ease.
- 【Mass device connectivity】Experience enhanced online connectivity with our higher storage capacity, catering to over a hundred devices and fulfilling the requirements of DIY users seeking to install additional plugins. Enjoy stable and reliable connections, ensuring seamless performance and accommodating a wide range of digital needs.
3. Plan the Ad Selection API integration
Organizations that participate in the preview or a later rollout will need JavaScript changes for the API’s seller and buyer roles. Treat this as a platform migration: define the data each role needs, verify that the browser’s privacy constraints still support the intended auction, and maintain a fallback for browsers or regions where the API is unavailable.
4. Build stronger first-party measurement
Microsoft Advertising’s June 25, 2024 identity guidance recommends a broader identity strategy rather than dependence on one mechanism. It specifically recommends implementing the Universal Event Tracker (UET), or the Universal Pixel on Microsoft Invest, so conversion tracking and retargeting can continue as third-party cookies are removed. These tags do not make third-party cookies permanent; they provide a first-party measurement path that still needs privacy, consent, and data-quality review.
5. Treat authentication as its own migration
Advertising and authentication are different technical problems. Microsoft’s Interop 2025 material identifies the Storage Access API as a focus area for preserving legitimate sign-in and embedded-account flows while browsers reduce third-party-cookie access. Test login renewal, embedded account widgets, payment authorization, and logout behavior separately from ad measurement.
What changes for users and the advertising ecosystem
Third-party cookies historically supported cross-site measurement, retargeting, frequency capping, and advertising-funded content. Under Microsoft’s proposed model, advertising does not disappear; more of the decision-making moves into browser APIs, first-party signals, contextual information, and privacy-constrained auctions.
| Area | Legacy unpartitioned-cookie model | Microsoft’s proposed direction |
|---|---|---|
| Privacy exposure | A shared identifier can be read across many sites. | The browser limits cross-site access and applies constraints to ad selection and reporting. |
| Implementation | Existing integrations often read or set third-party cookies directly. | Sites may need JavaScript changes for the Ad Selection API, partitioned storage testing, and first-party tags. |
| Targeting and measurement | Retargeting, cross-site attribution, and frequency capping can use a common identifier. | Advertisers combine first-party measurement, contextual signals, and browser-mediated APIs such as the proposed Ad Selection API. |
| Authentication and embeds | Many embedded flows assume third-party-cookie access. | Some flows may require partitioned storage, explicit user access, or Storage Access API support. |
| Rollout certainty | Current integrations have known browser behavior. | Microsoft has announced experiments and previews, but not a documented universal completion date. |
Will Edge block third-party cookies?
Microsoft says that Edge will generally block third-party cookies by default in the future, while preserving explicitly partitioned cookies and partitioning other storage. The evidence currently available establishes a direction and limited tests, not a date on which every Edge installation will behave that way.
That distinction matters operationally. A site should not wait for a final calendar announcement: users may encounter different behavior based on Edge channel, version, experiment assignment, device management, region, and whether a storage access request is involved. Conversely, a site should not assume that a limited preview proves the final production design.
A practical migration plan
- Map data flows. List every cookie, local-storage entry, iframe, tag, and vendor that crosses a site boundary.
- Classify the purpose. Separate advertising, analytics, fraud prevention, personalization, login, payments, and embedded-content requirements.
- Test failure modes. Use Edge test channels and both cookie experiment behaviors where available. Check sign-in, checkout, consent, attribution, retargeting, frequency caps, and logout.
- Adopt first-party measurement. Implement and validate UET or the Universal Pixel on Microsoft Invest where appropriate, and reconcile its conversions with your existing reporting.
- Evaluate partitioning. Determine whether each embedded service can operate with storage scoped to the top-level site. For cross-site authentication, investigate Storage Access API behavior and user prompts.
- Prototype API participation. If you are an ad seller or buyer, model the JavaScript and data requirements of the Ad Selection API and define a fallback for unsupported browsers.
- Monitor rollout notices. Recheck Microsoft’s current Edge documentation before changing production defaults, because preview availability, geography, versions, and experiment assignments are not permanent guarantees.
What remains uncertain
- Completion date: Microsoft has not established a universal date for full default blocking in the cited announcements.
- Performance: The available material does not independently show how Ad Selection API results compare with cookie-based targeting or measurement.
- Privacy effectiveness: K-anonymity, differential privacy, and TEEs are stated safeguards, but the cited sources do not provide an independent audit of their real-world protection.
- Interoperability: Sites may still need different implementations for browsers that do not support the same APIs or partitioning rules.
- Compatibility: Authentication, embedded content, and other cross-site functions can fail differently from advertising, so they require dedicated testing.
Bottom line
Microsoft’s plan is to replace unrestricted third-party-cookie tracking in Edge with browser-mediated advertising and stronger first-party measurement. The Ad Selection API is the centerpiece, supported in Microsoft’s design by K-anonymity constraints, differential privacy, and trusted execution environments. Because Edge has so far demonstrated experiments and a limited preview rather than a universal shutdown, the right response is staged preparation: audit dependencies, test partitioned storage, protect authentication flows, and build measurement that does not require a shared cross-site identifier.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Recommended Free Tools
