Apple is switching off the identity layer. Here’s what it means for your reach.

When Apple shipped iOS 27 in September, Safari began blocking a short, unpublished list of ad tech domains. The headline casualty was The Trade Desk, whose ads stopped serving in Safari on updated devices. Apple has since released a beta that restores The Trade Desk’s ad-serving domain, and the fix should reach users in the coming weeks.

It’s tempting to read that as the end of the story. It’s the beginning.

The rest of the list stays in place: the sync domains behind UID2, ID5, LiveRamp, Permutive and Audigent, some of the most widely used identity solutions on the open web. Industry reporting suggests Apple is preparing a much broader list covering hundreds of vendors that handle user data and device IDs. Apple has published no rules, no timeline and no appeal process. Vendors found out when publishers asked why ads had stopped rendering.

Many DSPs only bid on placements that carry an identifier. In Safari, identity vendors used to fill that gap by adding an alternative ID to the bid request. With those vendors blocked, an ID-dependent campaign simply stops bidding on a large share of iPhone traffic.

The campaign keeps running and the dashboard stays full. What changes is who you reach. Spend concentrates on the browsers the ID layer can still see, and the audience you lose leaves no trace in the report.

Identity also stitches the journey together: a streaming spot to a mobile ad, a TV flight to a spike in search. When the identity layer goes dark in Safari, those connections break for every Safari user at once. Some advertisers have already paid for impressions in winning auctions that never rendered on screen.

1. Reach risk: your addressable audience is defined by a browser vendor’s list, which can change with any update. 2. Measurement risk: results look stable because the missing users are absent from the data. 3. Delivery risk: a block aimed at identity can take out ad serving on the same domain, as The Trade Desk learned. 4. Governance risk: the rules are unpublished and can change overnight.

Start with a dependency audit. Ask every partner three questions. Which domains does the reader’s device call during an ad request? What share of my reach relies on an identifier? How do targeting, frequency and measurement behave in Safari today?

Then build on the one signal every reader requests: the page itself. Context is present on every page view, in every browser, on every device. It describes the moment someone is in, which is often the clearest sign of what they care about right now. Identity can sit on top as a layer where it exists. Context carries the plan everywhere else.

C Wire matches brand meaning to editorial and video moments across 500+ premium publishers. MatchPersona finds where your target personas are reading and watching, using the content of the page as the signal. Because the signal travels with the page, campaigns plan the same way across every browser, and the audience you planned for is the audience you reach.

The industry’s long-term fix, moving ad calls onto publisher-controlled servers, is still in testing. Until it scales, the brands that keep their reach will be the ones whose plans already run on context.