A demand-side platform (DSP) is software that lets advertisers buy digital ad impressions programmatically across many publishers and exchanges from a single interface. A supply-side platform (SSP) is the mirror-image technology: software that lets publishers and app developers expose their inventory to as many potential buyers as possible to maximize yield. The two platforms sit on opposite sides of the same auction and are designed to work together, not replace each other.

If you are running user acquisition for a mobile app, you are almost certainly buying through a DSP. If you are monetizing an app with advertising, you are almost certainly selling through an SSP. Understanding how each platform works and how they interact in real time is foundational to making smarter decisions about where to spend, how to measure, and which supply paths to prioritize.

DSP vs SSP at a glance

	Demand-side platform (DSP)	Supply-side platform (SSP)
Primary user	Advertiser or UA team	Publisher or app developer
Core function	Buy ad impressions efficiently	Sell ad inventory at maximum yield
Optimization goal	Cost efficiency, targeting accuracy, ROAS	Revenue per impression, fill rate
Inventory role	Accesses inventory from many sources	Exposes inventory to many buyers
Data applied	First-party audience data, bidding signals	Publisher audience data, floor prices
Pricing logic	Sets bid price, manages budget pacing	Sets price floors, chooses winning bid
Mobile specifics	Targets users by device, OS, in-app behavior	Manages in-app ad slots, SDKs, in-app bidding

What is a demand-side platform (DSP)?

A demand-side platform is software that lets advertisers and their agencies purchase digital ad impressions automatically across multiple publishers, ad exchanges, and SSPs from a single interface. Rather than negotiating directly with individual publishers, a DSP connects to the broader programmatic ecosystem and submits real-time bids for impressions that match the advertiser’s targeting criteria.

Per the IAB Tech Lab’s OpenRTB standard, the protocol underpinning most programmatic transactions was built specifically to standardize how buyers and sellers communicate across the supply chain. DSPs are the primary implementation of the buy-side of that standard.

In practice, a DSP does several things simultaneously:

1. Receives bid requests from ad exchanges and SSPs containing anonymous signals about an available impression (device type, app category, audience segment, location).
2. Evaluates each impression against the advertiser’s targeting parameters, frequency caps, and budget constraints.
3. Submits a bid in real time, typically within 100 milliseconds of receiving the request.
4. Reports on outcomes: impressions won, clicks, installs, downstream events, and cost metrics.

For mobile UA practitioners, the DSP is where campaign strategy becomes executable. Audience segmentation, bid shading, creative rotation, frequency capping, and attribution window alignment all happen within or adjacent to the DSP layer.

What is a supply-side platform (SSP)?

A supply-side platform is technology that enables publishers, app developers, and connected TV operators to manage their available advertising inventory, make it accessible to multiple buyers simultaneously, and optimize the revenue earned from each impression.

Per the IAB Tech Lab’s sellers.json specification, SSPs are required to publish a public record of every seller they represent, giving DSPs a verifiable way to trace each bid request back to a legitimate publisher. This supply-chain transparency layer has become a baseline requirement for responsible programmatic buying.

An SSP performs these functions for a publisher:

1. Aggregates demand: connects the app or site to dozens of DSPs and ad exchanges at once, so each impression is competed for by the widest possible pool of buyers.
2. Sets price floors: the minimum CPM below which an impression will not be sold, protecting inventory value.
3. Runs the auction: collects bids from all eligible buyers, selects the winner according to the auction rules (typically first-price in modern programmatic), and delivers the winning creative.
4. Provides yield analytics: reporting on fill rates, average CPMs, and demand-source performance to help publishers understand which demand relationships are most valuable.
5. Manages brand safety and suitability controls: enforces publisher policies about which categories of advertiser can serve in their inventory.

For mobile app developers, SSP selection is a significant monetization decision. The breadth of demand connected to an SSP, the quality of its auction mechanics, and the accuracy of its SDK are all factors that affect how much revenue a given impression generates.

How DSPs and SSPs work together in the programmatic ecosystem

Every time a user opens an app and an ad slot becomes available, a programmatic auction takes place in the background. The DSP and SSP are the two primary actors in that auction, and the full transaction completes before the page or screen finishes loading. Here is how the sequence works:

1. Ad slot triggers a bid request. The app’s SSP (or its mediation layer) detects that an ad slot is available and assembles a bid request containing signals about the impression: app bundle ID, device type, operating system, geographic location, and any audience data the publisher shares.
2. Bid request is broadcast. The SSP sends this request to connected ad exchanges and DSPs, often simultaneously via header bidding or its equivalent in mobile (parallel auctions run by a mediation SDK).
3. DSPs evaluate and bid. Each DSP receiving the request checks whether the impression matches the targeting parameters of active campaigns. If it does, the DSP calculates a bid price based on the expected value of the impression and submits it, typically in under 100 milliseconds.
4. The auction clears. The SSP collects all bids, applies the publisher’s price floors and any deal-priority rules, and selects the winning bid.
5. The ad renders. The winning DSP’s creative is fetched from an ad server and rendered in the app. The publisher receives payment (minus platform fees) and the advertiser records an impression.

