Definition
A demand-side platform is software through which advertisers and agencies buy digital advertising impressions in real time across many sources of supply from one interface. The IAB Tech Lab's OpenRTB specification, which standardises the exchange between buyers and sellers, describes the buyer-side system as a bidder: it receives a bid request describing an impression opportunity, the context it sits in and whatever is known about the user, and returns a bid response naming a price and a creative. A DSP wraps that bidder in the tools a buyer needs: campaign and line-item structure, targeting, budgets and pacing, bid strategies, creative management, reporting and integrations with data sources and ad servers. The registry phrasing is the short form: it bids on impressions in real time using audience and contextual data. The programmatic ecosystem guide places the DSP among the other platforms.
How it works
For each bid request the DSP works through a fixed sequence. It parses the request: site or app, placement, size and format, device, location, consent signals, deal ID if present, and any user identifier it can match. It checks eligibility: which line items target this context, which have budget left and are within flight, which have not exceeded their frequency cap for this user, and which brand safety and inventory rules permit the placement. For the eligible line items it prices the bid, from a fixed CPM, a rule, or a model that predicts the chance of a click or conversion and values it against the line item's goal; in a first-price auction it may also shade the bid below the predicted value. It returns the highest-valued bid with the creative or a pointer to it. If the exchange reports a win, the DSP serves the creative, logs the impression and later matches clicks and conversions to it. The real-time bidding guide covers the auction mechanics from both sides.
| Platform | Works for | Decides |
|---|---|---|
| DSP | Advertiser or agency | Whether to bid, how much, which creative |
| SSP or exchange | Publisher | Which bidders to invite, floors, which bid wins |
| Advertiser ad server | Advertiser | Which creative to serve, the independent count |
| Publisher ad server | Publisher | Which demand source fills the slot |
| DMP or CDP | Either side | Which audience a user belongs to |
Data enters a DSP in three ways: first-party audiences from the advertiser's own tags and customer lists, third-party or publisher segments matched through identifiers, and contextual signals read from the bid request. Deals negotiated with publishers are matched by deal ID in the request and give a line item access to inventory, pricing or priority outside the open auction.
In practice
Choosing and running a DSP is mostly about supply access, data and fees. Platforms differ in which exchanges and publishers they connect to, which identifiers and audience sources they can match, which formats they handle (connected TV, audio and digital out-of-home are not universal), what their technology fee is, and how much of the bid decision they expose. Day to day, the work is structural: line items narrow enough to be judged, a frequency cap at the level the line items share, a conversion source the bid strategy can trust, and regular reading of the supply path and placement reports. Google's platform in this category is covered in the DV360 hub, which also describes the hierarchy most DSPs share in some form.
One bid request, one decision
A DSP receives a bid request from an exchange for a 300×250 slot on a cooking site, mobile web, UK, with a consented identifier and a floor of £1.20 CPM. Three line items are eligible on context; one is excluded because the user has already seen its creative 5 times today, and one has spent its daily budget. The remaining line item, a retargeting campaign for a kitchenware brand, matches the identifier to its site-visitor list and predicts a 0.9% click probability against a £0.45 target cost per click, which values the impression at £4.05 CPM. The bid shading model, seeing recent clearing prices on this placement around £1.60, bids £1.95. The exchange reports a win at £1.95, the creative is served, and the user clicks; the DSP records the click at £0.195 for the line item's cost-per-click report.
What it is not
A DSP is not an ad network: a network sells its own aggregated inventory at its own prices, while a DSP buys from many sellers on the advertiser's behalf and charges a fee on the media it buys. It is not an exchange or an SSP, which sit on the sell side and run the auction the DSP bids into. It is not an ad server, although most DSPs serve the creatives they win; the independent count across buying routes is the advertiser ad server's job. It is not a data platform, even though it stores audiences; the data it matches comes from the advertiser, from publishers or from vendors. And it is not programmatic itself: programmatic is the automated buying method, and a DSP is the buyer's tool for it, as Google Ads is the tool for buying Google's own inventory without one.
Related terms
The SSPSoftware publishers use to sell inventory. is the mirror image: where the DSP decides whether to buy, the SSP decides whom to ask and at what floor, and the OpenRTB bid request and response are the messages between them. RTBAuction per impression in milliseconds. is the auction protocol the DSP participates in for open and private-auction inventory, and the DSP's bidder is what the specification calls the buyer. A DMPPlatform that organises audience data for targeting. was the traditional source of third-party audience segments a DSP matched against identifiers; as cross-site identifiers decline, customer data platforms, publisher data in deals and the DSP's own modelling have taken over much of that role. Deal IDs, ad exchanges, header bidding and supply-path optimisation are the remaining vocabulary of the buy side, and the advertiser ad server is the system that keeps the DSP's own counts honest.
Common mistakes
- Judging a DSP by its interface. Supply access, identifier matching and fees decide outcomes; the console decides comfort.
- Buying everything in the open auction. Premium and video inventory is mostly sold through deals; the open auction returns what is left.
- Trusting the DSP's own conversion count across platforms. It sees only the impressions it bought; an ad server reconciles the rest.
- No frequency cap at the top of the hierarchy. Line items bid independently; the cap must sit where they all share it.
- Loading audiences without checking match rates. A segment that matches a small share of its users targets almost nobody.
- Ignoring the supply path. The same impression can arrive through several resellers at different prices; prefer the direct path.
