Tech Lab Trusted Server is an open-source initiative providing Publishers on the open web with privacy first control over their monetization that is independent of browser APIs and signal loss.
We are actively seeking Publisher partners to test the prototype and help define the roadmap. Submit here to join the Trusted Server Task Force.
Trusted Server enables publishers to manage ad requests, auction execution, and creative delivery entirely in their own server-side framework—removing reliance on third-party tools that browsers continue to restrict. Key features include:
The Trusted Server roadmap outlines robust support for third-party plugins. This plug-and-play approach facilitates seamless integration with fraud prevention, brand safety, identity solutions, and measurement partners without disrupting existing operations.
Given the privacy related changes made and proposed by top browsers, it is clear that client side ad technology dependent on third party code execution on the client side cannot be sustained as it stands today.
There is a need for a new approach that is resilient to these changes and puts publishers and advertisers in more reliable and predictable control.
The Trusted Server does just that – moves advertising functions to the server side and enables execution of third party functions and code in the context of the publisher’s domain, including
The Trusted Server approach will preserve all critical advertising functions by keeping all entity relationships and reply on fast edge compute infrastructure to improve upon existing benchmarks.
Moving these advertising capabilities from the client to the server seems like a significant undertaking, but it does not need to happen all at once. Our modular approach ensures a smoother transition with steps such as:
Trusted server design ensures a plug and play architecture to enable third party services and plug into the existing programmatic supply chain with least disruption.
Below is a high level architecture diagram of how the different components of the Trusted Server architecture interact. More detailed architecture diagrams can be found in the code repository.
There are 3 phases to the Trusted Server project.
The table below shows some of the expected features and estimated project phase. This will get further updated and refined as the Task Force begins their work and the industry responds and starts testing in real world scenarios.
Project Phase | Goal | Features | Status |
---|---|---|---|
Proof of Concept | Demonstrate capabilities and open up ideas of what is possible with Trusted Server and its core concepts. We will continue to develop features, integrations, and use cases alongside the community | Send Ad Request to an Exchange Receive and process response Stitch the ad into the page Serve the Page and Ad | Ready for Publisher Testing |
MVP for Publishers | Enable Publishers to start running a %age of their inventory through the Trusted Server pipes | Addressability and Privacy Display, Native, Video creative types ID providers, Audience providers Server side tagging | In Progress |
Future enhancements and Releases | Further build out the Trusted Server ecosystem, integrating more partners and features. | Ad Fraud (Signals for ad fraud (IP address, TLS JA3) and plugin for ad fraud providers to execute their code and return result to core service) Brand Safety (Prebid brand safety evaluation by brand safety vendors and return result to core service, send result in bid request) Measurement (Enable server side measurement events redirect by publisher based on client side user actions) Other features prioritized by Task Force | Prioritization and scope to be determined by the Trusted Server Task Force. Sign up today. |
We welcome feedback on the Proof of Concept, MVP definition and other criteria like security, optimization, performance, data storage, prioritize edge cloud versions (Akamai, AWS etc.) and any other essential publisher side function which we may have missed in the roadmap above by joining the Trusted Server Task Force.