This process, known as real-time bidding (RTB), is the operational core of the open programmatic ecosystem. Not all programmatic transactions happen this way: private marketplace (PMP) deals and programmatic guaranteed (PG) deals are negotiated directly between buyers and sellers and then executed automatically, bypassing the open auction. The industry has been steadily shifting toward these direct transaction types as buyers prioritize curated supply and more controlled inventory relationships.

The ad exchange layer sits between DSP and SSP in open auction transactions, acting as a neutral clearinghouse that routes bid requests and aggregates demand. In practice, the boundary between SSP and exchange has blurred: most major SSPs operate their own auction exchange functions, and the terms are often used interchangeably in the industry.

What DSPs and SSPs mean for mobile UA specifically

The mobile UA context differs from general display advertising in several important ways, and those differences shape how you should think about both DSP and SSP selection.

In-app inventory is a different supply category

Web programmatic and in-app programmatic use different technical pipes. In-app inventory is accessed through SDKs embedded in the app, not browser-based JavaScript tags. SSPs serving mobile app inventory maintain their own SDK ecosystems, and the quality of that SDK (latency, crash rate, mediation compatibility) matters as much as the breadth of demand connected to it.

Mobile advertising led all major media types in advertiser spending in 2023, per Business of Apps’ mobile advertising research. And per EMARKETER, programmatic is on track to reach 90% of display ad spending worldwide. For UA teams, the conclusion is the same either way: the in-app supply chain is where the inventory is.

iOS privacy frameworks change what DSPs can see

On iOS, Apple’s App Tracking Transparency (ATT) framework limits the availability of device-level identifiers for advertising. Per AppsFlyer’s glossary, SKAdNetwork (SKAN) is Apple’s framework for providing privacy-compliant, aggregated attribution for iOS campaigns. At WWDC 2024, Apple introduced AdAttributionKit (AAK) as the successor framework, building on SKAN’s foundation with expanded re-engagement measurement and third-party marketplace support. Per Adjust’s SKAN documentation, AAK is designed to be interoperable with SKAN, allowing both frameworks to run concurrently during the transition.

For mobile UA teams, the practical implication is this: the attribution data flowing back to your DSP depends on which frameworks the ad network serving the impression and the publisher’s SDK support. A DSP that correctly supports both SKAN 4 and AdAttributionKit postbacks will give you more complete campaign measurement on iOS than one that does not.

Supply-path optimization is a UA budget lever

Per EMARKETER’s H1 2026 programmatic forecast, US programmatic ad spending is on track to exceed $200 billion in 2026, with most automated buys transacting via direct deals. As the market has matured, the number of intermediary hops between a DSP and a publisher has become a cost-efficiency issue. Supply-path optimization (SPO) is the practice of deliberately choosing which SSPs and supply paths to buy through in order to reduce fees and increase the share of budget that reaches working media.

For UA teams, SPO means auditing which SSPs your DSP is connected to, understanding the fee structures along each path, and, where possible, establishing preferred deal relationships directly with high-quality publishers. The IAB Tech Lab’s sellers.json standard is the mechanism that makes this auditable: it lets DSP buyers verify who is actually selling each impression in the chain.

Measurement integration across DSP and SSP requires MMP alignment

A mobile measurement partner (MMP) such as AppsFlyer or Adjust sits alongside the DSP as an independent attribution layer. The MMP receives postbacks from the SSP (via the publisher’s SDK) and from Apple’s or Google’s attribution frameworks, reconciles them against the DSP’s reported impressions, and produces the attribution view your team uses to make optimization decisions.

The implication for campaign setup is that attribution window settings must be aligned across the DSP, the MMP, and the SSP-level publisher integrations. A DSP reporting a 7-day click-through window while your MMP attributes to a 30-day view-through window creates measurement inconsistency that can distort ROAS calculations and misdirect budget.

Common misconceptions about DSPs and SSPs

“A DSP and an ad network are the same thing.” They are not. A traditional ad network bundles publisher inventory and resells it to advertisers at a markup, with the network controlling inventory selection. A DSP gives the advertiser direct access to individual impressions across many sources, with full control over targeting, bidding, and creative. The network model abstracts the supply; the DSP exposes it.

“SSPs just pass impressions to the highest bidder.” Modern SSPs do much more than run a price auction. They apply brand safety controls, enforce publisher floor prices, run header bidding logic to solicit bids from multiple demand sources simultaneously, and provide publishers with yield analytics. The SSP is an active yield-management layer, not a passive auction platform.

“Using more DSPs gives you access to more inventory.” Not necessarily. Because many major SSPs are connected to most major DSPs, the same underlying publisher inventory is often accessible through multiple buying paths. Adding more DSPs without a clear strategy can increase the risk of frequency inflation (the same user seeing the same ad multiple times through different buying channels) rather than expanding reach.

