← Back to blog
W

What Is an SSP (Supply-Side Platform)?

A supply-side platform (SSP) is software that publishers use to make their advertising inventory available to buyers in an automated, programmatic way. Where a demand-side platform (DSP) serves the advertiser’s interests, an SSP serves the publisher, helping them reach more buyers, increase competition for their inventory, and ultimately maximize revenue.

What problem does an SSP solve?

Before SSPs, publishers sold their inventory in two main ways: directly to advertisers through sales teams, or through ad networks that aggregated unsold inventory at discounted rates. Both approaches had limits. Direct sales required significant headcount and left residual inventory unsold. Ad networks offered little transparency and often priced inventory below its potential value.

An SSP changes this by exposing a publisher’s available impressions to a wide range of demand sources simultaneously (including ad exchanges, DSPs, trading desks, and ad networks) and letting those sources compete in real-time auctions for each impression.

Core functions of an SSP

Inventory management

Publishers configure their ad slots in the SSP: sizes, formats, placements, and any rules about which types of ads are allowed. Floor prices, the minimum CPM a publisher will accept, can be set globally or by audience segment, geography, device type, or ad unit.

Yield optimization

An SSP dynamically routes each impression to the demand source most likely to pay the highest price for it. This may involve header bidding (running simultaneous auctions across multiple buyers before the page ad server makes a final decision) or waterfall logic (sequential calls to demand sources in priority order).

Audience data packaging

SSPs often allow publishers to attach audience data to bid requests (age, interest categories, purchase intent signals) so that buyers can better assess the value of each impression and bid accordingly.

Brand safety controls

Publishers use the SSP to block categories of advertisers (competitors, sensitive sectors), specific domains, or content types that conflict with their editorial standards or advertiser relationships.

How an SSP connects to the rest of the ecosystem

When a user loads a page on a publisher’s website, the sequence typically unfolds as follows:

  1. The publisher’s ad server (or header bidding wrapper) calls the SSP.
  2. The SSP packages information about the impression (the ad slot, page context, and any available audience data) into a bid request.
  3. The bid request is sent simultaneously to connected DSPs and ad exchanges.
  4. Buyers evaluate the request and respond with bids.
  5. The SSP selects the highest eligible bid, sends it back to the publisher’s ad server, and the winning ad is rendered.
  6. The SSP logs the transaction and updates reporting dashboards.

This happens before the page finishes loading, typically within 200-300 milliseconds.

Header bidding and the evolution of SSPs

Header bidding emerged as a way to give publishers more control and increase auction competition. Rather than calling one demand source at a time in a waterfall, header bidding calls multiple SSPs and DSPs simultaneously, outside the ad server’s normal priority logic. The highest bid from any participating platform wins.

Most publishers today use header bidding through a wrapper (a JavaScript tag in the page header that manages the parallel auctions), often working with multiple SSPs at once to maximize demand coverage.

What publishers look for in an SSP

When choosing an SSP, publishers typically evaluate:

  • Demand breadth: how many DSPs, trading desks, and direct buyers are connected
  • Yield analytics: reporting that shows how different demand sources perform, and where revenue can be improved
  • Floor price management: tools for setting and testing CPM floors dynamically
  • Latency: how quickly the SSP responds to bid requests, since slow responses hurt auction outcomes
  • Brand safety tools: category blocking, domain blocking, ad quality filters
  • Integration: compatibility with the publisher’s existing ad server and header bidding setup

SSPs and programmatic direct

Beyond open auction, SSPs also facilitate programmatic direct deals: private marketplaces (PMPs) and programmatic guaranteed (PG) contracts. These give publishers more control over who buys their inventory and at what price, while still automating the delivery and reporting workflow.

How Arago helps

As a DSP, Arago connects to premium SSPs and exchanges on behalf of local retail advertisers, accessing publisher inventory across display, video, connected TV, and digital out-of-home. Understanding how SSPs work helps retailers appreciate how their campaigns reach audiences across the open web, and why inventory quality and supply-path transparency matter.