Safari tracking: Apple now blocks identity resolution. What changes for advertisers

Safari tracking just got another restriction. On October 19, 2026, Apple announced that Safari now blocks services that collect a visitor’s email to recognize them on other sites and devices. This time the target is not the cookie. It is the email typed into a login or newsletter form. Here is what

Wascer-TeamServer-side tracking4 Min. Lesezeit
Rastreamento no Safari: formulário de e-mail no iPhone com a chamada para um serviço de terceiro bloqueada
Safari tracking: email form on an iPhone with the request to a third-party service blocked

Safari tracking just got another restriction. On October 19, 2026, Apple announced that Safari now blocks services that collect a visitor’s email to recognize them on other sites and devices.

This time the target is not the cookie. It is the email typed into a login or newsletter form. Here is what changes and what to do.

What Apple announced

  • Where it applies: in the version 27 releases of iOS, iPadOS, macOS and visionOS.
  • What is blocked: the browser’s connection to “identity resolution” services.
  • How: by the service’s domain. Changing the format of the request does not get around it.
  • What is left out: personalization done by the website itself.

Apple has not disclosed which domains are on the list. For Wascer, this is the central point: today no one can say for sure which tools have stopped working.

What identity resolution is

It is when a third-party service, hidden on the page, takes the email the visitor typed, sends it to its own servers and creates an identifier tied to it. With that identifier, the same person is recognized on other sites and other devices.

iOS 27 cuts that path: the email does not leave the browser for the service’s domain.

Safari tracking: how identity resolution worked and where iOS 27 cuts the path

What is affected in Safari tracking

Situation

Facing the block

Third-party script that reads the email from the form and sends it to its own domain

At risk: it is exactly what Apple describes

Browser tag that sends customer data to the platforms

Uncertain: it depends on the domain list, which is not public

Company server sending the conversion to the platform’s API

Out of reach: it does not pass through the visitor’s browser

The symptom is not an error on screen. It is a smaller number in the report, concentrated among iPhone, iPad and Mac users. And when platforms receive less data, campaigns learn less.

What to do now

Wascer recommends three steps:

  1. Measure how much of your audience uses Safari. In GA4, check the Tech details report by browser and by operating system. That number shows the size of the risk.
  2. Track conversions by browser. A drop only in Safari disappears in the overall average.
  3. Move sending to the server. With server-side, the conversion and customer data leave the company’s server straight to Meta, Google Ads and GA4, without depending on a script in the browser.

Want to know how your site sends data today? Enter your site URL and see how your tracking is set up.

One caution: personal data is still personal data. Sending email and phone, even hashed, requires a legal basis and transparency with the visitor, as data protection laws such as Brazil’s LGPD require.

How to test Safari tracking

Checklist to test Safari tracking on iOS 27

  1. Open the site in Safari on a device running version 27, outside private browsing.
  2. Turn on Web Inspector and keep the Network tab open.
  3. Log in, sign up for the newsletter and place a test order. Check whether any request to another domain fails.
  4. Confirm that server events arrive in Meta (Test events) and in GA4 (DebugView).

How Wascer helps

Wascer launches and monitors a server-side Google Tag Manager container in one click, with no DevOps and no command line. The conversion leaves the server for each platform’s API, which is the path a browser block does not reach. Learn what Wascer is and how it works.

Frequently asked questions

Were the Meta pixel and the Google tag blocked?

The announcement does not name any platform, and the domain list is not public. So the safest choice is not to depend only on the browser.

Is server-side tracking affected?

The block happens in the browser. A send from the company's server to the platform's API does not pass through it.

Does Apple forbid sending hashed email from the server?

The announcement does not address server-to-server sending, and that is not an endorsement from Apple. Sending follows each platform's rules and data protection laws such as the LGPD.

Conclusion

Safari tracking lost one more door. First it was third-party cookies; now it is the email collected in the browser. The answer is the same: measure how much Safari weighs in your audience and take conversion sending out of the browser.

Want to know whether your site depends on the browser to measure sales? Enter your site URL and see how your tracking is set up.

Wascer: rastreamento server-side

By Ronny Rangel

Wascer launches and monitors your server-side Google Tag Manager container in one click: no DevOps, no Docker and no command line. Technical content on tracking, Meta, GA4 and Google Ads for teams that decide with data. wascer.com

Sources

Wascer-Team · Veröffentlicht am 23.10.2026 · aktualisiert am 06.11.2026

Weiterlesen

Alle Artikel
11 NOVGoogle Data Manager API: O Futuro do Envio de Dados para o Google Ads30 OKTMeta Ads and GA4 don’t match: when the gap is normal and when it’s lost data26 OKTWrong Google Ads conversion value: why it happens and how to fix it