Apple is stepping up pressure on advertising and marketing technologies that follow people across websites. In a post titled Blocking Identity Resolution Infrastructure, WebKit engineers John Wilander, Charlie Wolfe and Matthew Finkel explain why blocking third-party cookies no longer provides sufficient protection. As browsers restricted one tracking tool, the industry developed other ways to recognize users. Apple is now targeting the infrastructure that makes those alternatives possible.
Why Apple is expanding its restrictions
The WebKit team argues that people should decide whether to allow tracking across websites or covert identification through device fingerprinting. Without an explicit opt-in, the engineers believe these practices should be prevented. Their explanation is among Apple’s clearest public statements of its intention to curb third-party web tracking on its devices.
Apple regards Safari’s full blocking of third-party cookies in 2020 as a significant privacy advance. Advertising platforms, marketing services and data vendors nevertheless continued developing ways to match audiences. Approaches described as post-cookie tracking and identity resolution gained ground. From Apple’s perspective, a change in technology does not remove the underlying privacy concern.
How an email address becomes a tracking tool
Someone using an iPhone might provide an email address to receive a newsletter or access a subscription. They would normally expect that particular service to use it for communication or account management. Instead, the information can also enter outside identity systems and become part of graphs that connect details about the same person from multiple sources.
The address can then support profiling, ad targeting and continued tracking. Signing out or cancelling a newsletter does not mean the information automatically disappears from intermediaries’ systems. That gap between a user’s expectations and the subsequent use of their data is central to Apple’s argument.
Why first party data does not guarantee an exemption
The advertising industry has already started restructuring its services. Rather than relying on shared third-party systems, vendors increasingly offer tools organized around an individual client’s own data. For many businesses, this represents a substantial change in how they operate.
LiveRamp illustrates the scale of that transition. Its traditional role has been to provide shared identity infrastructure for major brands and media companies. Its Authenticated Traffic Solution, a network using publisher-provided data, also strengthens the value of its RampID identifier. Moving to a model restricted to each client’s first-party data means maintaining separate identity graphs instead of a common system that is continually enriched.
Around five years ago, a similar concept was described as a bunkered version of a data clean room. In that arrangement, individual clients’ graphs would not communicate directly. Yet even this restructuring does not guarantee removal from Apple’s blocklist, including under the restrictions associated with iOS 27.
WebKit also considers what the intermediary itself can do. An individual graph may contain only one company’s data, but the central identity resolver remains an outside organization. It can hold information spanning websites and devices and perform matches that each client could not make independently. The product’s label and the origin of its inputs therefore do not settle Apple’s concerns.
How domain blocking puts pressure on vendors
The new restrictions prevent email addresses and other information from reaching identity resolution infrastructure. Protection operates at the domain level, so simply altering the structure of a network request does not bypass it. That creates another obstacle for vendors that have already invested in moving toward first-party data services.
According to AdExchanger, companies affected early by the iOS restrictions included The Trade Desk, LiveRamp, Experian’s Audigent, ID5 and Permutive. Vendors began launching replacement domains that had not yet appeared on WebKit’s blocklist. A source familiar with Permutive’s strategy described the approach as a temporary measure rather than a durable answer.
The Trade Desk provides a specific example. Around the time AdExchanger first reported iOS 27 blocking major advertising vendors, the company created TTDCDN.org. It was intended as a secondary or fallback domain if Apple blocked its main ad-serving domain, adsrvr.org. Such measures may preserve access temporarily, but they leave the conflict with Apple’s approach to tracking unresolved.
Competing views of the post cookie era
Apple sees newer identity technologies as a continuation of practices it wants to prevent. In that account, stronger restrictions are a response to the tracking methods developed after cookies were blocked.
Advertising and marketing companies can make a different argument: Apple’s own decisions forced the industry to find alternatives to established tools. Vendors may regard their products as adaptations to conditions set by the platform. WebKit’s position nevertheless suggests that the advertising industry’s need for identity services is unlikely, by itself, to persuade Apple to relax its protections. Replacing cookies with another identifier no longer assures vendors of continued access on Apple devices.





Комментарии