Channel sheet · CH-29 · gain 4 min · logged November 17, 2026

Martech StackDirect input

Safari's Identity Block: The Tide Just Went Out on Ad Tech

Safari has blocked UID2, ID5, LiveRamp, Permutive and Audigent since mid-September, with no workaround — and the identity solutions they replaced cookies with never worked that well anyway.

By Marcus Bennett4 min read766 words

Signal notes

  1. Safari has blocked identity vendors UID2, ID5, LiveRamp, Permutive and Audigent since mid-September, with WebKit's rationale published 19 October.
  2. eMarketer puts Apple's US ad revenue above USD$8.5bn (£6.3bn) this year.
  3. In one cited study, 17 of 18 identity companies issued an ID to a self-declared bot crawler; one ID followed it across nearly 30,000 sites.
  4. Google retired most of Privacy Sandbox in 2025 after dropping its cookie phase-out plan in 2024.
  5. Apple Maps began serving ads in August, one month before Safari's identity block.
Ad Tech Tides: Building the Same Castle, Just Higher Up the Beach
Input monitorAd Tech Tides: Building the Same Castle, Just Higher Up the Beach — manuelamilani / pixabay

Since mid-September, Safari has blocked domains belonging to the companies that turn email addresses into cross-site IDs — UID2, ID5, LiveRamp, Permutive and Audigent all landed on the list. Apple stayed quiet for a month, then on 19 October the WebKit team published its reasoning, and it read less like an explanation than a policy. The vendors, Apple said bluntly, are "just there to track you."

That's the hardest fact in this story, and it lands on an industry that has spent a decade rebuilding the same castle every time the rules shifted.

How did we get here?

Shirley Marschall, writing in her weekly column, walks the timeline, and it's worth repeating because the pattern is unmistakable:

  • 2017: Apple shipped Intelligent Tracking Prevention in Safari. Ad tech answered with first-party cookie workarounds.
  • 2018: GDPR hit Europe. Consent banners became the visible face of compliance while ad tech built "compliant tracking" — with cookies still available underneath.
  • 2020: Safari blocked third-party cookies outright and closed the CNAME cloaking loophole that had disguised third-party trackers as part of a site's own domain. Google gave Chrome cookies two years to live.
  • 2021: App Tracking Transparency made the IDFA opt-in; most users declined. The industry rebuilt around probabilistic matching and fingerprinting. Google's Privacy Sandbox launched its own experiments, then Google pushed its deadline back for the first time.
  • 2024: Google dropped the cookie phase-out plan entirely.
  • 2025: Google retired most of Privacy Sandbox — years of preparation for a deadline that never arrived.

Regulators moved too. California's privacy law, the European Commission's Digital Omnibus, and Australia's privacy regulator pulling inferred data, third-party enrichment and AI-generated attributes under privacy law. Marschall's warning: what starts down under rarely stays there.

What does this change for independents?

The block reaches every updated Apple screen, and there's no clever workaround. Everything built to replicate the cookie assumed the browser would keep tolerating the replica. The newsletter sign-up was always the weak point — people hand over an email address for a discount code, not to become a node in somebody's identity graph. That gap is exactly where Apple's intervention lands.

The incentive difference matters. Google needed the open web's ad stack to keep working, which is partly why the cookie tide never fully went out. Apple has no such dependency — but it does have first-party data. Apple Maps started serving ads in August. Safari started blocking identity vendors in September. eMarketer puts Apple's US ad revenue at more than USD$8.5bn (£6.3bn) this year, and some think regulators should take a look.

The walled gardens barely felt it. Meta, Amazon and TikTok hold the logins, which makes them first parties by Apple's own definition. In The Trade Desk's own bug report, Google's bids sailed through on the same Safari page where TTD's were blocked.

The Trade Desk's ad server, caught in the block by mistake, is back in Safari. UID2 isn't. IAB Tech Lab, meanwhile, is pushing the industry server-side — which, as Marschall puts it, is a few metres further up the beach.

Was the last castle even worth building?

Here's the uncomfortable part. Augustine Fou pulled the research together, and it isn't flattering:

  • In one study, researchers tracked IDs across more than 600,000 websites using a crawler that openly declared itself a bot. Seventeen of the 18 identity companies gave it an ID anyway — and one of those IDs followed it across nearly 30,000 sites.
  • In another, an HP campaign aimed at IT decision-makers through bought segments reached people who, more than eight times in ten, had no role in buying technology. The segments performed worse than random.

So the industry is left holding identity solutions built on sand it doesn't own, for targeting that never worked as well as advertised. GDPR was supposed to "end programmatic"; cookie deprecation was supposed to "end targeting". Neither happened — digital advertising adapted. But every adaptation meant rebuilding the targeting it had just lost, in whatever space the latest rule left open, and expecting this version to last.

Someone will move the waterline again, and the next workaround will be pitched as the one that holds. Then the water will come back, and so will the castles. Marschall's closing point is the one practitioners should sit with: maybe the next step isn't finding higher ground, but building on foundations that don't depend on the water staying where it is.

via exchangewire.com (Source)

Filed under

  • safari
  • ad-tech
  • identity-tracking
  • online-privacy
  • first-party-data
Share this article:

More from Marcus Bennett

Marcus Bennett

Show full bio

Senior reporter covering technology and product news in marketing professionals running AI in the stack at Mart Signal.

161 articles

Bus out

‹ Previous article