iOS 27 Blocks The Trade Desk From Serving Ads in Safari

The Trade Desk cannot serve ads in Safari on devices running iOS 27, released September 14. Apple is investigating the failure, but no fix or explanation has been issued yet.
By Marcus Bennett
2 min readAt a glance
- The Trade Desk cannot serve ads to Safari on devices running iOS 27, released September 14.
- Apple has been investigating the issue since last week with no resolution announced.
- Neither Apple nor The Trade Desk has publicly confirmed the cause of the ad delivery block.
The Trade Desk cannot serve ads to Safari users who installed iOS 27, Apple's latest operating system update released on September 14. The outage affects Apple device owners across Safari, cutting off one of the largest independent ad exchanges from a major browser inventory pool.
Apple has been investigating the issue since last week, according to AdExchanger. As of now, there is no resolution.
The scope of the problem is defined by two hard facts: the block applies to Safari on devices running iOS 27, and the operating system shipped on September 14. Everything beyond that — whether the block stems from an intentional policy change, a privacy-related technical gate, or simply a bug in the rollout — remains unconfirmed. Apple has not publicly stated the cause, and The Trade Desk has not detailed the mechanics of the failure. Practitioners should treat causal claims circulating in industry discussion as speculation until either company issues an official statement.
For advertisers and agencies running campaigns through The Trade Desk, the practical impact is straightforward. Any Apple device that has updated to iOS 27 no longer receives Trade Desk-served ads in Safari. That means delivery against Safari inventory on updated devices is effectively zero for those campaigns, and buyers may see drops in reach, delivery rates, and potentially skewed frequency and performance metrics as budgets shift elsewhere. Campaigns targeting Apple-heavy audiences — a substantial share of premium mobile and tablet traffic in many Western markets — will feel the gap most acutely.
Media buyers should audit current campaigns now. Check delivery reports for Safari-specific performance since mid-September, flag any unexplained drops in impression volume against Apple device IDs, and ask their Trade Desk account teams for guidance on how the platform is handling reallocation. Advertisers with strict reach commitments or frequency targets against iOS audiences may need interim adjustments, such as shifting spend to channels that still reach updated Safari users or reassessing pacing.
The timing matters for another reason. Safari has spent years stripping away ad-targeting signals, from ITP's cookie restrictions onward, and any ambiguity about whether this block is deliberate or accidental feeds directly into that history. But the available reporting does not establish intent. The only confirmed position: ads are not serving, Apple is investigating, and no fix has landed. Amplifying theories about a permanent Safari ad lockout ahead of confirmation would put unverified claims in front of decision-makers who are already recalibrating budgets.
Watch for three signals in the coming days: an Apple statement clarifying whether the block is a bug or a feature, a Trade Desk advisory to clients with workaround details, and delivery data showing whether the failure extends beyond iOS 27 devices or Safari specifically. Until Apple resolves the issue or explains it, buyers should assume the block persists and plan Safari reach on updated devices accordingly.
Original: bugs.webkit.org
Marcus Bennett
Show full bio
Market editor covering money, funding and market shifts around Social platform news and policy at Reach Brief.