Is an SSP the same as an ad exchange?

No, though the two are often bundled by the same vendor. An SSP is the publisher's tool for managing inventory, setting floor prices, and connecting to demand. An ad exchange is the actual marketplace where auctions happen. Your SSP connects you to one or more exchanges. Google Ad Manager is an SSP; Google Ad Exchange (AdX) is the exchange it connects to.

Do I need an ad exchange if I already have an SSP?

You access ad exchanges through your SSP, not separately. If you are using Google Ad Manager, PubMatic, or Index Exchange, you are already connected to exchanges. You do not acquire an ad exchange relationship directly. The SSP manages those connections on your behalf.

Where does AdSense fit in the ad network vs SSP vs ad exchange taxonomy?

AdSense is a managed ad network. Google bundles the ad network, the exchange-level auction, and the SSP decision-making into one product. As an AdSense publisher, you have no direct control over floor prices, bidder mix, or which exchange fills your impressions. The tradeoff is simplicity. The cost is margin and transparency.

Where does AdMob fit in the SSP vs ad exchange framework?

AdMob is the app equivalent of AdSense. Google manages the demand path for you. When you add a mediation layer such as AdMob mediation, MAX, or LevelPlay, you are creating an SSP-like setup that connects multiple ad networks in a controlled auction or waterfall. That mediation layer is functionally your SSP.

What is a DSP and why does it appear in SSP vs ad exchange comparisons?

A DSP (demand-side platform) is the advertiser's buying tool. Publishers do not run DSPs. DSPs appear in these comparisons because your SSP's job is to expose your inventory to as many DSPs as possible. More DSP connections mean more bid competition, which raises your CPM. Understanding DSPs matters to publishers because supply path optimization by buyers, where DSPs cut their SSP connections, directly affects your fill rate and CPM without any change on your end.

At what scale does it make sense to move beyond a managed ad network to an SSP-level setup?

For web publishers, the threshold is roughly 5 million monthly impressions. Below that, the operational overhead of Google Ad Manager plus Prebid typically costs more in time than the yield improvement justifies. For app developers, the equivalent signal is around 10 million monthly ad requests. At that scale, direct SSP relationships and in-app bidding via MAX or LevelPlay start returning measurable eCPM improvements over managed networks alone.

Ad Network vs Ad Exchange vs SSP vs DSP: Where Does Your Setup Actually Sit?

The four pieces of the programmatic stack get conflated constantly. Ad networks sell inventory in a managed marketplace. Ad exchanges run real-time auctions across many networks. SSPs represent publishers in those auctions. DSPs represent advertisers buying through them. Most publishers don't have a clean mental model of where their setup sits, which is why "should I add an SSP" or "do I need an ad exchange" come up so often. The answer depends on what you're already running.

The taxonomy that actually matters

Four entities, four roles. The cleanest mental model:

Ad network: Side they serve: Both, simplified · What they do: Managed marketplace where the network handles demand and serves ads via a single integration · Who runs them: AdSense, AdMob, Media.net, Mediavine

Ad exchange: Side they serve: Both · What they do: Real-time auction infrastructure where many SSPs (selling) and many DSPs (buying) compete · Who runs them: Google AdX, Magnite, OpenX, Index Exchange

SSP (supply-side platform): Side they serve: Publisher side · What they do: Represents publisher inventory in exchange auctions, optimizes yield, takes a fee · Who runs them: PubMatic, Magnite, OpenX (yes, they run both)

DSP (demand-side platform): Side they serve: Advertiser side · What they do: Buys impressions through exchanges on behalf of advertisers · Who runs them: The Trade Desk, DV360, Amazon DSP

The reason these get confused: the boundaries blur in practice. PubMatic operates as both an SSP and an ad exchange depending on the relationship. Magnite is an SSP and an exchange. AdMob is an ad network but it also acts as an SSP in mediated setups. The clean four-entity model is a teaching tool. Real-world implementations mix the layers.

What this means for publishers: don't try to identify "which type of company is my partner" from the name alone. Identify what role they're playing in your specific setup.

