The Maze: Publishers are starting to count the cost of Apple’s Safari tracking restrictions. Aditude, which helps websites sell ad space, reports a 10.5% drop in earnings per thousand shown ads among readers who installed the relevant software update. Other publishers report little immediate change. The October 12 findings reveal uneven exposure: the browser a reader uses, their installed software and a publisher’s advertising partners all matter. The sample’s country mix and measurement window remain undisclosed.

Source: WebKit. WebKit’s 2024 Mac settings illustration shows protection enabled for all browsing. This is historical interface context, not today’s iPhone screen or a revenue measurement.
The 10.5% decline describes a slice of traffic. Aditude measured effective earnings per thousand ads shown, often called eCPM, among upgraded users. In its customer data, Safari on iPhones and iPads represents 11.7% of ads shown and 11.4% of ad revenue. Those figures describe Aditude’s customers, rather than the whole publishing market. Aditude also estimates roughly 8% software adoption and a current overall revenue effect of about 1%. The report does not disclose enough about those estimates’ denominator or calculation to independently reconstruct them. A fall in the price earned per ad is different from a fall in a publisher’s total income.
Safari targets recognition across websites. Advertising software can combine device and browser clues to recognize the same reader on different sites. That process is called fingerprinting. Apple announced protection across all Safari browsing by default in iOS 26 in 2025. WebKit’s technical explanation describes restrictions on known fingerprinting scripts accessing device signals, storing persistent data and reading navigation information. These are privacy controls, rather than a promise to remove every advertisement. Code used by an advertising vendor can nevertheless stop working, affecting its ability to buy or deliver ads. The new event here is early impact reporting, rather than the original privacy announcement.
Some publishers have little immediate exposure. Publishers advised by consultant Scott Messer noticed little change. Two senior news-publisher executives also reported no impact; one pointed to a business funded mainly by subscriptions. Index Exchange, which operates advertising exchange infrastructure, said it was largely unaffected because it does not depend on identity code in the same way. These are individual observations, not a representative survey. They explain why one vendor’s reported decline cannot be applied to every website. A publisher’s dependence on automated ad sales matters alongside its Safari audience share.
A test-build correction is still a test-build correction. The Trade Desk buys advertising space for advertisers. Its ad-serving component was removed from Apple’s blocklist in a test version of iOS after engineers filed a bug report. The October 12 report says users of the current public version remained blocked. That change could alter the eventual damage for publishers using the vendor, but it did not establish a fix already available to those readers. Public delivery timing remains unconfirmed here.
Why it matters: For publishers and advertisers in any market, the useful question is which software and advertising partners their readers actually use. Track earnings on upgraded Safari traffic separately from total revenue before treating a headline percentage as a budget forecast. Aditude’s early signal deserves attention, while subscription-heavy publishers and less identity-dependent vendors offer a counterweight. The next evidence to watch is broader adoption and a verified public vendor fix, with each estimate’s scope intact.
Sources: Digiday · Apple · WebKit Safari 26 · WebKit historical settings
Images: 1 Apple via WebKit · Cover AI-generated


