iOS 27 Is Blocking Trade Desk Ads in Safari

Affiliate disclosure: This post contains affiliate links. If you buy through them, I may earn a commission at no extra cost to you. Full disclosure

Apple’s iOS 27 is blocking The Trade Desk from serving ads in Safari, according to AdExchanger, which reported the block on September 29.

If you run a high-ticket store and buy programmatic display, retargeting or connected TV through an agency or a self-serve platform, ask this week whether The Trade Desk sits underneath it. Safari carries 46.38% of US mobile browser traffic as of September 2026, per StatCounter, so a vendor that cannot deliver on updated iPhones loses a large slice of mobile reach. I track this kind of platform risk at Ecommerce Paradise because your ad budget is only as stable as the pipes it runs through.

Apple has not said whether the block is deliberate. Below: what the reports confirm, how the Trade Desk got here, what it does to a store built on high-ticket dropshipping, and five checks to run before Black Friday spend ramps up.

Ad vendors can lose a browser overnight, and your business should never be that fragile: form your LLC with Northwest, the best LLC formation service for ecommerce owners. Northwest has 25 years behind it, which is the reason I trust it over cheap formation sites that upsell and disappear. Form your LLC with Northwest →

Safari 27 Blocks adsrvr.org, The Trade Desk’s Ad Delivery Domain

Apple released iOS 27 on September 14, 2026. Within a week, The Trade Desk could not serve ads in Safari on updated devices, per PPC Land.

The blocked domain is adsrvr.org, which AdExchanger describes as The Trade Desk’s primary ad request and delivery domain. Apple’s blocklist also covers UIDAPI.com, the domain tied to Unified ID 2.0, plus identity vendors ID5, Audigent, LiveRamp and Permutive.

Ian Meyer, senior director of engineering at The Trade Desk, raised the issue on GitHub. “Adsrvr.org is The Trade Desk’s core ad request and delivery domain, not identity,” he wrote, according to AdExchanger. PPC Land reports that John Wilander, who handles WebKit privacy and ad tech at Apple, acknowledged the flag.

The timeline is short. KeyBanc Capital Markets analysts wrote that The Trade Desk submitted its request to Apple’s WebKit team on September 21 and that the issue was still unresolved on September 28, per StreetInsider. Neither Apple nor The Trade Desk gave a statement to ExchangeWire for its October 1 digest.

The distinction that matters is identity versus delivery. Blocking an identity vendor lowers bid quality because the buyer knows less about the person. Blocking a delivery domain stops the ad from rendering at all. ReachBrief reports that Trade Desk delivery against Safari inventory on updated iOS devices is “effectively zero.”

Other buyers were not hit the same way. AdExchanger cites test data showing Google’s bids passed through Safari while The Trade Desk’s were blocked on the same impression, and PPC Land reports that Google’s ad.doubleclick.net kept working. ReachBrief does not say whether Meta or Amazon’s DSP are affected, so treat that as unknown.

Nobody has confirmed the cause. ReachBrief writes that whether the block is an intentional policy change, a privacy gate or a bug in the rollout “remains unconfirmed.” KeyBanc, per StreetInsider, called it possible the block was unintentional and estimated a low-single-digit percentage annual revenue headwind for The Trade Desk if it persists. The firm said the impact would likely be immaterial if Apple resolves it quickly, since device upgrades take weeks to spread. Shares traded around $12.15 on September 30 in StreetInsider’s report.

A February WebKit Commit and a Rough Summer for Trade Desk

The rule did not appear in September. PPC Land traced it to a WebKit change committed February 13, 2026: 11 lines added to a file called WebPrivacyHelpers.mm that introduce a check against a private Apple list of domains. That means the logic sat in the code for seven months before iOS 27 shipped it to users.

PPC Land also reports the check works on registrable domains, so every subdomain of a listed domain is caught. The private list holds nine entries, and Audigent is now part of Experian. The same article puts Safari at roughly 15% of global browser traffic. That figure and StatCounter’s 46.38% US mobile figure measure different things, which is why a US store owner should care more than a global chart suggests.

