Demand path optimization
Demand path optimization (DPO) is the sell-side counterpart to supply path optimization. Publishers and SSPs assess which demand sources and routes deliver the best net yield, quality and reliability, then prioritise those paths and reduce ones that add cost, latency or risk without adding value.
What is demand path optimization?
Demand path optimization, or DPO, looks at the programmatic chain from the seller’s side. Where buyers use SPO to choose efficient supply routes, publishers and SSPs use DPO to judge which demand partners, buyers and routes deserve their impressions. It considers net revenue after fees, bid density, latency, ad quality and payment reliability. DPO is closely related to Yield optimization and often shapes a publisher’s Header bidding setup. SSPs also apply a form of DPO, sometimes called traffic shaping, to send bid requests only to DSPs likely to respond.
How demand path optimization works
Publishers analyse bid data by SSP, DSP and buyer to see who bids, how often, at what prices and with what fees. They streamline their stack by keeping partners that bring unique, well-paying demand and removing those that duplicate others. SSPs may also tune which DSPs receive which requests to cut wasted traffic.
- The publisher gathers bid, win, revenue and latency data for each demand partner.
- Partners are compared on net yield, unique demand contribution, quality and reliability.
- Low-value or redundant partners are removed or given a reduced role.
- Floors, timeouts and partner settings are tuned for the streamlined setup.
- Results are monitored to confirm revenue holds or improves after changes.
Why it matters
Too many demand partners add page latency and operational overhead without necessarily raising revenue. DPO helps publishers keep the partners that genuinely contribute to yield and user experience.
For publishers
DPO helps publishers balance revenue against page speed and operational effort by keeping demand partners that add real value.
For adtech platforms
SSPs use demand-side traffic shaping to cut infrastructure costs and send buyers more relevant requests.
Practical example
A recipe website reviews six months of bid data, finds two SSPs rarely win and mostly duplicate other bids, and removes them to speed up page loads.
Key considerations
- Removing a partner can remove unique buyers, so test changes before cutting widely.
- Gross bid prices can mislead; compare partners on net revenue after fees.
- Traffic shaping by SSPs should not hide inventory from buyers who would value it.
More Publisher Monetization terms
Frequently asked questions
How is DPO different from SPO?
SPO is the buyer choosing efficient routes to supply; DPO is the seller choosing which demand partners and routes deliver the best net outcome.
Does DPO mean fewer demand partners?
Often, but not always. The goal is the right mix of partners, which may mean adding a partner that brings unique demand as well as removing others.
What is traffic shaping?
Traffic shaping is when an SSP filters which bid requests it sends to each DSP, based on the likelihood of a response, to reduce wasted processing.