Where does your setup actually sit?

Most publishers running ads fit into one of four archetypes. Find yours and the rest of this article makes sense.

You have a website. You signed up for Google AdSense. You added one tag to your site. Ads serve and you get paid monthly.

In the four-entity model: AdSense is functioning as an ad network for you. It's also using AdX (Google's ad exchange) under the hood to source demand, but you don't see that layer. Behind the scenes, DSPs from across the industry are bidding on your inventory through AdX, but to you it's a single monthly check.

The simplification works fine for most small web publishers. The entire stack is hidden. You don't need to know what an SSP is. You don't have one in any meaningful sense.

When you outgrow AdSense alone (typically at 50K monthly sessions and up), you start hearing terms like "header bidding wrapper" and "SSP relationship." That's when the four-entity model starts mattering operationally.

Archetype 2: AdMob only (mobile app)

You have a mobile app. You integrated the Google Mobile Ads SDK with AdMob. Ads serve in your app. Same simplified model as AdSense for web.

In the four-entity model: AdMob is an ad network. It also operates as part of Google's exchange infrastructure on the backend. To you, it's one integration that handles everything.

When you outgrow AdMob alone (typically when you hit consistent revenue and want to test multi-network mediation), you start adding mediation networks. AppLovin MAX, Unity LevelPlay, ironSource. Those add complexity but stay within the "ad network" tier of the model. You're adding more networks, not jumping to the SSP/exchange layer.

The jump to the SSP/exchange layer happens when you move to GAM (Google Ad Manager). That's when you start having direct SSP relationships and dealing with line items.

Archetype 3: Managed service (Mediavine, Raptive, Ezoic)

You signed up with a managed publisher service. They handle the entire ad operations layer for you. Multiple ad networks, header bidding wrapper, SSP integrations, optimization. You see one dashboard and one revenue line.

In the four-entity model: your managed service is operating as an ad network on top of a real header bidding setup. Behind the scenes they have direct relationships with multiple SSPs (PubMatic, Magnite, Index Exchange). They run a header bidding wrapper that puts those SSPs in real-time competition. They also serve AdSense and AdX as backfill demand sources.

You don't need to manage the four-entity model directly. Your managed service does it for you, takes a 25-35% revenue share, and you get a simpler dashboard in exchange.

Archetype 4: GAM plus mediation or header bidding (publisher at scale)

You're running Google Ad Manager as your primary ad server. You have direct SSP relationships, possibly a header bidding wrapper (Prebid or similar), maybe direct deal infrastructure. You see multiple networks competing in real-time auctions and you tune the configuration yourself.

In the four-entity model: you're operating at every layer. GAM is your ad server. Your SSPs (PubMatic, Magnite, Index Exchange, OpenX) represent your inventory in the exchange ecosystem. AdX is one of your exchanges (Google's). DSPs bid through those exchanges to win your impressions. AdSense and AdMob exist as demand sources within GAM (line items in your mediation chain).

This is the archetype where the four-entity model genuinely matters in daily operations. The decisions you make about adding or removing partners, configuring floors, tuning the wrapper, and managing supply chain integrity require the mental model.

The four-layer comparison in detail

For each entity, the things that actually matter to a publisher:

Ad network

A managed marketplace. The network handles demand sourcing, serves ads, and takes a revenue share (commonly 30-40 percent). You sign up, integrate one tag or SDK, and ads flow.

Best for: Smaller publishers, simple integration, single dashboard
Pricing: Revenue share, typically 30-40 percent to network
Examples: AdSense (web), AdMob (mobile apps), Media.net, Mediavine, Raptive
Trade-off: You give up control over exactly which advertisers serve, the configuration of the auction, and the floor pricing in exchange for operational simplicity

Ad exchange

The auction layer. Exchanges connect many SSPs (selling inventory) with many DSPs (buying inventory) in real-time bidding infrastructure. Publishers don't typically work with exchanges directly. They work through SSPs that sell into exchanges.

