Apple's Safari changes and IAB Tech Lab Trusted Server

Apple's Safari changes and IAB Tech Lab Trusted Server

Apple has begun restricting some ad tech and identity domains in Safari, and early data indicates an effect on publisher revenue. IAB Tech Lab's open-source Trusted Server is one of the approaches being explored. Here is our first update on what's happening, and what Trusted Server is

 

When Apple released iOS 27 on 14 September 2026, it included a change that Apple didn't explain publicly until
19 October. WebKit, the engine behind Safari, no longer connects to a small number of ad tech and identity domains.
If a domain is on the list, the browser doesn't make the request, which means bids, identity matching and ads from that company don't load.

 

Every browser on iPhone and iPad runs on WebKit, so Chrome and in-app browsers are affected too. Apple says the change also applies to Safari on Mac and Apple's other version 27 operating systems.

 

What's on the list?

 

Apple hasn't published the list. It came to light on 21 September, when The Trade Desk filed a bug report with WebKit after its ads stopped serving in Safari. The report listed nine entries: eight vendor domains belonging to The Trade Desk, Unified ID 2.0, ID5, LiveRamp, Permutive and Audigent (now part of Experian), plus what appears to be a test entry.

 

This change differs from earlier Safari privacy updates in three ways. There is no published list, criteria or appeal process. It applies to every subdomain of a listed company and overrides Safari's usual exceptions. And it extends beyond Safari, because every browser on iPhone and iPad uses the same engine.

 

What's Apple has said

 

On 19 October, Apple's WebKit team explained the block in a blog post. It said Safari now blocks third parties that, in Apple's view, collect email addresses when people log in or sign up to newsletters and turn them into persistent tracking IDs. Apple said the login and newsletter services themselves are not the target.

 

Apple said it blocks whole domains by design, so that requests can't be restructured to avoid the block. The post did not name companies or explain how domains are selected.

 

Two points are particularly relevant for publishers. First, Apple says a publisher using its own readers’ data to personalise its own site isn’t tracking, but passing readers’ email addresses to an outside identity company that matches them across sites is. Second, IAB Australia’s reading is that sending the same data from a server rather than the browser is unlikely to change this. On that basis, IAB Tech Lab’s Trusted Server can help route a publisher’s own ad calls, but it would not provide a way to continue sharing email-based IDs that Apple has blocked.

 

The current state of play

 

Apple released iOS 27.2 on 26 October. According to IAB Australia, WebKit marked The Trade Desk's bug report as resolved during iOS 27.2 testing, so its ad domain should now load on updated devices, although Apple's release notes don't mention it. The identity and data domains in the original bug report are understood to remain blocked. Trade press reports suggest Apple is preparing a much larger list, covering hundreds of data and ad tech companies, which could be updated without a new iOS release. Apple has not confirmed these reports.

 

Early data suggests revenue is being affected, with the largest impact so far on Mac. Data from ad tech company Aditude, reported by Digiday, shows that, for affected readers:

  • Bid rates are down about 8% on iOS and 25% on Mac
  • eCPMs are down 4% on iOS and 11% on Mac
  • Revenue per ad opportunity is down 6% on iOS and 20% on Mac.

 

WebKit browsers account for about 30% of ad impressions across Aditude's customers.

 

Some companies have started trialling responses. ID5 has begun testing server-side integrations with selected publishers, and US publisher Paradium, owner of Parade and Men's Journal, has rerouted its blocked Permutive integration through Trusted Server to test whether audience data flows in Safari.

 

The wider context

 

The change follows a decade of browser privacy updates. Safari has restricted tracking since 2017 and blocked third-party cookies by default since 2020. Firefox, Brave and Microsoft Edge have all added their own protections. Google developed Privacy Sandbox for Chrome over six years before retiring most of it in October 2025, and publishers that had built on it needed to adjust.

 

Each change has affected setups that rely on the reader's browser calling a vendor's domain. iOS 27 differs in that the browser doesn't make the call at all. As IAB Australia puts it, "If you build your monetisation on a browser vendor's roadmap, you will inherit its reversals." In New Zealand, iOS accounted for about half (49.29%) of mobile web page views in October 2026, according to StatCounter. Source: StatCounter - Mobile operating system market share, New Zealand

 

A simple test from Daniel Jaye, Founder and CEO of Aqfer in New York, cited by IAB Australia, can help publishers assess their exposure. If the answer to any of the questions below isn't "ours", that call may be more exposed to future changes.

 

Jaye suggests asking three questions for every call your pages and apps make:

  1. Whose domain is it? If it’s not yours, it could be on a future blocklist.

  2. Whose relationship does it serve? Jaye suggests anchoring identity to the consumer’s relationship with you,
    rather than to a vendor’s graph.

  3. Whose infrastructure holds the data? If your partner’s cloud holds it, your resilience may depend on their roadmap.

 

Jaye recommends designing for the next blocklist, not the last one.

 

What Trusted Server is

 

