Apple keeps tightening Safari, and the industry group behind a server-side fix is making a maximal claim: every other answer fails. The claim deserves attention, but the product’s own evidence is still thin.
What the essay argues
Shailley Singh, COO and EVP of product at IAB Tech Lab, published an essay on October 29 and updated it on October 31 arguing that Trusted Server is “the only industrywide practical response” to Apple’s browser restrictions. The software is an IAB Tech Lab project, and Singh leads its product team.
The backdrop is Apple’s WebKit 27 release, which blocks network access to identity-resolution infrastructure at the domain level. The block applies to all browsing, not just private windows.
The three-part filter
Singh measures every proposed response against three ad requirements:
- Reach audiences at scale
- Preserve necessary advertising services, including measurement, fraud detection, brand safety and verification
- Protect publisher and advertiser choice of partners
His essay says an industry-built browser fails because consumers would need to switch. Agentic advertising fails because agents negotiate deals but do not deliver the creative or provide device evidence. Replacing the publisher ad server fails because migration costs and workflow requirements are substantial. Singh leans on a US court finding that Google held 91% of publisher ad-server impressions in 2022 to underline switching costs, while calling it historical rather than a current estimate.
Why this matters to marketers
Even if you set aside the fact that the essay promotes its author’s own product, the underlying shift is real. Safari is pushing ad-related calls off the browser and onto first-party infrastructure. If your measurement, identity or creative delivery depends on third-party browser domains, part of your Safari audience may lose verification or disappear.
Trusted Server’s approach is to place a publisher-controlled execution layer at the edge or behind a CDN, so browser requests go to the publisher’s domain instead of a list of outside vendors. That architecture is the right direction for many stacks—but it is not yet a proven standard.
The evidence gap
Singh concedes Trusted Server is “working towards production evidence.” The essay names no publisher using it, no adoption count, no revenue impact and no latency comparison. Its own documentation lists creative-processing limits, meaning a share of programmatic creatives may still load scripts and assets directly from third parties.
That does not kill the server-side argument. It does mean marketers should treat this as a migration signal, not a ready-made switch.
What to do now
Run a tag audit of every third-party domain your site calls from the browser, splitting identity resolution from creative delivery and measurement. Then run a small server-side proof on one format, market or site section before committing. Use Singh’s three-part test as a checklist: reach, services, partner choice.
The server-side direction will outlast any single vendor’s product claim.
Source: PPC Land
