What is SSP consolidation, and how do buyers do it safely?
Part of Supply path transparency
The short answer
SSP consolidation is a buyer's decision to route programmatic spend through fewer supply-side platforms. The aim is fewer repeated offers of the same impression and more spend on paths that are authorized, direct and visible in the bid request. Done well, it starts from the publishers on the plan and keeps at least one authorized route to each.
Key takeaways
- SSP consolidation trims the supply partners a buyer bids through, not the publishers it wants to reach.
- The ANA's 2024 benchmark found participating marketers used slightly more than 19 SSPs on average, the 2023 level, and saw significant room for further optimization.
- Choose paths from public records: the publisher's ads.txt, the exchange's sellers.json and the SupplyChain object in the bid request.
- Before removing an SSP, check whether any publisher on the plan is sold only through it.
- Measure the change by publisher coverage, path length and delivery against a baseline taken before the cut.
What is SSP consolidation?
Definition
- SSP consolidation
- Reducing the number of supply-side platforms a buyer bids through, so that each publisher the buyer wants is reached by fewer and clearer routes.
A supply-side platform sells a publisher's ad space to buyers. One page view can reach a buyer through several of them. IAB Tech Lab's Programmatic Auction Definitions (opens in a new tab) describe request initiators that call selling platforms, and note that "each selling platform may call (n) additional selling platforms in a single ad request initiation." A buyer connected to several exchanges can therefore see one opportunity arrive more than once, with different intermediaries attached.
Consolidation is the buyer's response: pick fewer routes to the same supply. It is one possible outcome of a supply path optimization review, not the review itself.
It remains that any participant in the ecosystem is free to choose their partners; the aim is the reduction of redundant requests by ensuring that requests are sent to each partner only once per underlying ad opportunity, per integration mechanism or inventory partner domain.
The same draft, written by Tech Lab's Programmatic Governance Council, adds that "companies are encouraged to clearly define and understand the business value of each integration partner." The document was still labeled public comment, not final, when checked on October 22, 2026.
How many SSPs do advertisers use?
The best public reference is the ANA's benchmark, run with TAG TrustNet on the log data of participating marketers. Its December 12, 2024 release (opens in a new tab), the latest public release to give an SSP count, says "The average number of SSPs used is slightly above the 2023 level of 19," and adds that this indicates "there is significant room for further optimization." It describes benchmark participants, not the whole market.
| Measure | What it tells a buyer | What it misses |
|---|---|---|
| SSPs connected to the DSP seat | How many integrations and contracts the team manages | Whether each wanted publisher is reachable, and through how many routes |
| Routes per publisher | How many authorized ways exist to buy one site | Which route carries fewer intermediaries or better terms |
| Share of spend on confirmed direct paths | How much money reaches the publisher's own seller account | Whether a reseller path was the only way to reach a small site |
| Average nodes in the SupplyChain object | How many intermediaries handled the requests that were bought | Fees, which sit in contracts and logs, not in the chain |
How do you choose which paths to keep without ranking vendors?
Start from the publishers, not the SSP contracts. What a path connects and how cleanly it is declared sit in public files. The ads.txt 1.1 specification (opens in a new tab) lets content owners "declare who is authorized to sell their inventory." The sellers.json specification (opens in a new tab) lets buyers "discover who the entities are that are either direct sellers of or intermediaries in the selling of digital advertising." The SupplyChain object (opens in a new tab) "enables buyers to see all parties who are selling or reselling a given bid request."
A publisher first method for choosing paths
- List the publishers first. Take the approved site list for the brief, not the list of SSPs enabled in the buying seat.
- Read each site's ads.txt. Note each advertising system, account ID and relationship. DIRECT means the publisher "directly controls the account"; RESELLER means it "has authorized another entity to control the account."
- Match each account in sellers.json. Confirm the seller ID exists in that exchange's file and read seller_type: PUBLISHER means the named entity owns the medium and is paid directly.
- Check real requests. In bid logs, confirm that the SupplyChain nodes name the same advertising system and seller ID, and that the complete flag is 1.
- Build a coverage table. Put publishers in rows and paths in columns. Mark any path that is the only authorized route to a site.
- Keep the smallest set that covers the list. Remove a path only when each site it reaches has another authorized, confirmed route.
Some reasons to keep a route are practical: a plan with connected TV placements needs a route that carries them, and a private marketplace deal needs the SSP where it lives. Record those reasons in the coverage table.
Can consolidation cut off independent publishers?
Yes. A small publisher may list only one or two advertising systems in its ads.txt file, sometimes through a sales house that represents several local sites. If the buyer turns off the SSP behind that line, the site stays on the plan but stops delivering, and only the domain report shows it.
Buying platform defaults make this easy to miss. Display & Video 360's inventory source help page (opens in a new tab) says that without inventory source targeting, "your line item will target open auction inventory on all enabled exchanges by default." Narrowing the enabled exchanges therefore narrows each line item that relies on the default. The same page answers whether exchange exclusions reach deals: "No. Public inventory controls are completely separate from private deals." Review exchange settings and deals as two lists.
A RESELLER line is not a reason to drop a site. The publisher authorized that entity to sell for it. ads.txt 1.1 also defines MANAGERDOMAIN, which "Specifies the business domain of a primary or exclusive monetization partner of the publishers inventory." A local news site whose sales are run by such a partner may have no direct route at all. The fair publisher planning hub covers why small sites deserve the extra check.
Before removing an SSP from a plan
- Each site the SSP reaches has at least one other authorized route in its ads.txt file.
- That other route is confirmed in the exchange's sellers.json file.
- Sites sold only through a reseller or a MANAGERDOMAIN partner have been reviewed one by one.
- Deals that run on the SSP are listed separately, because exchange settings do not control deals.
- Video, connected TV or app placements on the plan still have a route that carries them.
- The publishers affected by the change are named in the plan notes for the client.
How do you measure the effect of consolidation?
Take a baseline before changing anything, over a flight of the same length and season, then compare the same measures after. Other things change between two periods too, so treat the comparison as evidence to discuss, not as proof that the cut caused the change.
The buying platform is the main data source. The MRC's January 2026 Digital Advertising Auction Transparency Standards (opens in a new tab) require DSPs to validate seller IDs in ads.txt against sellers.json, to ensure the chain ends at the owner of the inventory, and to "Provide buyers with fully transparent reporting on the average number of nodes (also known as hops) and mis- or undeclared supply chains." Where it is missing, log level data can produce the same counts.
| Measure | Where it comes from | What to look for after the change |
|---|---|---|
| Publishers on the plan that delivered | DSP domain or app report | The same publishers still delivering, with any loss explained |
| Bid requests received per impression won | DSP bid logs | Fewer requests for the same delivery, a sign of fewer repeated offers |
| Average nodes per chain | DSP supply chain reporting or schain fields in logs | Shorter or stable chains |
| Spend through confirmed direct paths | Logs matched to ads.txt and sellers.json | A stable or larger share |
| Undeclared or unauthorized chains | DSP supply chain reporting | Fewer, ideally none |
Fee questions belong to the contract and the logs, which the ad tech tax guide covers.
What does SSP consolidation look like on a real plan?
Fictional example
A jazz concert series trims its supply paths in upstate New York
An agency plans ads for an unnamed jazz concert series selling season passes in Rochester, Syracuse and Albany. The approved list holds 60 English language sites: arts and culture magazines, entertainment listings, college radio sites and local news. The buying seat has a long list of exchanges enabled, and the planner wants to know which ones the list needs.
The coverage table shows that four exchanges carry DIRECT, confirmed paths to almost the whole list. Two small arts magazines list only one advertising system each, as RESELLER, through a regional sales house named in their MANAGERDOMAIN lines, and that exchange is not among the four. One college radio site has no ads.txt file, so it has no declared route to keep or drop.
The planner keeps the four exchanges for open auction line items and reaches the two magazines through a deal on the fifth exchange. The college radio site goes into the plan notes as unreachable until its file appears. Before launch, the team saves a baseline of delivering domains and chain length.
How does PlacementGraph show the selling paths before a consolidation?
Frequently asked questions
Does SSP consolidation lower prices?
No public source opened for this page isolates the price effect of buying through fewer SSPs. IAB Tech Lab's 2026 draft frames the gain as fewer redundant requests and lower processing costs across the supply chain. Treat price as one measure against a baseline, not a promised result.
Do private marketplace deals count toward the SSP total?
Count them separately. A deal lives on one exchange, and Display & Video 360 says public inventory controls are completely separate from private deals. A buyer can turn an exchange off for open auction buying and still run a deal there to keep a single publisher reachable.
Can a publisher ask a buyer to add a path back?
Yes. The publisher can point to its ads.txt line and the matching sellers.json entry for the exchange it uses. If both confirm the account, the buyer can enable that route for the site alone, for example through a deal, without reopening the exchange for the whole plan.
Should the publisher's own seller account always be the path kept?
It is a strong candidate, since a DIRECT line matched to a PUBLISHER entry means the site controls and is paid for the account. It is not the only valid choice. A site run by a monetization partner named in MANAGERDOMAIN may sell mainly through that partner, and dropping it would drop the site.
Sources
- Programmatic Benchmark release, December 2024 (opens in a new tab)Association of National Advertisers
- Programmatic Best Practices version 1.0 (public comment, September 16, 2026) (opens in a new tab)IAB Tech Lab
- Programmatic Auction Definitions (opens in a new tab)IAB Tech Lab
- ads.txt specification version 1.1 (opens in a new tab)IAB Tech Lab
- sellers.json specification (opens in a new tab)IAB Tech Lab
- SupplyChain object specification (opens in a new tab)IAB Tech Lab
- Inventory source targeting (opens in a new tab)Google Display & Video 360 Help
- Digital Advertising Auction Transparency Standards (January 2026) (opens in a new tab)Media Rating Council
Researched and written by PlacementGraph Research. Read how we research, source and update these pages. Corrections: diana@placementgraph.com.