What an SSP actually does for app and CTV publishers
A plain-English walk through a single ad request, from the moment an app asks for an ad to the moment one appears, and what a supply-side platform does at every step.
“Supply-side platform” is one of those terms everyone in advertising uses and few people define. If you run an app or a streaming service, it is worth knowing exactly what an SSP does for you, because it sits between your audience and your revenue.
The short version
A supply-side platform (SSP) helps publishers sell advertising space programmatically. It takes each opportunity to show an ad, offers it to many potential buyers at once, runs an auction and returns the winning ad, usually in a fraction of a second.
Its counterpart on the buy side is the demand-side platform (DSP), which advertisers and agencies use to decide which opportunities to bid on and how much to pay. An ad exchange is the marketplace where those bids meet; in practice, many SSPs operate their own exchange.
Following one ad request
The easiest way to understand an SSP is to follow a single impression.
A slot opens. A user reaches a natural break in your app, or a CTV stream reaches an ad break. Your app, SDK or ad server knows an ad can be shown and what kind: a banner, an interstitial, a video, or a pod of several video ads.
The SSP receives the opportunity. Depending on your integration, this arrives as an OpenRTB request from your server, a VAST tag call from a video player, or a call from an SDK inside your app. It describes the placement, the format, the app and the device, along with any privacy signals that apply.
The SSP asks buyers. It turns the opportunity into bid requests and sends them to connected demand partners, usually DSPs and other exchanges, in the OpenRTB format. Each buyer has a short window to respond, usually a few hundred milliseconds at most.
The auction runs. The SSP compares the bids against your floor price and its auction rules and picks a winner. Most programmatic auctions today are first-price: the winner pays what it bid.
The ad is delivered. The winning creative goes back to your app or player. For video and CTV this is a VAST document describing the media files and the tracking that fires as the ad plays.
Everything is recorded. Impressions, clicks, video quartiles and errors flow back into reporting, so both sides can reconcile what was bought and sold.
What a good SSP adds on top
Running auctions is the baseline. The differences between SSPs show up in what they do around the auction.
Demand access
An SSP is only as valuable as the buyers it can reach. Ask which DSPs and exchanges are connected, for which formats, and in which regions. CTV demand, in particular, can be very different from mobile demand.
Integrations that fit your stack
Mobile and CTV publishers rarely have identical setups. Some run their own ad server and prefer a server-to-server OpenRTB connection. Video-first publishers often want a VAST tag they can drop into a player or an ad server. App developers may prefer an SDK. A good SSP meets you where you are.
Yield tools
Floors protect the value of your inventory; set them too high and you lose fill, too low and you leave money on the table. Look for dynamic floors that adapt per impression rather than a single number per placement.
Transparency
Buyers increasingly check every request. They read your app-ads.txt file to confirm who is authorized to sell your inventory, look the seller up in the SSP’s sellers.json, and follow the SupplyChain object to see every hop. An SSP should make this easy and keep its own files clean. (Here is how those pieces fit together.)
Quality and privacy
Invalid traffic, spoofed apps and mismatched device signals hurt everyone’s prices. A good SSP filters what it can before buyers see it, passes the privacy signals that come with a request (consent strings, opt-out flags, child-directed flags) and respects them.
Reporting you can act on
Look for revenue, fill rate, win rate and eCPM by placement, format, country and buyer. Good reporting explains what changed, not just that something did.
CTV is not just bigger mobile
Connected TV adds its own complexity. Ads often run in pods, several ads in one break, so an SSP needs to understand pod structure, creative durations and competitive separation. Many CTV ads are stitched into the stream by a server (server-side ad insertion), which changes how device information reaches buyers. And app identification works through each TV platform’s app store rather than a website domain. We cover pods in more detail in our OpenRTB 2.6 notes.
Choosing well
The right SSP for an app or CTV publisher is the one that brings real demand for your formats, connects the way your stack already works, protects your floors, shows its supply path openly and reports in a way that helps you decide. If you want to see how ManaForge handles each of these, request a demo.
Three small files and one object in the bid request let a buyer trace an impression from the app to every company that touched it. Here is how they fit together, and how to keep yours clean.
OpenRTB 2.6 gave connected TV the vocabulary it was missing: ad pods, exact creative durations, prices per second and better content signals. A field-by-field guide for sellers and buyers.
The average internet user expects instant access to infinite premium, ad-free content. Few realize that ads are the structural framework holding the OpenWeb together. Without them, the free internet would quickly fragment into a series of paywalls and walled gardens.
Read the article ↗
Strike while it’s hot.
Share your inventory and what you want to achieve. Let’s find where Arcaneflow fits.