Apple’s Private browsing and the only practical path for advertising

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.

It rests on three core advertising requirements: 

  • Grow and reach audiences at scale.
  • Preserve necessary advertising services. 
  • Protect publisher and advertiser choice of partners.

Ever since Apple announced the browser restrictions in iIOS and Mac 27, I have seen multiple plausible solutions being proposed. One is a moonshot idea for the industry to develop its own browser. And the second is a first party publisher model powered by, hold your breath, ‘Agentic’. 

A new browser depends on consumers changing their habits. Agentic advertising automates commercial tasks. A first-party-only model assumes publishers can replace capabilities they currently get from specialist providers.

None of these proposals, by itself, meets all three requirements.

Apple’s version 27 release blocks network access to identity-resolution infrastructure. Its earlier Private Browsing 2.0 article describes broader protections against trackers, cloaking and fingerprinting. Together, these publications show a sustained direction that the industry must address. 

Publishers need a sustainable architecture for that direction. They cannot base their future on each browser restriction remaining narrow.

A new browser does not solve today’s publisher problem

An industry browser needs consumers to install it, trust it and use it regularly. Until that happens, publishers still depend on the browsers their audiences already use.

Consumer adoption is an uncertain distribution strategy. Publishers need an infrastructure response they can deploy across their existing traffic.

Agentic buying leaves the delivery problem

Agents can negotiate deals, process instructions and reduce operational work. These capabilities do not determine how an advertisement reaches the browser.

The browser still renders the creative. Measurement still needs device evidence. Addressability, fraud detection, brand safety and independent verification still need technical support.

The agentic proposals acknowledge that the advertisement remains on the device. Its resilience depends on the publisher’s own ad serving and first-party audiences. Agent negotiation alone does not provide that resilience.

Publishers also need access to partners whose capabilities they cannot economically reproduce. 

Advertisers need independent evidence about delivery and quality.

A complete response must support these relationships.

Replacing the ad server is a major undertaking

A publisher-controlled endpoint does not mean every publisher must develop an ad server. But proposals that depend on replacement ad servers face a substantial burden.

I have personally led, not one but two ad server migrations in my past life, both involuntary, and can attest that it’s not a decision to be taken lightly.

An ad server must do much more than return a creative.

Mature platforms support inventory forecasts, campaign delivery, guaranteed commitments, programmatic transactions, reporting and multiple formats. Google’s documentation alone shows extensive capabilities across video delivery, forecasting, creative formats and platform support. 

The market evidence shows the scale of the transition.

The April 2025 court opinion reported Google’s 2022 worldwide share at 91% of publisher ad-server impressions for open-web display advertising. It also identified high entry barriers and substantial switching costs. These are historical findings, not a current market-share estimate. 

The court also attributed Google’s position to anticompetitive conduct. Market share alone does not prove technical superiority.

But the practical consequence remains: a replacement must support publishers’ established workflows, integrations and demand access.

A new platform needs evidence of that capability. An agent interface or a demonstration of ad delivery does not establish near-term operational parity.

For publishers, migration costs and revenue risks form part of the economics. A proposal that ignores them leaves the business case incomplete.

Trusted Server offers a shared migration path

Trusted Server places a publisher-controlled execution layer at the edge or behind the publisher’s CDN. It supports server-side auctions, creative processing and first-party delivery paths. 

This approach lets the industry adapt existing infrastructure through integrations. It avoids the assumption that publishers must replace their complete advertising stack.

Its open-source foundation gives publishers and specialist providers a shared system to develop. Partner choice remains part of the architecture.

Agents can negotiate transactions through this infrastructure. Ad servers can contribute established capabilities. Measurement and verification providers can develop supported methods that preserve independent evidence.

That is the business case: preserve necessary relationships while reducing dependence on third-party browser connections.

The industry must complete the architecture

Trusted Server is working towards production evidence across integrations, formats, measurement and publisher economics by partnering with publishers. Its documentation identifies browser components and creative-processing limits that deployments must address. 

First-party routing also does not make cross-site identity resolution first-party. Publishers must control downstream data use as well as the browser connection.

No architecture can promise immunity from future browser changes.

The industry can, however, choose a foundation that gives publishers more control and supports continued adaptation.

Of the proposals discussed here, Trusted Server offers that practical foundation. This approach lets the industry migrate using existing rails and infrastructure with direct integrations and zero client side changes to header bidding configurations. It certainly avoids the assumption that publishers must replace their complete advertising stack

The industry priority must be to rally behind a practical solution and prove it across the services publishers need.

Shailley Singh Headshot

Shailley Singh
COO and EVP, Product
IAB Tech Lab