Marketing analytics

Safari Tracking Prevention Now Blocks Identity Resolution

Safari tracking prevention in the 27 releases blocks identity-resolution services that turn emails into cross-site IDs. What it means for marketers.

By Jasper Koers Published 7 min read

On this page
  1. What WebKit announced on 19 October 2026
  2. How identity resolution works, according to WebKit
  3. How this fits Safari's existing tracking prevention
  4. Safari tracking prevention: what is affected and what still works
  5. What this means for attribution and retargeting
  6. Where ClearAnalytics fits

On 19 October 2026, the WebKit team published Blocking identity resolution infrastructure. In the iOS, iPadOS, macOS and visionOS 27 releases, Safari tracking prevention now blocks network access to identity-resolution services. These are the third parties that take the email address you type into a login or newsletter form and turn it into a tracking ID that can follow you across sites. WebKit calls them "post-cookie" tracking, and it blocks them at the domain level.

This matters because email-based IDs were the ad industry's main answer to the end of third-party cookies. If your attribution, retargeting or audience matching depends on such an ID being created in the browser, Safari users on the 27 releases will drop out of it. This article covers what WebKit actually announced, what it did not say, and which kinds of measurement are unaffected.

What WebKit announced on 19 October 2026

The post, by John Wilander, Charlie Wolfe and Matthew Finkel, makes a few concrete points:

  • What is blocked: Safari and WebKit block network access to identity-resolution infrastructure, which stops email addresses from being sent to those servers.
  • Where: in the iOS, iPadOS, macOS and visionOS 27 releases.
  • How: at the domain level. According to WebKit, the services cannot get around it by changing the structure of the network request.
  • What is not targeted: WebKit states plainly that "first party personalization is not tracking". A site that remembers your preferences or shows you your own order history is not what this is about.
  • What is not published: the post does not include a list of blocked domains, and it does not describe a testing tool or an appeal process.

The post also mentions Hide My Email, the iCloud+ feature that gives each site a unique, random address that forwards to your real inbox. That limits email-based tracking from the other side: even if a service receives the address, it is not the same address on every site.

How identity resolution works, according to WebKit

WebKit describes the mechanism like this. When a visitor logs in or signs up for a newsletter, a third-party script collects the email address and sends it to the identity-resolution service. The service returns an opaque ID linked to that address, and the ID is stored on the website. From then on the ID can be used to profile browsing or target ads across every site that uses the same service.

Two details in the post stand out. First, logging out or unsubscribing does not remove the ID or the stored email. Second, these services grow an identity graph over time from more logins and form entries. WebKit points out that email addresses and phone numbers are personally identifiable and work across sites and across devices, which makes them a stronger tracking key than a cookie ever was. It also argues that even a graph run for a single company by a third-party resolver acts as a "tracking clearinghouse".

What about hashed emails?

The industry usually sells these solutions as "hashed email" or "universal ID" solutions, on the reasoning that a SHA-256 hash of an address is not the address itself. WebKit's post does not discuss hashing. But because the blocking happens at the network level, per domain, it does not matter what the payload looks like: if the request to the identity-resolution domain never leaves the browser, neither a plain nor a hashed email reaches it. A hash of the same email is also the same on every site, which is exactly what makes it useful as a cross-site key.

How this fits Safari's existing tracking prevention

Identity-resolution blocking is the latest layer on top of protections WebKit has shipped for years. The post itself notes that WebKit fully blocked cross-site cookies six years ago and is "actively fighting device fingerprinting". WebKit's tracking prevention documentation describes the rest of Intelligent Tracking Prevention (ITP):

  • All third-party cookies are blocked by default, with access only through the Storage Access API.
  • Script-writeable storage (cookies set by JavaScript, LocalStorage, IndexedDB and similar) is deleted after 7 days without user interaction with the site.
  • Third-party CNAME cloaking (a tracker hidden behind your own subdomain) gets its cookie lifetime capped at 7 days.
  • Link decoration: when ITP detects click IDs added to a URL, JavaScript-set cookies on the landing page expire after 24 hours.

On top of that, Safari's Private Browsing blocks known tracking query parameters in links, introduced in Safari 17. WebKit's Private Browsing 2.0 post explains that Safari removes a subset of parameters used for cross-site tracking before navigation, while parameters used for campaign attribution are allowed through. The same protections can be switched on for all browsing through Safari's advanced tracking and fingerprinting protection setting.

