Programmatic Advertising & Monetization Insights

TL;DR: Ad mediation is a management layer — usually an SDK — that lets a publisher run multiple demand sources (ad networks, exchanges, DSPs) for the same ad slot and automatically serve whichever one pays the most. It is not a demand source itself; it's the traffic controller sitting on top of them. An ad network aggregates and resells inventory from many publishers to advertisers. A DSP is the buy-side tool advertisers use to bid on impressions across exchanges. An SSP is the sell-side tool publishers use to make inventory available to those buyers programmatically. Mediation platforms typically sit above all three, calling them either in a waterfall (sequential, ranked by historical eCPM) or via in-app bidding (parallel, real-time auction) to maximize fill rate and yield.

Topics Covered

• What ad mediation actually does, mechanically
• Waterfall vs. in-app bidding (and the hybrid model most publishers run in 2026)
• Ad networks vs. mediation platforms — the distinction publishers most often get wrong
• DSPs explained: the buy-side counterpart
• SSPs explained: the sell-side infrastructure mediation and networks both plug into
• A side-by-side comparison table
• Where each piece sits in the end-to-end programmatic stack
• Common misconceptions and how to think about your own monetization setup

What Is Ad Mediation?

Ad mediation is the technology layer that lets a publisher — typically a mobile app developer — plug in multiple ad networks and demand sources for a single ad placement, then have the system automatically decide which one gets to fill each impression. Instead of hard-coding one network's SDK into an app and hoping its fill rate and CPMs hold up, a publisher integrates a mediation SDK once, connects several networks behind it, and lets the mediation layer route each ad request to whichever source is currently paying the most or has an ad available.

The mechanics work like this: an ad request comes in, the mediation layer checks eligible demand sources, an ad gets selected and served, and the platform logs performance (fill rate, eCPM, latency) to keep optimizing future decisions. The value proposition is straightforward — it turns "manage five SDKs and hope one of them fills" into "manage one SDK that automatically finds the best-paying available ad."

Mediation has historically worked through one of two auction models:

Waterfall mediation ranks networks in a priority order, usually by historical average eCPM, and calls them one at a time. If the top-ranked network can't fill the request, the call cascades down to the next network, and so on — hence "waterfall." It's simple to set up but structurally inefficient: rankings are based on past performance, not the actual value of this impression, and a long waterfall can take over a second to resolve, losing impressions when users navigate away mid-load.

In-app bidding (the mobile equivalent of header bidding) sends the request to all connected networks in parallel, collects real bids in real time, and serves the highest one. This closes the gap between what a static waterfall assumes a network will pay and what it would actually pay for that specific impression. Public benchmarks from major mediation platforms have shown meaningful eCPM lifts when publishers move from a single-network or pure-waterfall setup to bidding-based mediation with several networks connected. By 2026, pure waterfall setups are largely treated as legacy, and most mature publishers run a hybrid: a bidding auction runs in parallel while a waterfall of fixed-price demand backstops whatever the bidding layer doesn't cover, often segmented by geography and ad format.

The mediation layer itself doesn't buy or sell media — it doesn't have its own advertiser demand. It's infrastructure that sits above demand sources and arbitrates between them.

Ad Mediation vs. Ad Networks: The Distinction That Trips People Up

This is the comparison publishers most often blur, because in practice the two frequently show up bundled in the same product. But conceptually, they answer different questions.

An ad network is a demand source. It aggregates ad inventory from many publishers on one side and advertiser demand on the other, then matches the two — essentially acting as a broker so an advertiser doesn't have to negotiate individually with hundreds of sites or apps, and a smaller publisher doesn't need direct advertiser relationships to sell out its inventory. When a publisher integrates an ad network's SDK, they are plugging into one pool of demand.

Ad mediation is a management layer. It doesn't supply its own demand; it decides which connected demand source — which network, which exchange, which bidder — gets to serve a given impression. A publisher can run mediation with one network behind it (in which case mediation isn't doing much) or, more typically, with many networks behind it, competing for every ad slot.

The confusion is compounded by the fact that several major platforms operate as both, depending on the setup. A single company might function as a pure ad network in one publisher's stack and as a mediation layer — or even an SSP — in another's, depending on what role it's playing for that specific relationship. The practical takeaway for a publisher isn't to try to categorize a partner from its brand name; it's to identify what role that partner is actually playing in your configuration.

A simple gut check: if a platform is one of several sources competing for your impressions inside a bigger system, it's a network. If it's the system deciding between sources, it's mediation.

What Is a DSP?

