What is an SSP, actually.

01Definition

A supply-side platform, SSP, is the system publishers connect to that auctions their inventory to programmatic demand. It receives ad requests from the publisher's app or site, packages them into bid requests, offers them to demand sources, and returns the winning advertisement to be displayed. The SSP's job, stated plainly, is to get each impression the highest price the market will pay, under the publisher's rules, and to prove it did.

02Where it sits

The chain from impression to money, with each hop:

1. The app or stream. An SDK call on mobile, or server-side ad insertion on CTV, produces an impression the publisher wants to sell.
2. The SSP auction. The impression is packaged with context: app identity, format, geography, consent signals, and on CTV the pod position. This is the bid request.
3. DSPs and networks. Demand-side platforms bid on behalf of advertisers; some networks bid through adapter integrations; direct campaigns compete inside the same auction where the platform supports it.
4. The advertiser. The DSP's bid represents an advertiser's budget and targeting. The advertiser rarely sees the individual impression; they see the campaign.
5. Settlement. The winning bid is logged, the impression served, and revenue attributed back to the publisher through the SSP's reporting.

03What an auction actually does

OpenRTB, in plain language. A bid request is a structured message describing the impression: the app object naming the application, the impression object describing format and sizes, the device object, the user object with consent signals, and the supply chain object tracing who is selling. The SSP sends it to every eligible demand source at once. Each source responds with a bid: a price and the creative that would serve, inside a deadline measured in milliseconds. The SSP validates the bids against floors, policy and deal terms, then the highest valid bid wins, and its creative is returned to the app.

Two things in that paragraph are where SSPs differ. Which sources see the request is a curation decision. Whether every source truly sees the request at the same time is an integrity decision. The second one is worth testing before the first one is worth admiring.

04Key terms

eCPM: revenue per thousand impressions, the comparable price of an inventory slice. Fill rate: the share of requests that returned a billable impression. Win rate: the share of auctions a source won where it responded. Bid density: how many bids an auction actually attracts per impression, which caps everything else. Full definitions live in the glossary.

05SSP versus ad network versus exchange

An ad network aggregates inventory and sells it in packages, historically on its own terms and with its own demand relationships; the publisher sells to the network rather than through an auction. Anexchange is the matching engine: a more neutral marketplace that connects sellers and buyers in real time. An SSP is the publisher-side representative: it packs the exchange mechanics plus yield management, deal logic, mediation and reporting that act on the publisher's behalf.

The demand each brings historically differs too: networks grew on performance demand, install campaigns and direct response, while programmatic access through an SSP opens brand budgets that never bought through network packages. A platform with both, competing in one auction, is the current normal.

In practice the categories blur, and most companies are some of each. The useful question is not which box a partner sits in, but which function it actually performs for you: does it auction every impression at par, does it manage your yield, and can you verify both.

06How publishers evaluate an SSP

The honest checklist, each item checkable rather than askable:

• Auction transparency. Can the SSP show why an impression sold at its price: the competing bids, the floor, the winner? Logged decisions or a shrug.
• Demand diversity. How many distinct demand sources bid, and in how many geos? Bid density per impression is the number to ask for.
• Fee clarity. What is the revenue share, and where in reporting does it appear? A revenue number you cannot reconcile to a payment is a fee structure you cannot audit.
• Reporting. Can you cut by placement, country and demand source, and does it reconcile to the invoice?
• Authorized selling. Does the SSP enforce app-ads.txt on incoming paths and publish its own sellers.json? This one is binary and verifiable in an afternoon.

07CTV specifics

When the supply is a television stream, three things change. Delivery moves server-side: SSAI stitches the ads, so the SSP must integrate with the stitching layer rather than an SDK. Structure matters more: ads trade in pods, and pod position prices differently inside the same break. Measurement is harder: beacons come from the stream, verification depends on platform capability, and no SSP measures uniformly across every TV platform today. TheCTV ecosystem guide covers the landscape, and the CTV monetization page covers ours.