The Trade Desk came into this weakened. It was removed from the S&P 500 on September 4 and cut about 575 jobs the same day, roughly 15% of a 3,843-person workforce, according to PPC Land. The article puts Q2 2026 revenue growth at 3% year over year, the slowest since 2020, and says Q3 guidance implied a 12% decline. Shares fell 24.22% after hours on August 6 after the weak guidance and now sit about 90% below the roughly $80.40 July 2025 index-entry price.

None of the reports link those troubles to Apple’s block. PPC Land says the S&P removal and layoffs are not causally linked in any disclosed sense, and I would not treat the block as a sign Apple is targeting a struggling company.

Here is the counterpoint. AdExchanger lays out two scenarios: accidental miscategorization that Apple fixes, or intentional enforcement that signals tighter treatment of ad tech across Safari. KeyBanc leans toward unintentional. Until Apple speaks, both readings are live, and anyone who tells you they know which one is guessing.

This is not the first platform rule change to move the ground under ad buyers. When Meta widened retargeting audiences in July, I covered how audience rules can shift under a store owner. More recently I covered Google testing a sponsored grid that mimics free listings, another change a store owner had no vote on.

What the Safari Block Means for Store Owners Buying Ads

My read: most store owners never log into The Trade Desk, so the exposure is indirect. It shows up when an agency runs programmatic display for you, when a retargeting vendor buys inventory on your behalf, or when a connected TV platform routes through a demand-side platform you have never heard of. The reports I read do not say which self-serve platforms buy through The Trade Desk, so I will not guess. If you are weighing platforms, my breakdown of the best CTV platforms for Shopify stores covers how they differ.

The baseline matters here. StatCounter has Chrome at 47.44% of US mobile browser traffic and Safari at 46.38%, with Samsung Internet at 3.28% and Firefox at 1.29%. Two browsers carry nearly 94% of US phones, which means a delivery gap on one of them cannot be averaged away by the small ones. When one of the two big pipes narrows, your reach narrows with it.

The money does not leak the way people assume. As far as I know, demand-side platforms bill on delivered impressions, so an ad that never renders should not appear on your invoice. The real damage is lost reach and a skewed audience. Your campaign keeps spending, but it spends on Chrome, Android and desktop inventory, and the iPhone buyers disappear from your frequency caps and your retargeting rotation.

Here is hypothetical math, and I am labeling it as such. Say you push $10,000 a month through an agency whose programmatic buying runs on The Trade Desk, and 60% of delivery is mobile. If Safari’s 46.38% US mobile share applied to that mix, about 28% of your impressions, or $2,800 of that budget, would be aimed at inventory that cannot currently serve. Real exposure is lower because the block only hits devices that have updated to iOS 27, and it climbs every week as people update.

Here is how I would set thresholds. If Safari on iOS 27 is under 10% of your programmatic delivery, note it and move on. Between 10% and 25%, ask your vendor for a rebalanced plan and a written make-good. Above 25%, I would pause Trade Desk-routed retargeting and move that budget to channels where delivery is intact until Apple resolves it.

When you email your agency, ask for the numbers in a form you can check yourself: impressions by operating system, by browser and by week, starting August 1 so you have a clean baseline. A vendor who has watched the account will have that report in an hour. A vendor who has not will take days, and that delay is information about how closely they manage your spend.

High-ticket stores feel this harder than low-ticket stores because the buying cycle is long. A shopper researching a $4,000 product visits three or four times over two weeks, and the retargeting touch between visits does real work. Take Safari users out of that rotation and you remove the second and third impression for a chunk of your best audience. I wrote about why the conversion system around the click matters as much as the click itself, and this is a live example.

My opinion on where to put the money: Google Shopping and search capture people who already typed the product name, and they sit on Google’s own delivery domains, which reports say still work in Safari. My guide on turning Google Shopping clicks into sales is where I would start. Treat programmatic and connected TV as an add-on after search is working, which is how I rank ad platforms for high-ticket stores.

