Apple Confirms Safari Block Targets Email-Based Ad IDs

Apple has officially confirmed what its September Safari crackdown was about: blocking identity resolution, the practice of turning email addresses typed into websites into cross-site advertising IDs. In a WebKit engineering blog post published Monday, October 19, Apple's browser team explained for the first time why it cut off some of the ad industry's biggest identity providers.

The mechanics matter here. When someone enters their email to log in or sign up for a newsletter, a company working with that site can capture the address and convert it into a durable identifier (an ID that advertisers use to recognize the same person across sites, without cookies). Apple wants that pipeline shut down, and the post leaves little ambiguity about who was in its sights.

Who did Safari actually cut off?

The blog post confirms what practitioners had already pieced together. LiveRamp, ID5 and The Trade Desk's UID 2.0 all operate on the email-to-ID model Apple describes. All three were among the first companies Safari blocked when Apple shipped its latest software update in September, alongside Permutive and Audigent.

The block's scope is wider than many assumed. It doesn't stop at iPhones and iPads — Apple confirmed it extends to Macs and the Vision Pro headset. Once a user updates their software, Safari stops communicating with those companies entirely, and the tracking stops with it.

What does this change for advertisers and publishers?

For ad tech buyers, the practical question is whether email-based identity — the fallback the industry built after cookie deprecation stalled — still works at scale on Safari. As of September, it doesn't, and Apple has now put that in writing.

That has budget implications. Safari carries a substantial share of mobile and premium web traffic, particularly in markets where iPhone usage is high. Campaigns that lean on LiveRamp's RampID, ID5 or UID 2.0 for frequency control (limiting how often one person sees the same ad) and audience matching will see that functionality degrade for Safari users on updated devices.

Publishers face the sharper edge. Those selling authenticated audiences — newsletter registrations, logins — through these identity partners lose a chunk of their addressable Safari inventory. Data collaboration platforms like Permutive and Audigent, which sit between publishers and advertisers, took the same hit in the first wave of blocks.

Official word versus industry speculation

Apple's post is the official record: it describes the email-based ID mechanism and states the intent to block it, and it confirms device coverage across iPhone, iPad, Mac and Vision Pro. What Apple has not done is publish a full blocklist or spell out enforcement criteria going forward — so any claim about which company gets blocked next remains speculation, not policy.

Worth watching, too, is the tension practitioners keep flagging: Apple restricts third-party tracking while growing its own ads business, which puts its Safari blocklist under scrutiny. That competitive question hangs over every future expansion of this policy.

Whether Apple widens the block to more identity providers — or other browsers follow suit — will shape how much of the post-cookie ad stack survives intact.