A Demand-Side Platform (DSP) is software that advertisers and media buyers use to purchase ad impressions programmatically across many exchanges and supply sources at once, rather than negotiating with publishers or networks one at a time. A media buyer sets targeting parameters, budgets, and bid strategy inside the DSP, and the platform bids on their behalf, in real time, against every eligible impression that matches their criteria as it becomes available across the ad exchanges it's connected to.

The core difference between a DSP and an ad network is who it serves and how much control they have. An ad network typically sells inventory at a fixed or negotiated rate with limited transparency into exactly where ads run. A DSP gives advertisers impression-by-impression control — they can see (within the platform's disclosure limits) which sites or apps they're bidding on, adjust bids per audience segment, and optimize continuously against performance data. That precision comes with a steeper learning curve; DSPs are built for buyers who want granular control, not simplicity.

DSPs exist purely on the buy side. A DSP doesn't have its own publisher relationships or inventory — it needs something to bid into. That something is usually an ad exchange, fed by SSPs.

What Is an SSP?

A Supply-Side Platform (SSP) is the publisher-side counterpart to a DSP. It's the technology publishers use to make their ad inventory available to buyers programmatically — connecting to ad exchanges, DSPs, and sometimes ad networks simultaneously, and running (or participating in) the auction that decides which bid wins each impression. Where a DSP helps an advertiser buy at scale across many publishers, an SSP helps a publisher sell at scale across many advertisers, while also handling yield optimization: floor pricing, deal prioritization, and reporting on which demand sources are actually performing.

In a typical large publisher's stack, the ad server sits at the center, several SSPs are connected to represent that inventory into the broader exchange ecosystem, and DSPs bid through those exchanges to win impressions — with an ad network or two often plugged in as an additional, simpler demand source alongside all of it.

Side-by-Side Comparison

How They Fit Together in Practice

A useful way to see the full picture: imagine a mobile game publisher running ads.

1. The publisher integrates a mediation SDK in the app.
2. Behind that mediation layer sit several ad networks, each with their own advertiser demand, plus a connection into the broader exchange ecosystem.
3. That exchange connection runs through one or more SSPs, which represent the publisher's inventory to outside buyers.
4. On the other end, advertisers are using DSPs to bid into that same exchange, targeting the audience this app's users represent.
5. When an ad request fires, the mediation layer checks bids from the connected ad networks and the real-time bid coming through the SSP-to-DSP auction, and serves whichever one is highest (or next in the waterfall if bidding didn't clear).

Four distinct roles, one impression. The "clean four-entity model" is a useful teaching tool, but real implementations mix layers constantly — the same company can be a pure network in one relationship and function as an SSP or a mediation source in another, depending on the deal.

Common Misconceptions, Clarified

"Mediation and ad networks are the same thing." They're not — mediation is the decision layer; a network is one of the things it's deciding between. A setup can run mediation with just one network behind it, or a network can operate entirely outside any mediation stack (direct-integrated, no competing demand). They're related but structurally different roles.

"More demand sources in mediation always means more revenue." More connected networks generally raises the ceiling on eCPM and fill rate, since more competition means a higher likelihood of a strong bid for any given impression. But each additional network integrated also adds latency and complexity, which is part of why the industry has broadly shifted from long sequential waterfalls toward parallel, real-time bidding.

"DSPs and ad networks compete for the same job." Not quite — a DSP is a tool for advertisers who want granular, self-directed control over targeting and spend across many sources. An ad network is closer to a managed service: the publisher (or advertiser) hands over more of the decision-making in exchange for simplicity. They can even be complementary — a DSP might be bidding through an exchange that an ad network is also plugged into for the same inventory.

"SSPs and mediation platforms do the same job." Both sit on the sell side and both aim to maximize what a publisher earns from its inventory, but an SSP's job is primarily to connect that inventory into the broader real-time-bidding exchange ecosystem for outside DSPs to bid on. Mediation's job is to arbitrate between whatever sources — networks, SSPs, direct bidding connections — a publisher has chosen to plug in. In many modern in-app stacks, the two work together rather than in place of each other.

The Bottom Line

If you're a publisher trying to make sense of your own monetization stack, the fastest way to cut through the terminology is to ask one question of each partner: is this a source of demand, or is this deciding between sources of demand? Ad networks, DSPs, and SSPs all ultimately connect to advertiser budgets in some form — they're demand or demand-adjacent infrastructure. Ad mediation is the layer that decides which of those demand sources wins, impression by impression. Understanding which role each partner in your stack is playing — rather than assuming it from the company's name or category label — is what actually helps in configuring floors, adding or removing partners, and diagnosing where revenue is being left on the table.

Have questions about how your current monetization stack is structured, or which of these pieces you're missing? Reach out to explore your setup.