Identity doomsday: What iOS 27 means for the future of identity

What iOS 27 means for the future of identity

Apple just showed the ad industry who decides whether your identity works. It isn't you, and it isn't your vendor.

On September 14, Apple shipped iOS 27. Inside was an 11-line change to Safari that blocks a set of identity and ad tech domains outright. The user's privacy settings don't matter. Neither does the fact that your vendor's tag loads on your page. The request never leaves the phone.

Nobody was warned. The Trade Desk found out when its ads stopped serving on iPhones. Its engineers filed an urgent bug. Apple's answer: "We're investigating."

Then it got bigger. AdExchanger reports that Apple has swapped its short list for a private library of hundreds of CDPs, ad tech and martech companies, data sellers and ID graph operators. Vendors may not know they're on it. Only Apple knows the rules.

I've been saying since May that brands should stop renting their identity and start owning it. Until now, that was an argument about cost and control. iOS 27 makes it an argument about survival.

This isn't a bug. It's a policy.

The first names on the list tell you exactly what Apple is going after:

→ uidapi.com, for Unified ID 2.0

→ adsrvr.org, The Trade Desk's ad delivery domain

→ id5-sync.com and eu-1-id5-sync.com, for ID5

→ rlcdn.com and pippio.com, for LiveRamp

→ permutive.com, for Permutive

→ ad.gt, for Experian's Audigent

The Trade Desk's own engineer said it plainly in his bug report: "The intent seems to be to hard block domains that power 'post-cookie' identity."

That's the post-cookie playbook. Every one of these companies sold the industry a way to keep recognizing people after third-party cookies faded. Apple just switched them off for some of the most valuable users on the web. And because every iPhone browser has to run on WebKit, Chrome and Firefox users are cut off too.

No vendor can promise you it's safe

Three weeks after the block, Apple let The Trade Desk's ad server back in through a test build of iOS. The identity domains stayed blocked.

Look at why. Apple runs its own ad network, so blocking a rival's ad delivery invited questions about abuse of position. Identity vendors don't compete with Apple, and Apple can defend blocking them on privacy grounds. They have no leverage.

Neither do you. If the vendor you rent your identity from lands on the list, you can't file a bug and wait for Apple to call you back. You find out when your numbers drop.

For now, the damage is narrow. Digiday tested more than 70 ad tech domains and found only the original handful blocked. LiveIntent, Lotame and Yahoo ConnectID got through.

Don't mistake that for safety. AdExchanger reports that Apple devices already check a remote list Apple can change at will. Digiday reports that code hasn't shipped yet. Either way, the direction is set. "What this will allow Apple to do is make this block list dynamic," said Rowena Lam of IAB Tech Lab.

So any vendor that tells you it's fine is guessing. It can't see the list either.

ID vendors are already testing workarounds, like moving their pixels server-side. Expect a long game of cat and mouse, where every workaround lasts only until Apple closes it.

Renting your identity used to mean one landlord. Now there are two.

Last week, Nick Jordan wrote that Publicis buying LiveRamp ends the era of neutral identity. Your identity provider now has a side.

iOS 27 adds a second landlord. Even if your vendor stays independent, the browser decides whether it works.

Rent your identity, and two companies you don't control get a vote on whether it keeps working. Own it, and they get a vote on one input.

Your customer records (logins, purchases, loyalty accounts, the CRM) live in systems you control. No browser update can reach them. Email-based matching still works outside Safari. The vendors hit hardest are the ones whose product links cookieless browsers back to cookies.

What control buys you when the list keeps changing

You can't control Apple's list, but you can control how much time and money it you when it changes. It’s the difference between an existential meltdown (i.e. we are “all in” on 1-2 IDs) and an annoying adjustment.

• ‍You see changes first. When your identity lives in your own systems, you watch match rates by browser and OS yourself. If a vendor goes dark on Safari, you spot it in minutes/hours/days.‍
• You know the blast radius. You know which audiences and reports depend on which vendor, so you know what breaks and what doesn't.‍
• You swap the vendor, not the strategy. Your audiences, suppression lists and measurement keep running on the records you hold. Brands that rent have nothing to fall back on, because the vendor's graph was their graph.‍
• You can tell a broken signal from a bad campaign. With your own baseline, a Safari drop shows up as a data problem, so you don't pull budget from something that's working.

When the rules can change on a Tuesday, the brands that own their identity adjust that week. The rest wait on their vendors, who are waiting on Apple.

Run these five checks this quarter

You don't need a new vendor for any of these, and most take an afternoon.

1. List every identity, data and ad tech vendor that touches your website or app. Check each one against the domains above.
2. Ask each vendor in writing whether it's on Apple's list, on the "potentially blocked" list, or in talks with Apple, and what it will do if it gets blocked. Give them a deadline.
3. Compare your match rates, audience sizes and conversions for Safari and iPhone traffic since September 14 with the month before. If your analytics can split traffic by iOS version, compare iOS 27 with iOS 26 for the same weeks.
4. Sort your identity signals into two groups: signals collected in a browser, and signals from your own customer records. Write down who controls each one.
5. For the second group, write down where the records live, who can access them, and how long it takes to use them for matching, measurement and activation.

‍

Curious what data normalization can do? Book a demo and see Narrative run inside your own environment.