Skip to content
Sunday 25 October 2026 marketing · daily

Martech · AdTech

Apple explains Safari block as identity vendors get cut

Apple details why Safari now blocks email-based ad IDs, which vendors were caught first, and what marketers should audit before the block widens.

Apple explains Safari's block on email-based ad IDs
In this story
  1. What Apple actually said
  2. Where Apple draws the line
  3. The track record behind the block
  4. What marketers should do now

What Apple actually said

Apple has laid out the thinking behind its September Safari update, and the target is unmistakable: email-derived ad IDs. In an engineering blog post published on Monday, the company said third parties that sit on login and newsletter forms can turn an email address into a stable identifier, letting advertisers recognize the same person across sites without cookies. LiveRamp, ID5 and The Trade Desk’s UID 2.0 were among the first firms cut off, alongside Permutive and Audigent. The block applies not just to iPhones and iPads but also to Macs and the Vision Pro headset.

Apple’s argument is that email has simply replaced the cookie as the tracking anchor. People keep one address for years and use it on every device, so an ID built from that address is harder to escape than a cookie ever was. Apple also noted that logging out or unsubscribing does not remove the tracking code the third party already holds, allowing that vendor to keep adding details into what the industry calls an identity graph.

Where Apple draws the line

Apple says personalizing for your own customers is not the problem. A publisher using what it knows about its own readers to recommend articles or tailor a page is not the target. The line is crossed when outside firms are paid to match data across sites, even when the data starts with one company’s own customers.

That distinction still leaves publishers with hard questions. Apple did not name the vendors on its list, explain how companies get added or say how they can get off it. Digiday’s own testing found most ad tech web addresses were still loading, so the current block is narrow. But Apple was blunt: “We’ll continue to prevent covert and cross-site tracking by default.”

The track record behind the block

Some ad executives will read this through Apple’s history. In 2017, Safari’s Intelligent Tracking Prevention hit cookie-dependent ad tech; Criteo warned of up to a 10% fourth-quarter revenue impact. In 2021, App Tracking Transparency led Meta to estimate a $10 billion cost for 2022, while Apple’s share of the iPhone app install ad market rose from 17% to 58%, according to Branch data reported by the Financial Times.

This time the block arrives as Apple’s ads business pushes into Maps and lists 86 open Apple Ads roles. That includes engineering and client-facing jobs in Cupertino and New York, and a “Signals Intelligence” team that tunes language models to label ads and search queries.

What marketers should do now

  • Map every vendor that touches email addresses from login, newsletter and gated-content forms.
  • Measure Safari reach and match rates before and after the September update.
  • Strengthen first-party personalization, which Apple explicitly says it is not blocking.
  • Treat third-party cross-site matching vendors as a potential single point of failure.

One ad tech executive at a publisher said the real question is not Apple’s right to protect privacy, but who controls the technical rules for what counts as privacy-preserving advertising. For marketers, the practical answer is to reduce dependence on any identifier Apple can switch off.

Source: Digiday

Written by

Marketing Junkies Desk

Marketing Junkies covers agency moves, campaigns, martech and adtech launches with an Indian and global lens. Every story is written from a named source and links back to it.