Best for: The infrastructure layer, not a publisher relationship per se
Pricing: Exchange takes a small fee (typically 5-15 percent of media spend) on each transaction
Examples: AdX (Google), Magnite, OpenX, Index Exchange, AppNexus (now Xandr)
Trade-off: Publishers don't pick exchanges directly. They pick SSPs that connect them to the exchange layer.

SSP (supply-side platform)

The publisher's representative in the exchange auction. SSPs aggregate publisher inventory, plug into multiple exchanges, optimize yield, and provide reporting. They charge a take rate on the media spend.

Best for: Publishers at scale (typically 500K+ monthly sessions, or mid-tier mobile apps with consistent volume) who want competitive auction pressure across multiple demand pools
Pricing: Take rate, typically 10-15 percent of gross media spend
Examples: PubMatic, Magnite, OpenX, Index Exchange, AppLovin (mobile-focused), ironSource (mobile)
Trade-off: Operational overhead (integration, monitoring, account management) in exchange for transparent supply chain control and the ability to run multiple SSPs in competitive auction (header bidding)

DSP (demand-side platform)

The advertiser's representative in the auction. DSPs are not typically a publisher relationship. They're the buy-side infrastructure that places bids on behalf of advertisers.

Best for: Advertisers and ad agencies, not publishers
Pricing: They charge advertisers, not publishers
Examples: The Trade Desk, DV360, Amazon DSP
Why publishers care anyway: When a publisher reads "demand from The Trade Desk," that means TTD's clients (advertisers) are bidding on their inventory through their SSPs and the connected exchanges

Common confusions corrected

The patterns I see most often across publisher conversations:

Wrong question framing. AdSense already routes through Google's ad exchange (AdX) under the hood, with multiple DSPs competing for your impressions. You're getting exchange-level demand, just abstracted away. The right question is: do you need direct SSP relationships beyond the abstraction AdSense provides? That depends on whether you have enough volume to attract a managed service or to run direct multi-SSP integration. Below 50K monthly sessions, the answer is almost always no.

Misunderstanding of the model. Publishers don't add ad exchanges directly. They add SSPs that connect them to exchanges. The exchange layer is infrastructure, not a partner relationship for publishers.

"Is AdMob an ad network or an SSP?"

Both, depending on context. As your only ad source, AdMob is functioning as an ad network. As one of several demand sources in a GAM mediation setup, AdMob is functioning as an SSP for AdMob's specific demand pool. The same partner can play different roles depending on how you've configured the stack.

"Do I need a DSP?"

Almost certainly not. DSPs are advertiser-side. Unless you're also buying advertising for your own products at meaningful scale, you don't need a DSP relationship. The reason publishers see DSP names in their reporting (TTD, DV360, etc.) is that those DSPs are the buyers behind the demand your SSPs are surfacing. You don't have a contract with them. They're upstream in the auction.

"An ad exchange and an SSP do the same thing"

They're related but not the same. SSPs sit between publishers and exchanges. SSPs handle yield optimization, supply path optimization, deal management, and direct relationships with publishers. Exchanges run the auction infrastructure that SSPs plug into. PubMatic the company runs both an SSP and an exchange, which is part of why this gets confused. The distinction: an SSP optimizes for the publisher's yield. An exchange runs the auction.

When you actually need each

The decision framework, by traffic stage:

Pre-revenue or under 10K monthly sessions: Just an ad network. AdSense or AdMob, depending on platform. Don't think about SSPs, exchanges, or DSPs. The stack you don't need is the one that costs operational time without paying back.

10K to 50K monthly sessions: Still ad network territory. Maybe two networks if you have mediation infrastructure. SSP/exchange direct relationships are over-engineered at this stage.

50K to 500K monthly sessions: Managed service (Mediavine, Raptive, Ezoic) is usually the right answer. They handle the SSP/exchange layer for you. You stay in the "ad network" mental model from your perspective even though the underlying infrastructure is multi-SSP plus exchange.

500K to 5M monthly sessions: Direct multi-SSP relationships start making economic sense. You bypass the managed service take rate. You take on operational complexity. Header bidding wrapper becomes essential. AdSense remains as a demand source, served through GAM as one line item among many.