Trusted Server is a free, open-source framework from IAB Tech Lab, released under the Apache 2.0 licence. It moves ad requests, auctions and ad delivery out of the reader's browser and onto infrastructure the publisher controls, under the publisher's own domain. IAB Tech Lab calls it "the new execution layer for the open web".

 

It's software, not a service. A publisher runs it at the edge of its network, on its content delivery network (CDN) or just behind it, so every page and ad request passes through it. It runs on Fastly, Cloudflare and Fermyon Spin, or on a publisher's own servers using Docker or Kubernetes. Akamai's EdgeWorkers platform isn't supported yet.

 

Because calls to ad partners go from the publisher's server rather than the reader's browser, they aren't subject to the WebKit domain block, although Apple's position on data sharing still applies. The publisher also controls what data each partner receives.

 

How it works

 

Today, on most websites, the ad auction runs in the reader's browser. Scripts such as Prebid.js send bid requests to several supply-side platforms (SSPs), the ad server picks a winner, and verification, measurement and identity tags fire in the background. A single page view can involve many companies dealing directly with the reader's browser.

 

With Trusted Server, the process looks like this:

  • A reader visits the publisher's website. The request goes to the publisher's own domain and passes through
    Trusted Server.
  • Trusted Server reads the reader's consent signals and the publisher's own first-party signals, and sets or reads the Edge Cookie, an identifier the publisher creates and controls.
  • It runs a server-side auction through Prebid Server, calling SSPs directly from the server where consent allows.
  • SSPs return their bids.
  • Trusted Server picks the winner, stitches the ad into the page and returns it to the reader.
  • The reader's browser shows the ad as part of the publisher's site, without calling any third-party ad tech domain.

 

Trusted Server works alongside Prebid Server rather than replacing it. Prebid Server runs the auction. Trusted Server prepares the signals going in, then hands the result to the ad server and places the winning ad on the page. IAB Australia notes existing SSP relationships can carry over, although commercial agreements still apply, and publishers can move gradually, running a share of inventory through Trusted Server while the rest stays as it is.

 

Other features include:

  • Consent handling for TCF v2, GPP and GPC signals, applied before any data leaves the publisher
  • Signed outgoing requests, so partners can check they came from the publisher
  • Support for display, native and video ads, and integrations with ID and audience providers
  • A command-line tool that audits a live page and drafts a starting configuration.

 

IAB Australia recommends running Trusted Server in the publisher's main request path, at or behind its CDN, rather than on a separate subdomain that points to a vendor. Safari limits cookies set through those vendor subdomains to seven days, which would reduce the value of the Edge Cookie. Safari 27.2 fixed a separate bug that applied the same seven-day limit to some publishers whose site points to a CDN, but cookies set through vendor subdomains are still capped.

 

Trusted Server’s current status

 

IAB Tech Lab declared Trusted Server production-ready on 8 October 2026, and IAB Tech Lab CEO Anthony Katsur has urged publishers to "go server side". It is at an early stage. There are no tagged public releases yet, so engineering teams may want to lock to a specific version and test it thoroughly. It doesn't yet integrate directly with Google Ad Manager, which is widely used by New Zealand publishers, and it covers websites, not ads inside native apps. Fraud signals, brand safety and server-side measurement are on the roadmap. Adoption is at an early stage internationally. IAB Tech Lab says interest has increased since the Safari changes, but the publicly named tests so far are in the US.

 

Katsur also describes it as "one tool in a publisher's tool belt", not a guarantee of revenue.The software is free, but it needs developers and edge hosting, where page and ad requests are typically billed as traffic.

 

It does not change a publisher's obligations under Apple's policies or consent requirements, and the publisher remains accountable for the data it shares.

 

What publishers can do now

 

Publishers may find it useful to assess their exposure, for example by checking which pages call affected domains and splitting Safari revenue by iOS version and device. Larger publishers with engineering resources may want to run Trusted Server's page audit on a live page and watch early results offshore.

 

Agencies and buyers can ask their partners how they're responding to the Safari changes. Ad tech members can help by sharing their position on Trusted Server with publisher partners. IAB Tech Lab also welcomes publishers to join its Trusted Server Task Force, which sets priorities such as fraud, brand safety and measurement.

 

Find out more

 

IAB Tech Lab's recent webinar on Trusted Server is available on demand: IAB Tech Lab Trusted Server webinar.

IAB New Zealand will keep tracking developments and share updates from IAB Tech Lab and IAB Australia.

 

Further reading

 

Thank you to Jonas Jaanimagi and IAB Australia, whose explainer on Apple domain blocking and Trusted Server informed this article.

 

 

Our Members

Our members include advertisers, agencies, ad tech companies and media owners, so you're in the right place to discover the very best of digital advertising.
CalibreCandor_whitetext
8cd3dc17-56f2-4b9a-8b90-eb6bcd3d02f3-company_logo-RE_Horizontal_White_RGB
TVNZ+_White
Azira logo white
MarsUnitedCommerce-LS-White
Stitch White Logo-TRANSPARENT