Why this matters
Under-delivery, odd prices and counts that disagree all have a cause somewhere between a page load and an impression, and the cause is only findable if you know which platform made which decision. This exercise applies the guide to DSPs, SSPs, exchanges and data platforms, which sets out who works for whom, and the real-time bidding guide, which opens the auction window itself. The programmatic advertising hub has the chain in one table.
The opera house and its first buy
Harbourlight Opera is a fictional regional opera company new to programmatic. Its agency has set up a display buy in a demand-side platform (DSPSoftware advertisers use to buy programmatic inventory.) to sell seats for an autumn production: regional targeting, an inclusion list of local news and arts sites, a frequency cap, and creatives served through the agency's ad server. The marketing director has asked: "When someone reads the local paper online, how does our ad end up on the page, and who decides?" The agency has pulled one impression's records from several systems, in no order.
Harbourlight Opera: one impression's records, jumbled
| Record | Source | What it says |
|---|---|---|
| A | Exchange | Bids received from three buyers; one arrived at 131 ms and was discarded; highest eligible bid £3.40 CPM; auction type first price |
| B | Reader's browser | Article "Festival season opens on the waterfront" requested on estuarycourier.example at 19:42:07 |
| C | Advertiser ad server | Impression counted when the creative began to render; viewability tag attached |
| D | Publisher ad server | No direct-sold campaign claims the mid-article slot at this moment; slot offered to programmatic demand |
| E | Supply-side platform | Bid request sent: site, page category arts and culture, slot size 300x250, floor £2.20 CPM, device mobile, region matched, consent string present, deadline 120 ms, supply chain one hop |
| F | DSP | Line item eligible: region, domain on inclusion list, approved creative of matching size; frequency check passed; pacing on plan; valuation £4.10; bid shaded to £3.40 |
| G | Exchange | Win notice sent to the DSP with clearing price £3.40 CPM |
| H | DSP | Creative markup returned: a tag pointing to the advertiser's ad server |
| I | Exchange | Billing notice fired when the creative began to render |
Over the first week, the DSP reports 182,000 won impressions; the ad server reports 171,000 rendered impressions.
Following the impression
Work from the reader's side outwards. Something must decide that the slot is open to programmatic buyers before any auction runs. The supply-side platform (SSPSoftware publishers use to sell inventory.) then describes the impression; the buyers' platforms decide; the exchange settles; and only after the window closes does the advertiser's ad server act. Keep apart what each platform knows and what it decides, and notice that the impression is counted more than once, at different moments.
Task
- Put the nine records in the order the events happened.
- For each record, name the platform, its side, the data it holds and the decision it makes.
- Mark the boundaries of the auction window: the record that opens it and the record that closes it.
- Name three points where this impression could have been lost, and which a higher bid would have fixed.
- Explain to the marketing director why the DSP and the ad server report different weekly totals, and which to report.
Worked answer
The impression traced
| Order | Record | Platform and side | Holds | Decides |
|---|---|---|---|---|
| 1 | B | Reader's browser | The page request | Nothing; it starts the chain |
| 2 | D | Publisher ad server, publisher | Direct campaigns and their priority | Offers the slot to programmatic because no direct campaign claims it |
| 3 | E | SSP, publisher | Page, slot, device, region, consent, floor, supply chain | What to tell buyers and the minimum it will accept |
| 4 | F | DSP, advertiser | The request plus the opera's targeting, cap, pacing and creatives | Bids £3.40 from a £4.10 valuation |
| 5 | A | Exchange, marketplace | All bids that arrived in time | Ranks bids above the £2.20 floor; the late bid is ignored |
| 6 | G | Exchange to DSP | The winning price | Tells the opera's DSP it won at £3.40 |
| 7 | H | DSP | The creative tag | Returns markup that calls the advertiser's ad server |
| 8 | C | Advertiser ad server, advertiser | The creative and counting rules | Serves and counts at render |
| 9 | I | Exchange | The render event | Makes the impression billable |
The auction window opens with the bid request (E) and closes when the deadline passes and the bids are ranked (A). Inside it, real-time bidding (RTBAuction per impression in milliseconds.) is software acting without a person.
Where it could have been lost. The publisher's ad server could have given the slot to a direct campaign (D). The DSP could have found the line item ineligible (F): domain off the list, no approved creative of that size, or the cap reached. The bid could have arrived late, as one rival's did, or fallen below the floor (A). The creative could have failed to render after the win (C). Only losing on price is fixed by bidding more.
The two totals. The DSP counts auctions won; the ad server counts creatives that began to render. Some wins never render, so the ad server's figure is lower.
The week's reconciliation
DSP won count for the week: 182,000. Ad server rendered count for the same week: 171,000.
182,000 − 171,000 = 11,000 impressions won but never counted as rendered, and 11,000 ÷ 182,000 ≈ 6 per cent of the DSP's figure. If the following week shows a gap of 15 per cent with no change to the plan, the first place to look is the creative and its tag, not the auction or the market.
The opera should report the ad server's total, because it is independent of the platform doing the buying, and watch the gap: steady is normal, a sudden widening points to a creative or tag problem.
Common mistakes
- Starting the chain at the SSP. The publisher's ad server first decides whether the slot is offered.
- Putting the advertiser's ad server inside the auction. It acts only after the win.
- Treating every loss as a price problem. Eligibility, deadlines, floors and render failures need other fixes.
- Reporting the DSP's won count. It measures auctions, not impressions that appeared.
Next, test your judgement in the DSPs, SSPs and real-time bidding checkpoint, or see the full module on the beginner programmatic level page.
