IAB Tech Lab’s chief operating officer has published her case that Trusted Server, the Tech Lab’s open-source project for first-party ad delivery, is the practical response to the network blocking Apple shipped in version 27 of its operating systems and Safari.

Shailley Singh, COO and EVP of Product at IAB Tech Lab, set out the argument in a post on October 29. “Trusted Server is the only industrywide practical response that I see to Apple’s browser restrictions that can preserve the advertising ecosystem that publishers need,” she wrote. The post is an advocacy piece from the group that maintains the project, and it compares Trusted Server only against the alternatives it names.

What Apple changed

The restriction at issue was described by WebKit on October 19. In its iOS, iPadOS, macOS and visionOS 27 releases, WebKit wrote, “Safari and WebKit block network access to identity resolution infrastructure to prevent cross-site tracking.” WebKit says the blocking works at the domain level, so a vendor cannot avoid it by changing the structure of a request. We covered the post when it appeared in Apple Explains Safari’s Identity Resolution Block in a WebKit Post, and compared three accounts of what the blocklist costs in Three Accounts of Safari’s Ad Tech Blocklist Count Three Different Losses.

Event Partner

The MarTech Summit — Event Partner

Singh says Apple’s earlier Private Browsing 2.0 article describes broader protections against trackers, cloaking and fingerprinting, and that the two publications together show a sustained direction. Her warning is that publishers “cannot base their future on each browser restriction remaining narrow.”

The three requirements and the alternatives

The post sets three requirements for any response: grow and reach audiences at scale, preserve necessary advertising services, and protect publisher and advertiser choice of partners. It then tests two proposals against them without naming who made them.

The first is an industry-built browser. Singh writes that this depends on consumers installing, trusting and regularly using it, and that until then publishers still depend on the browsers their audiences already use. The second is a first-party publisher model powered by agentic software. Agents can negotiate deals and cut operational work, she writes, but the browser still renders the creative, measurement still needs device evidence, and fraud detection and brand safety still need technical support. A third idea, replacing the ad server, gets its own section. Singh says she has led two ad server migrations, both involuntary, and that an ad server returns far more than a creative: inventory forecasts, guaranteed commitments, programmatic transactions and reporting.

What Trusted Server does, according to its documentation

Per the post, Trusted Server places a publisher-controlled execution layer at the edge or behind the publisher’s CDN, supporting server-side auctions, creative processing and first-party delivery paths. The project’s creative processing guide describes one mechanism. Trusted Server rewrites the HTML and CSS of third-party ad creatives so that images, frames and style resources load through the publisher’s own domain, with signed URLs that the guide says prevent in-flight substitution. Rewriting of winning-bid creatives is on by default, while sanitizing them is opt-in and off by default. The guide also forwards an identifier it calls the EC ID to downstream endpoints, as the deployer configures it.

The documentation page carries a notice that it is built from a rolling main branch and “may describe unreleased behavior.” A buyer reading it should treat the settings as the project’s current direction and confirm what has shipped before relying on them.

Singh’s description of how the pieces fit is short. Agents can negotiate transactions through this infrastructure, existing ad servers can contribute their established capabilities, and measurement and verification providers can develop supported methods that preserve independent evidence. She calls that the business case: preserve necessary relationships while reducing dependence on third-party browser connections. The post gives no timeline for publisher adoption and names no publisher running it.

Newsletter

Get the week's best tech coverage.

Free. Read by thousands of HR, tech, and business leaders.

The limits the post concedes

Singh’s post lists several. Trusted Server “is working towards production evidence across integrations, formats, measurement and publisher economics.” Its documentation identifies browser components and creative processing limits that deployments must address. First-party routing “does not make cross-site identity resolution first-party,” and publishers must control downstream data use as well as the browser connection. She also writes that “No architecture can promise immunity from future browser changes.”

That last point sets how far to read the headline claim. The post argues for the best available foundation and reports no deployment with measured results, which leaves publishers and their partners to run the tests themselves.

What it means for the marketing leader

Marketing teams do not run Trusted Server; their publishers and ad tech partners do. The effect reaches a media plan in three places. Match rates and addressable reach on Safari traffic depend on how a publisher’s stack reaches identity vendors. Frequency and measurement reporting depend on whether a verification partner can still collect device evidence through a first-party path. And partner choice, one of Singh’s three requirements, determines whether the vendors in a plan remain callable from the publisher’s page. Safari’s earlier cookie change, covered in Safari 27.2 Fixes a Seven-Day Cap on Cookies Set by CNAME-Hosted Sites, showed that first-party hosting rules shift between browser releases.

One practical step

In our reading, 2027 publisher deals should carry one test. Ask each publisher whether it is testing a first-party delivery layer, which identity and verification partners route through it, and what Safari share of its inventory those partners still reach. A publisher that cannot answer has not yet planned for the version 27 blocking.

Source: IAB Tech Lab, “Apple’s Private browsing and the only practical path for advertising”