The Zero-Hop Advantage: What SPO Really Rewards

Buyers running supply-path optimization don't grade a publisher's content. They count nodes. Every partner sitting in a request's supply chain object is a hop a buyer can choose to route around — and increasingly, they do, often at the publisher's expense.

The Node Nobody Adds

SPO's mechanics are fairly mechanical: buyers inspect a request's schain object — the record of every seller a bid request has passed through — and prune paths with too many stops. A demand partner working the conventional way, sitting in that chain as its own distinct seller, adds a hop, and stack enough partners on top of each other and the chain gets long enough that SPO-driven buyers start cutting it, usually without the publisher having much say in which hops survive.

There's a structurally different model taking hold: a partner that writes contextual, audience, household, and identity signal directly into a request inside an existing connection, without adding a new node to the chain at all. Same supply, same SSP or DSP relationship, same user experience — the only thing that changes is what the buyer knows when they bid.

The Two Effects Publishers Miss

For buyers, that distinction is invisible in the interface but decisive in the auction. Enrichment without a new node means SPO sees a shorter path, not a longer one, while the request itself carries more information — the buyer gets more to bid on, not more to verify.

For publishers, two effects compound here, and most sell-side pitches only mention one. Publishers consolidating onto clean, signal-rich paths have reported revenue gains in the 10–25% range in SPO industry benchmarking, and in some of the most signal-rich, zero-hop paths, DSPs have been benchmarked by ad-tech research firm Jounce Media bidding close to 2x more per request than into blind, rebroadcast paths. That sits on top of a second, quieter effect: moving from open-market pass-through economics toward curated, zero-hop economics is itself a meaningful recovery of spend that was leaking out before enrichment ever entered the picture. Stack both, and a realistic range for most publishers — before counting any new demand access — lands somewhere around 20–45%, by estimates that combine the two effects. That's a range worth validating against a publisher's own traffic, not one to take as guaranteed.

For the person on the other end of that impression, none of this is visible — which is sort of the point. The page loads the same way, through the same ad stack, with the same experience. The difference shows up only in whether the ad that fills the slot has anything to do with the content sitting next to it.

The Catch

Enrichment without a node isn't a way to dodge scrutiny forever. Buyers running increasingly sophisticated SPO are starting to evaluate not just node count but the quality and verifiability of what's written into a request — meaning a partner that enriches a path still has to prove its signal is real, sourced, and privacy-compliant, not just cheaply added. And the benchmarked revenue ranges are aggregate figures, not guarantees; actual lift depends heavily on how much value a publisher's existing traffic was already leaking through long, unmanaged paths in the first place.

From Counting Hops to Verifying Them

SPO began as a blunt instrument — buyers counting hops and cutting the longest chains. It's maturing into something closer to signal verification, where the question isn't just how many nodes a request passed through but what got attached to it along the way. That shift rewards publishers who can make their inventory more legible to a buyer's auction logic without making it more expensive to reach. The zero-hop model is one answer to that problem — probably not the last one.

LEARN MORE

Loyal, a CTV and mobile publisher and ad tech provider, builds toward exactly this model. Its Path SDK writes contextual, audience, and identity signal into existing waterfall connections without adding a chain node, so SPO-driven buyers see a shorter path that's already carrying more information. More on how that works: