DEV Community

Aleksander Sekowski
Aleksander Sekowski

Posted on

Trusted Server Explained: How Edge OpenRTB Assembles user.id, eids, and tmax

In early November 2026, Digiday reported that publishers are racing toward server-side auctions after Safari began blocking identity resolution hosts. IAB Tech Lab's Trusted Server is the stack name in those conversations, but the operational question is narrower: what JSON actually leaves the edge toward Prebid Server and your SSP adapters? It is not a copy of what Prebid.js would have posted from the browser. The edge runtime assembles OpenRTB from first-party cookies, merged EIDs, consent gates, and provider timeouts that live on a different clock than pbjs.setConfig({ bidderTimeout }).

That distinction matters twice this month. Safari thinned what browser sync can put on user.eids, which we mapped in Safari 27 thins user.eids. Separately, Google's proposed antitrust remedies would route AdX demand through Prebid-shaped auctions, which only works if the OpenRTB object Prebid Server receives is the one buyers price, not a cousin object with different identity and timeout semantics. Our Google remedies and Prebid Server bid request note sits on that second pressure.

If you sell header bidding, you already know the browser path: Prebid.js collects consent, runs user ID modules, builds ad units, and forwards a request. Trusted Server keeps the page on publisher origin while a CDN or edge worker orchestrates providers. The Prebid integration guide describes injection of an EC id, OpenRTB 2.6 conversion, and a downstream call to /openrtb2/auction. The object that arrives at the bidder is assembled there, not replayed from DevTools.

Identity: ts-ec on user.id, partners on user.ext.eids

Trusted Server's edge cookie is ts-ec. When forwarding is allowed, that first-party value is written to OpenRTB user.id, not tucked only inside a custom extension. Partner identifiers collected in the browser and partner identifiers already associated with the edge cookie on prior visits are merged, deduplicated, and sent downstream as user.ext.eids.

OpenRTB 2.6 also defines a first-class user.eids array. The current Trusted Server Prebid guides document user.id and user.ext.eids explicitly. They do not promise that the edge copies user.ext.eids onto user.eids before Prebid Server forwards the payload. A buyer filter written for user.eids (common on stacks that never adopted the 2.6 field split) can no-bid a request that is fully addressed on user.id and user.ext.eids. The same auction looks anonymous to a rule that was written for browser Prebid, where modules often populated user.eids directly.

device.ifa is a second false friend on web inventory. An edge auction for Safari still has a device object with UA and OS, but it does not magically gain an IFA. Filters that require device.ifa for "addressable" web inventory will reject edge-built requests even when user.id carries a stable publisher minted id. Field-level docs for the user object live on OpenRTB user.

{
  "user": {
    "id": "<ts-ec when forwarding is allowed>",
    "ext": {
      "eids": [
        {
          "source": "id5-sync.com",
          "uids": [{ "id": "ID5-example", "atype": 1 }]
        }
      ]
    }
  }
}
Enter fullscreen mode Exit fullscreen mode

The snippet is one shape the guides describe; your deployer's consent gate can empty ext.eids while still setting user.id. Ops should diff identity on the wire, not on the dashboard impression count.

Time: page timeout, provider budget, and tmax

A second assembly step that breaks buyer filters is time. Trusted Server's Prebid integration treats [integrations.prebid].timeout_ms as the browser auction timeout only. Server-side orchestration uses an auction-level timeout_ms and per-provider timeouts (for example the prebid-server provider). The OpenRTB tmax that Prebid Server sees is capped by the remaining server auction budget, not by whatever timeout the page printed in its console logs.

Teams that copy the page's 1500 ms straight into tmax believe they preserved latency tolerance. They actually told downstream bidders they have less time than the orchestrator grants the provider stack, or more time than the server will wait, depending on which number they pasted. Both directions produce silent bid loss: timeouts on the buyer, or incomplete auctions logged as "no demand" on the seller side. Compare OpenRTB 2.5 versus 2.6 if your exchange still keys validation on an older dated snapshot while the edge emits 2.6-shaped video and banner imps.

Identity sync adds a third clock that never moved server-side. LiveRamp IdentityLink with notUse3P: false is still a browser call to third-party hosts. Trusted Server does not proxy that hop. Safari can block the call before the edge receives an EID to merge, which leaves you with user.id populated and an empty partner set. That is not a tmax bug; it is a network path that never entered the server budget math.

Supply chain and the browser comparison

source.fd often flips when the auction initiator moves from client to server. Buyer analytics keyed on fd: 0 may bucket edge inventory separately even when the slot is the same ad unit id. Supply chain completeness is equally sensitive: an edge proxy that assembles source.ext.schain without the hop a browser-loaded wrapper would have inserted can trip schain.complete checks. The OpenRTB supply chain field reference and schain node docs are the checklists those filters encode. Our supply chain trust stack guide walks the ads.txt and schain join buyers expect next to the JSON.

For a side-by-side of why the edge object is not the browser object, start with edge OpenRTB versus the browser Prebid request on rtblint.org. It is the canonical diff for ops teams onboarding Trusted Server beside existing Prebid.js, and it matches what we see when sellers compare Safari volume to DSP logs.

How you catch it

An LLM or codegen tool can emit a plausible OpenRTB request for "Trusted Server plus Prebid Server" and still get an OK from a loose JSON schema. Buyer filters and exchange validators are stricter: they care whether user.eids is empty while user.ext.eids is not, whether tmax matches the server clock, and whether schain nodes match ads.txt authorization.

RTBlint is the deterministic check for that assembled object (cargo install rtblint, npm install rtblint-core, or the MCP server). It validates the OpenRTB payload against dated snapshots and supply-chain rules independent of what your edge config UI claims. It is not an IAB Tech Lab or AAO product, and the Trusted Server repo does not replace a bid-request lint pass on the bytes your SSP actually received.

Pipe a captured edge auction JSON through rtblint validate in CI beside your Trusted Server config tests. Config validation proves YAML loads; it does not prove the downstream OpenRTB matches what buyers wrote filters against. When you are teaching a new hire the spec grammar first, how to read the OpenRTB spec pairs well with edge debugging.

Where to go next

Trusted Server is a deployment model, not a guarantee that buyers accept the identity and timeout story your edge emits. Assemble the object deliberately, then lint the object buyers price.

Top comments (0)