The story. A new iOS 27.2 beta removes The Trade Desk’s ad-serving domain from Apple’s Safari blocklist. The identity vendors on the list stay blocked, and WebKit holds a wider list of hundreds of vendors that Apple has not published. (AdExchanger, The Apple Bites Back, 9 October 2026)
01What happened
- The Trade Desk is cleared in the beta. AdExchanger reports that iOS 27.2 removes adsrvr.org, the DSP’s core ad request and delivery domain, from the blocklist.
- The fix is not live yet. It must become the default install first, which AdExchanger says might take three or four weeks. Anyone who downloads iOS 27 today still blocks The Trade Desk’s ads.
- The identity vendors are still blocked. LiveRamp, UID2 and ID5 remain on the list, along with Permutive and Audigent, so cross-channel matching on iOS 27 is still impaired.
- The wider list is untouched. According to AdExchanger’s sources, WebKit holds a private list of hundreds of ad tech, martech and identity vendors, and only Apple knows what gets a vendor blocked.
- Apple has said little. AdExchanger says that, unlike with Intelligent Tracking Prevention in 2017 or AppTrackingTransparency in 2021, there was no guidance or developer-conference session this time.
- Some spend went to ads that never rendered. Two agency buyers told AdExchanger that win logs for Trade Desk clients show iOS 27 impressions that did not serve.
02What it means inside a GAM network
Our earlier coverage asked whether the block on a DSP’s serving domain was a mistake. The beta removing the domain points to an unintended side effect for The Trade Desk. The lesson for a publisher sits elsewhere.
Safari blocks at the domain level. AdExchanger’s read is that the block aimed at match.adsrvr.org, the cookie-sync endpoint, and took the serving domain down with it. Any vendor that keeps matching and serving on one domain carries the same risk, and a publisher’s own stack does too.
The second effect is bidding. AdExchanger says identity vendors often put an alternative ID into the Safari bidstream, and many DSPs bid only on targetable placements. If that ID is blocked, the impression can lose bidders even when the ad would have rendered.
Measurement vendors told AdExchanger the Trade Desk focus has hidden how large the analytics and attribution problem is. Buyers use identity to stitch streaming, mobile and web traffic together. If your buyers cannot do that on iOS 27, expect questions about reporting before you see a change in bid price.
One limit on the evidence: iOS 27 adoption is still low, and AdExchanger describes the revenue hit as limited. We have no figure for how much Safari revenue is at risk.
The headline fix covers one vendor, and the wider blocklist is still Apple's to edit.
03What publishers should do about it
04The bottom line
The headline fix covers one vendor, and the wider blocklist is still Apple’s to edit. Publishers should measure Safari by iOS version, keep a signal that does not depend on a blocked ID, and ask partners to separate serving from matching.