A supply-side platform, or SSP, is software publishers use to sell advertising inventory programmatically. The publisher supplies the space; the advertiser buys an opportunity to show an ad. An SSP helps connect that supply to potential buyers. Its presence does not establish the revenue a publisher will earn.
SSP and DSP: which side does each serve?
Amazon's SSP guide describes SSPs as publisher software and DSPs as advertiser software. A publisher can connect to multiple demand sources; a buyer uses its demand-side platform to determine which impressions to buy and at what price. Exchanges and integrations connect the parties.
For a publisher evaluating an SSP, the relevant question is what inventory it will help sell and on what terms. For an advertiser evaluating a DSP, the question is what inventory it can buy. These roles explain the names without implying that every vendor offers identical controls or commercial terms.
Where header bidding fits
Prebid's introduction describes publishers choosing demand partners, gathering their bids and passing one or more bids to an ad server. The server considers those bids alongside other available advertising, including direct and guaranteed commitments. Collecting a bid is therefore a step in the selection process, not proof that the ad was displayed.
In Prebid's documented setup, ad operations configures ad-server line items to match the key values sent with bids. If the matching setup is wrong, a header-bidding winner may not be considered in the final auction. The guide also describes app, video and server-side implementations.
What the publisher needs to operate
Use the following checklist to assign responsibilities before changing the setup. It is an operational review, not a claim that an SSP vendor performs every task.
| Area | Question to settle |
|---|---|
| Inventory | Which ad units and formats are included? |
| Demand partners | Which partners are enabled, and who approves changes? |
| Integration | Who checks that bid information reaches the intended ad-server configuration? |
| Commercial terms | Which fees, deductions and payment conditions apply to this agreement? |
| Reporting | Which event does each count represent, and who investigates mismatches? |
Avoid comparing a gross revenue number from one report with a net payment from another. Ask for the deductions, reporting period and counted event before deciding that either record is wrong. Keep the fee schedule attached to the actual agreement instead of relying on a generic industry percentage.
A fictional integration check
In a fictional integration check, a publisher receives a bid but cannot confirm that the ad server considered it. Ad operations checks whether the relevant line item matches the key values sent with the bid, working with engineering to resolve a mismatch. The returned bid alone does not establish display. This is a troubleshooting illustration, not a reported incident.
Check data assumptions separately
A technical integration is not evidence that every audience signal is available or appropriate to use. Ask which signals the implementation sends, which settings govern them and who owns the relevant privacy review.
Do not base a plan on an undated statement that Chrome has eliminated third-party cookies. In its April 22, 2025 announcement, Google said it would maintain user choice through Chrome settings and would not introduce a new standalone prompt. That is a dated product-policy statement, not permission to collect data or a complete account of today's browser features. Check the current documentation for the implementation you intend to use.