Tim Peterson asks whether web users can trust ad tech’s server-side shift

Tim Peterson asks whether web users can trust ad tech’s server-side shift

Digiday’s Tim Peterson examines a privacy trade-off in ad tech’s move from browser-based calls to server-side calls, which run through a publisher’s server. The shift can give publishers more control over which partners receive data, says Rowena Lam of IAB Tech Lab, but it also makes those calls less visible to users’ browsers. A key example is Trusted Server’s edge cookie, a server-side identifier created in part by hashing a user’s IP address with a domain-specific secret key. Peterson describes how a returning user on the same IP address could receive a new edge cookie matched to the earlier one, potentially undoing the effect of clearing browser cookies. Lam says publishers choose whether to send the edge cookie to downstream vendors; it is not automatically passed on. She also says Trusted Server supports integration with consent management platforms and includes logging and auditing. The article’s central concern is that these safeguards depend on publishers configuring and using the system responsibly, while users cannot inspect server-side calls through their browsers. Peterson presents greater publisher control as a possible privacy advantage, not a guarantee: the same shift can reduce user visibility, leaving trust in the publisher central.

Publication: 3113e236-2603-4be9-8df7-05a08c180c72

attribution — pass: The draft attributes the article and its framing to Digiday's Tim Peterson. It attributes the claims about publisher control, non-automatic edge cookie sharing, consent management integration, and logging and auditing to Rowena Lam of IAB Tech Lab. The source supports this split. Lam's statements are not presented as established fact.

Nobody downstream would automatically receive an edge cookie,” Lam said.

summary — pass: The summary faithfully conveys the trade-off. Server-side calls give publishers more control but are less visible to browsers, and the edge cookie can undo cookie clearing. It also covers Lam's rebuttals and Peterson's point that safeguards rely on trusting the publisher. Server-side calls and the edge cookie are explained in plain terms. One minor point: the draft omits Lam's stronger claim that going server-side is more privacy-preserving in general and the Apple crackdown context. Neither omission distorts the meaning. The question follows from the evidence.

But of course, that requires the user blindly trusting the site to do so.

date — pass: The originalPublished date of 2026-11-10 matches the article byline dated November 10, 2026, and the feed entry date.

By Tim Peterson • November 10, 2026

support — pass: Each claim's excerpt appears verbatim in the source and supports the claim. The edge cookie condition (same IP address and same secret key) is preserved. The interpretive claim that publisher control is presented as a possible advantage alongside reduced visibility is reasonably grounded: Peterson notes the control benefit, and Lam argues it directly. The limitation correctly notes there are no deployment measurements. The draft does not convert announcements into demonstrated benefits.

Taking ad calls out of the browser, however, has the effect of taking them out of users’ sights.

media — pass: The selected media is the verified direct link to the original Digiday article. This is the most direct way for readers to access the source.