Skip to main content

Safari Is Blocking Tracking Domains in Safari 27. Ad Tech Is Moving the Auction Off Your Browser.

On October 19, WebKit published "Blocking Identity Resolution Infrastructure" by John Wilander, Charlie Wolfe, and Matthew Finkel. It said that Safari (and more broadly, WebKit) on iOS, iPadOS, macOS, and visionOS 27 will block network access to identity resolution infrastructure to prevent cross-site tracking.

Apple has identified a major issue in the way the ad-tech market serves ads and leeches off of user data. Every time you type your email into a login box or a newsletter form, a third party, not the site owner, collects that email. It sends the email to its own servers, creates an ID tied to that email, and returns the ID to the site. Over time, that third party builds an identity graph from the dozens of sites providing them with this data. The ID is permanent and follows you across sites, devices, or anywhere you submit your email.

Safari will start blocking these third-parties at the domain level, WebKit says, so vendors cannot get around it by changing the structure of their requests.

WebKit names no companies in the post, and publishes no list. The names come from a public bug report filed on September 21 by Ian Meyers. That report identified nine blocked domains bundled into Safari 27, including uidapi.com, the domain behind Unified ID 2.0, id5-sync.com for ID5, rlcdn.com, and pippio.com for LiveRamp, permutive.com, and ad.gt for Audigent. It also included adsrvr.org, The Trade Desk's core ad request and delivery domain, which Meyers described as not identity. Apple restored adsrvr.org in the iOS 27.2 beta, and marked the issue resolved on October 9. The identity vendors stayed blocked.

Consolidating Infrastructure

Around the same time, the Federal Trade Commission blessed the biggest consolidation of ad-tech agencies in years.

On October 19, the FTC voted 2 to 0 to issue a complaint and accept a proposed consent agreement for Publicis Groupe to acquire LiveRamp. The deal is all cash, about 2.2 billion dollars. The FTC is allowing this as long as the consolidated company promises to stay neutral for five years.

Apple, a company that does NOT make its money from selling user data (wholly) is trying to mitigate identity resolution at the browser level, all while the FTC is letting these identity resolution providers consolidate.

Ad-tech's response

On October 13, Rowena Lam, Senior Director of Privacy and Data at IAB Tech Lab, published a post called "Apple's WebKit Updates Mean Advertising's Future is Server-Side." Lam is stating that, to survive, advertising infrastructure will need to move into network infrastructure. Moving the ad stack server-side means shifting the heavy lifting like bidding, identity, and others, out of the user's browser and into a secure, publisher-controlled runtime environment.

"Going server-side is more resilient because you're not on the device anymore, so there's nothing the device can do to block you."

-Mathieu Roche, ID5 CEO

IAB Tech Lab introduced the solution, Trusted Server, in March 2025. It is open source and described by its developers as a hyper-intelligent reverse proxy for publishers. It runs server-side ad requests, prebid server integration, edge processing, and server-side ad stitching. In plain terms, it runs the auction on the publisher's server, not in your browser.

IAB Tech Lab's 2026 roadmap says the same thing, in the same terms. Browser signal loss is not going away, so it is doubling down on Trusted Server. By shifting the ad stack to the publisher's server-side environment, Trusted Server empowers publishers and their partners to improve audience signaling, ad delivery, and inventory recovery.

CEO Anthony Katsur spent the ten days after Safari's block became public telling the industry to move. In three posts on X, dated September 30, October 8 and October 9, he pointed to Trusted Server, and on October 8 declared it "production ready TODAY." On October 10, the project's public GitHub repository showed 343 commits, 130 branches, an Apache 2.0 licence, and no published releases.

Digiday reported that ID5, one of the identity companies Safari blocked, is preparing to migrate more of its identity infrastructure server-side. Its CEO, Mathieu Roche, confirmed the development, "Going server-side is more resilient because you're not on the device anymore, so there's nothing the device can do to block you."

What the browser loses

A browser controls tracking in two ways, it blocks, and sees.

Safari is using the blocking method when it refuses to connect to a resolver domain, so the email never leaves. The other half of control over tracking is being able to see what a page sends, to whome, and when.

Trusted Server removes both.

Blocking - If the ad call never leaves the browser as a third party request, because it goes first party to the publisher's server, and then the bidder, Safari never sees a domain to block. The request happens between servers you do not control and on a network you cannot inspect.

Seeing - If the auction runs on the publisher's server, the browser cannot log it. This is the loss of the only enforcement and visibility point users have.

IAB Tech Lab says moving server-side is more privacy protective. That is the claim in Lam's post, and it is the claim in the roadmap. The argument is that a publisher-controlled server can limit what leaks, enforce rules, and keep data inside a first-party boundary.

"First-party"

A publisher-controlled server is only first-party in name.

This infrastructure is just a fancy way of making transparent calls to third-party domains, invisible, as these calls will now operate through publisher-controlled infrastructure. Publisher-controlled here just means the third party moved from your browser to the publisher's server and kept doing the same job.

We just watched that exact failure in the Penlink piece. Developers embedded an SDK they did not write, to show ads and make money, and then said they did not know their users' data could end up with the government. A publisher embedding a Trusted Server plugin, to run an auction and restore addressability, is in the same position. They know the plugin has access; they do not know, in full, where the data goes after the first server-to-server hop.

Moving forward

Trusted Server version 1.0 is out. The GitHub repository has no published releases as of October 10. Watch whether ID5, and others, actually move identity server-side, and whether that move is visible in any public measurement, or only in their own announcements.

WebKit's tracking prevention policy says it treats getting around its protections as seriously as exploiting a security hole, and it may add restrictions aimed at specific parties without notice, meaning Apple has reserved the right to block Trusted Server.

What I do know is that when identification services move out of the browser and are obfuscated by vendors, users lose the ability to measure it and meaningfully opt-out... You can't block what you can't see.