“A DMP and a DSP are interchangeable.” A data management platform (DMP) stores and organizes audience data. A DSP uses that data to bid on impressions. They serve different functions, though DSPs increasingly ingest first-party data natively, reducing (but not eliminating) the need for a separate DMP layer for most mobile UA use cases.

“SSPs only serve publishers, not advertisers.” SSPs serve publishers directly, but the decisions publishers make about their SSP configuration directly affect advertisers. Floor prices, deal structures, and brand safety categories set by publishers through their SSP determine what inventory is available to buyers and at what price, making SSP mechanics relevant knowledge for any UA team.

Frequently asked questions

What is the main difference between a DSP and an SSP? A DSP is used by advertisers to buy ad impressions efficiently across many publishers from a single platform. An SSP is used by publishers and app developers to sell their available ad space to as many potential buyers as possible. The DSP represents the buy side of the programmatic transaction; the SSP represents the sell side.

Can a company use both a DSP and an SSP? A publisher that also runs its own advertising campaigns (a common position for large app developers who both monetize with ads and run UA campaigns) can use an SSP to monetize their inventory while also using a DSP to run their own user acquisition. The two functions are distinct and typically managed by different teams.

What is an ad exchange and how does it relate to DSPs and SSPs? An ad exchange is a marketplace that connects buyers (DSPs) and sellers (SSPs) in real-time auctions. It routes bid requests from SSPs to eligible DSPs, collects their bids, and returns the winner. In modern programmatic infrastructure, many SSPs operate their own exchange functions internally, so the SSP and exchange layers are often combined in practice.

What is real-time bidding (RTB) and do all programmatic transactions use it? Real-time bidding (RTB) is the open auction process by which individual impressions are auctioned to the highest bidder in milliseconds. Not all programmatic transactions use open RTB. Private marketplace (PMP) deals are conducted between selected buyer-seller pairs at negotiated prices. Programmatic guaranteed (PG) deals offer reserved inventory at fixed prices, automated through programmatic pipes but without a live auction.

What does “supply-path optimization” mean and why does it matter for mobile UA? Supply-path optimization (SPO) is the practice of selecting which SSPs and supply routes to buy through in order to reduce fees and increase the share of each advertising dollar that reaches working media. Because a single publisher’s inventory is often available through multiple SSPs and exchanges, UA teams can use SPO to prefer the most direct and cost-efficient path to that inventory, reducing intermediary fees and improving effective CPM.

How does iOS attribution affect what a DSP can do on mobile? On iOS devices where users have not opted in to tracking via the App Tracking Transparency (ATT) prompt, DSPs cannot access device-level identifiers. Instead, campaign measurement relies on Apple’s SKAdNetwork (SKAN) or AdAttributionKit (AAK) frameworks, which provide aggregated attribution data. DSPs that have built deep integrations with these frameworks can still optimize campaigns at scale; those that have not face significant measurement gaps on iOS traffic.

What is the difference between a DSP and a mobile DSP? A mobile DSP is a demand-side platform specifically built or optimized for in-app and mobile web advertising. Mobile DSPs maintain direct SDK integrations with app publishers and SSPs, support mobile-specific targeting signals (device type, operating system, app category, carrier), and are integrated with mobile measurement frameworks including SKAN and AdAttributionKit. General-purpose DSPs often include mobile inventory access, but the depth of mobile-specific optimization varies significantly across platforms.

What role do MMPs play alongside DSPs and SSPs? A mobile measurement partner (MMP) such as AppsFlyer or Adjust acts as an independent attribution layer that reconciles signals from the DSP, the publisher’s SSP-side SDK, and Apple’s or Google’s attribution frameworks. The MMP produces the authoritative install and event attribution your team uses to evaluate campaign performance. Because DSPs and SSPs each report from their own perspective, an MMP is essential for deduplicating credit and producing a single source of truth for ROAS measurement. For more on how ROAS ties into your broader UA measurement strategy, see our guide to what makes a good ROAS for mobile apps.

The programmatic stack in context

DSPs and SSPs are the two most important platforms in the programmatic advertising ecosystem, but they do not operate in isolation. They sit within a broader stack that includes ad exchanges, MMPs, data management layers, and brand safety verification tools. Understanding how each layer interacts with the others is increasingly important as the industry moves toward curated supply, privacy-first measurement, and AI-driven bidding.

Per EMARKETER’s worldwide programmatic data, programmatic will account for the overwhelming majority of all new digital display ad spending for the foreseeable future. For mobile UA practitioners, that means the DSP and SSP are not just useful tools to understand. They are the infrastructure through which almost all scalable user acquisition now flows.

For a deeper view of how programmatic mechanics apply to specific in-app ad formats and buying strategies, see our complete guide to in-app advertising for mobile marketers.