The bigger lesson is dependence. Apple can change what a browser loads in a point release, and a vendor cannot appeal, bid around or detect the change in advance. The only defense is owning your audience: your Shopify store data, your email list, and your phone number on every page.

Organic traffic belongs on that list too, and a tool like Semrush shows you which product and category searches are worth building toward. Older, affluent buyers still pick up the phone before a big purchase, so I want a real number on the site, and Grasshopper is an easy way to add one. No browser update can take either of those away from you.

If auditing ad vendors sounds like a second job, that is the problem my team solves. We build and run high-ticket stores, from supplier onboarding to ad accounts, through the turnkey done-for-you service, so a surprise like this lands on a team with a checklist instead of on you.

Rebuilding your ad mix after a channel breaks? Want my team to scale the store you already have, with ad channels we have tested? See the scaling service →

Five Checks to Run on Your Ad Spend This Week

These need nothing you do not already have access to.

  1. Pull programmatic, retargeting and connected TV reports for September 14 through today and compare Safari and iOS impressions to the two weeks before. A drop of more than a third on Apple devices is your signal. If you have no breakdown by device, ask for one, because you cannot manage what the report hides.
  2. Email every agency and ad vendor and ask in writing which demand-side platform buys your inventory, whether it is The Trade Desk, and what Safari delivery has been since September 14. Their answer, or their silence, tells you how closely they watch your account. Use my guide to measuring ROI on CTV campaigns to frame the ask.
  3. Open Shopify analytics and check sessions by browser for the last 30 days. Write down Safari’s share of your own traffic, because the national 46.38% is not your number. If Safari is above 50% of your sessions, this story matters more to you than to most. If you want a second set of eyes on the numbers, start with my discovery page.
  4. Move the budget you would have spent on blocked Safari inventory to channels where delivery is intact. For most high-ticket stores that means Google Shopping and search first, then Meta retargeting. Cap the shift at 20% of the affected budget until you see two weeks of clean data.
  5. Collect the audience you own. Set up an abandoned-cart and browse-abandonment flow in Klaviyo and ask for a phone number at checkout. Configure your consent banner with Termly so you can legally email what you collect.

Frequently Asked Questions

Do I need to worry if I only run Google and Meta ads?
The reports I read do not say Meta or Google Ads are affected, and two of them say Google’s delivery still works in Safari. Still check your Safari share in Shopify, and read my note on ChatGPT Ads bulk product campaigns if you are testing newer channels.

Does iOS 27 block all ads in Safari?
No. PPC Land lists nine entries on Apple’s private list, and the check only catches requests to those registrable domains. Ads served from other domains are not caught by it.

Will Apple fix it?
Nobody outside Apple knows. KeyBanc called an unintentional block possible, and Apple had offered no resolution as of ExchangeWire’s October 1 digest.

Does a blocked ad cost me money?
As far as I know, unrendered impressions are not billed, but you lose reach and your campaigns skew toward other devices. Tag spend by channel in your books with a tool like Finaloop so an under-delivering channel shows up in the numbers. My post on why your payout is not your profit shows how to read them.

What is the cheapest way to cut my dependence on ad vendors?
Build an email and SMS list you own. Omnisend is a solid alternative if Klaviyo feels like too much. My guide to high-ticket sales follow-up covers what to send.

I have no ad budget yet. Where do I start?
Start with the niche and the supplier, not the ad platform. Grab my free list at ecommerceparadise.com/niches. Then read the high-ticket niches list before you spend a dollar.

Want 1-on-1 coaching to decide which ad channels deserve your budget before the next platform change hits? Get the coaching details →

Subscribe to the YouTube channel for daily breakdowns. More breaking news coming through the day.

Related Articles

If this was useful, these go deeper:

Free 1,000+ high-ticket niches list

Still deciding what to sell?

Grab the free list of 1,000+ niches that work for high-ticket dropshipping, sorted by category.

Free. Unsubscribe any time.