What is supply path optimization?

Header bidding let publishers offer the same ad slot through many SSPs at once. Buyers gained choice. They also started seeing the same publisher several times in one auction, each copy carrying a different fee, a different delay, and a different story about who sold it.

Supply path optimization (SPO) is the practice of picking the efficient routes and turning the rest down. It is a buying decision and a selling discipline. A DSP that ignores it wastes queries. An SSP that ignores it gets dropped even when the underlying publisher is good.

What “the same impression” means

One person loads one page. The publisher calls three exchanges. Each exchange may also forward the request to a reseller. The DSP receives several bid requests for one slot. If it bids on all of them, it can bid against itself. The publisher still shows one ad. The extra requests only added cost and confusion.

SPO asks which of those requests is the best representative of that slot, then bids there.

What buyers actually compare

• Directness. Fewer paid hops. A DIRECT ads.txt relationship is a stronger signal than a long reseller chain.
• Identity of every hop. schain nodes that resolve in sellers.json. Unknown intermediaries are a reason to skip the path, not a mystery to price later.
• Take rate. How much of the clearing price is left after each company is paid. A cheap bid on an expensive path can be a worse deal than a higher bid on a short path.
• Duplicates. The same publisher, placement, and user offered again through another seat.
• Performance. Win rate, viewability, invalid-traffic rate, and downstream conversions on that path, not just the lowest CPM.
• Latency. A path that answers too late does not get a chance to win, so it should not consume the buyer’s QPS either.

The files behind those checks are covered in ads.txt, sellers.json, and schain.

What SPO is not

SPO is not “buy only one SSP worldwide.” A publisher’s best path in one country can be a poor path in another. It is also not the same thing as moving an entire budget into private marketplaces. Private deals can still be duplicated across exchanges. The path question remains.

Early SPO programs cut partners until the spreadsheet looked tidy, then discovered they had also cut unique reach. A useful program keeps a path when it adds publishers or performance the shorter paths do not have.

What an SSP should do

• Send one request per impression to a given DSP, not the same chance reshuffled through reseller seats.
• Populate a complete schain and a stable publisher ID.
• Drop traffic you cannot describe: missing app identifiers, broken ads.txt, or placements the DSP has already said it will not buy.
• Make fees predictable. Buyers optimize paths they can explain to a client.

Publishers feel SPO as a change in which SSP wins, not as a setting in their ad server. If revenue concentrates on one or two partners, those partners are probably the paths buyers chose. Adding more resellers rarely reverses that.

A simple way to start

1. List the SSPs that deliver each priority publisher.
2. Mark which lines are DIRECT, and how many schain hops sit in front of them.
3. Compare win rate, viewability, and effective CPM after fees, not the gross bid.
4. Keep the paths that are unique or better. Suppress the copies.
5. Review quarterly. A path that was direct in January can pick up a reseller by June.

FAQ

Is SPO only for open-auction buys?

No. Deal ID campaigns can arrive through more than one exchange. Buyers still choose which pipe should carry the deal.

Does a short path guarantee quality?

It guarantees less room to hide. Viewability, invalid traffic, and audience fit are separate tests.

How is this different from curated supply?

SPO chooses routes to inventory you already see. Curation builds a defined pool before the request shows up. Many buyers do both.

← All posts · What is SPO? · ads.txt and schain · Demand partners