5M+ monthly sessions: GAM 360 or GAM with strong infrastructure. Multiple SSPs in real-time competition. Possibly direct deal infrastructure. Maybe your own DSP relationships if you're also buying advertising at meaningful scale (rare for publishers, common for retailers and platforms).

The rule of thumb: don't add a layer until the existing layer is saturated. Adding an SSP when AdSense is filling 80 percent of impressions at acceptable eCPM doesn't help. Adding an SSP when AdSense is filling 60 percent and the rest is going unfilled or at low CPM does help.

Frequently asked questions

What's the simplest version of the difference between an ad network and an SSP?

An ad network is a managed marketplace. You give them your inventory, they handle demand, they pay you a revenue share. An SSP is more like a representative. They put your inventory into real-time auctions on multiple exchanges, optimize the bidding, and take a percentage of the media spend. Ad networks are simpler. SSPs typically extract more revenue at scale but require more operational effort.

Do I need a DSP?

Probably not. DSPs are buy-side infrastructure for advertisers and agencies. Publishers don't typically have direct DSP relationships. The DSP names that show up in your reporting (The Trade Desk, DV360, etc.) are the buyers behind the demand your SSPs and ad networks are surfacing. You're indirectly working with DSPs whenever you serve ads, but you don't sign contracts with them.

Where does AdMob fit in this taxonomy?

AdMob is Google's mobile ad network. From a publisher's perspective, it functions as an ad network: you integrate the Google Mobile Ads SDK, ads serve, you get paid. Behind the scenes, AdMob sources demand through Google's broader exchange infrastructure (AdX) and through mediation partners. In a multi-network mediation setup, AdMob becomes one demand source competing alongside others. The same product plays different roles in different setups.

What about AdX, where does that fit?

AdX (Google AdX, formally "Google Ad Manager Exchange") is an ad exchange. It's the auction infrastructure layer. Publishers don't typically interact with AdX directly. They interact with it through GAM (which surfaces AdX demand as a line item) or through AdSense (which uses AdX as backfill). If you're hearing "AdX" mentioned, you're probably running GAM or talking with someone who is.

Is header bidding an ad network, an SSP, or something else?

Header bidding is a technical pattern, not an entity type. It's a way of running multiple SSPs in parallel real-time auction before the publisher's ad server makes a decision. The SSPs in a header bidding setup are still SSPs. Header bidding is the wrapper that puts them in competition. Prebid is the most common open-source header bidding implementation.

What's the difference between supply path optimization (SPO) and supply chain integrity?

SPO is the practice of trimming the supply path between publisher and advertiser to reduce intermediary fees. If your inventory is being resold through three intermediaries each taking 5 percent, SPO is the work of removing redundant middle layers. Supply chain integrity is broader: it covers ads.txt and sellers.json verification, authorized seller validation, and audit of who's actually authorized to sell your inventory. Related work, different scope.

What to do this week

If you're trying to figure out where you sit:

Identify your archetype above. AdSense only, AdMob only, managed service, or GAM-plus.
Confirm whether your current stack is working for your traffic level. If you're at 50K monthly sessions on AdSense alone, you're probably leaving revenue on the table. If you're at 5M sessions on a managed service, you're paying a take rate that direct relationships could capture.
Don't add a layer until the existing layer is saturated. The biggest mistake I see at the small/mid level is adding an SSP relationship before AdSense is being fully optimized.
If you're considering moving from a managed service to direct multi-SSP integration, do the take-rate math first. Most publishers underestimate the operational cost of running their own header bidding wrapper.
If you're a mobile app developer, the relevant taxonomy is slightly different. AdMob is the starting point, mediation networks are the SSP-like layer, and GAM is where the four-entity model becomes operationally relevant. We covered the AdMob to GAM upgrade decision in AdMob vs AdSense vs GAM.

If you're not sure which archetype you're in or which layer to consider next, book a 30-minute call. I'll look at your current setup and tell you whether you should be on an ad network, a managed service, or a multi-SSP setup based on your specific traffic profile and operational capacity.