The pattern is consistent: each time the industry finds a new way to carry a persistent identifier across sites, Safari closes it. Identity resolution is simply the next one.

Safari tracking prevention: what is affected and what still works

The table below maps common techniques to the Safari 27 change. "Affected" means the identity-resolution blocking itself; techniques already limited by ITP are marked as such.

Technique Affected by Safari 27? Alternative that still works
Third-party script turns login or newsletter email into a cross-site ID Yes, requests to identity-resolution domains are blocked First-party login and CRM data that stays with you
Identity graph linking a visitor across sites and devices Yes, it can no longer be fed from Safari Measure per site; accept that cross-site journeys are not visible
Retargeting audiences built from email-based IDs collected in the browser Yes, Safari visitors stop being matched Contextual targeting; consented, first-party customer lists
Third-party cookies Already blocked by ITP No cross-site alternative intended
Long-lived JavaScript cookies or localStorage IDs Already capped at 7 days without interaction Identifier-free, aggregated measurement
Click IDs in landing-page URLs Cookie lifetime capped at 24 hours; known tracking parameters stripped in Private Browsing Campaign parameters such as UTM tags (how to use them)
First-party personalisation (preferences, account pages) No, WebKit says it is not tracking Keep it first-party
Aggregated first-party analytics without persistent IDs No, nothing to resolve Keep reporting totals, sources and conversions

Note that the table only covers what WebKit has described. Since no domain list is published, you cannot know in advance whether a specific vendor is on it. The practical test is to open your own login and newsletter flows in Safari on a 27 release with the developer tools open and check which requests fail.

What this means for attribution and retargeting

For most marketing teams the impact will show up in three places:

  1. Match rates drop for Safari users. Any audience or conversion match that relies on an email-based ID created in the browser will lose the Safari share of your traffic. On sites with many iPhone visitors, that share is large.
  2. Cross-site and cross-device attribution gets thinner. If your reports join a mobile Safari session to a desktop purchase through an identity graph, that join will no longer happen for those visitors. Expect more conversions to look like single-touch or direct.
  3. Discrepancies between tools grow. Ad platforms, your analytics and your CRM will disagree more, because each sees a different slice. We covered why that happens and how to read it in why your analytics data is probably wrong.

What does not change: the number of people who visit, which channels and campaigns sent them, which pages they viewed and whether they converted on your site. None of that needs a persistent cross-site identifier. It needs first-party measurement and campaign parameters that browsers leave alone.

Moving tracking to the server is sometimes pitched as the fix. It can make data collection more robust, but it does not make cross-site identification acceptable, and browser vendors have shown they target the purpose, not the transport. Our comparison of server-side and client-side analytics goes into those trade-offs. If you want visitors to be able to express a preference instead of having to rely on browser defaults, browser-level privacy signals are another direction, covered in our post on Global Privacy Control and the cookie banner.

Where ClearAnalytics fits

ClearAnalytics was built for the kind of measurement WebKit leaves alone. It sets no cookies, stores nothing on the visitor's device and does not try to recognise anyone across sites. Unique visitors are counted with a daily-rotating hash, the IP address is not stored, and data stays in the EU without being shared for advertising. If you want to see what that looks like next to your current setup, the features page is a good place to start.

Frequently asked questions

What is identity resolution in advertising?

Identity resolution links a person's activity across websites and devices to one profile, usually by turning an email address or phone number into a persistent ID. WebKit calls it a post-cookie tracking method that builds an identity graph over time.

Does Safari block hashed email tracking?

Safari 27 blocks network requests to identity-resolution services at the domain level, so the email never reaches those servers whatever form it is sent in. WebKit has not published the list of blocked domains.

Which Safari versions block identity resolution?

WebKit says the blocking ships in the iOS, iPadOS, macOS and visionOS 27 releases of Safari and WebKit.

Does Safari tracking prevention break first-party analytics?

WebKit says first-party personalisation is not tracking and is not targeted. Analytics that runs on your own site, uses no cross-site identifier and reports aggregated statistics is outside what this change is aimed at.

  • safari
  • tracking-prevention
  • identity-resolution
  • attribution
  • privacy

Back to blog Read as markdown

Enjoyed this article?

Try ClearAnalytics for free and get privacy-first analytics for your website.