The journey of one impression
A person opens an article on a news site. The page contains a tag from the publisher's ad server, which in a large share of cases is Google Ad Manager. The ad server first checks whether a directly sold campaign has a claim on the slot. If it does not, or if the publisher has chosen to let programmatic demand compete with direct demand, the slot is offered to the market.
The publisher's SSP, or the exchange it is connected to, builds a bid request using the OpenRTB protocol published by IAB Tech Lab. The request describes the impression: the page and its domain, the size and format of the slot, the device and its approximate location, whatever user identifiers the browser and the person's consent allow, the floor priceThe minimum bid a publisher will accept for an impression, set in its supply-side platform or ad server. the publisher will accept, any deal IDs the impression is eligible for, and the time by which bids must arrive. It is sent, in parallel, to every DSP the SSP is integrated with.
Each DSP matches the request against the line items its advertisers are running. Most requests match nothing and are discarded in microseconds. Where there is a match, the DSP checks frequency, pacing and brand safetyControls that keep ads away from content that would harm the advertiser's reputation., estimates what the impression is worth, and returns a bid with a reference to the creative. The SSP ranks the bids under the publisher's rules, applies any deal priorities, picks a winner and sends the winning creative markup back to the browser. The markup usually calls the advertiser's ad server, which serves the creative, counts the impression and loads any verification script that will measure whether the ad was viewable. The whole sequence completes before the article has finished rendering. The programmatic hub shows the same chain as a table alongside the measurement and tooling that sit on top of it.
The players
Each stage of the journey belongs to a platform that works for one side of the trade. Keeping the sides straight is the first skill in programmatic.
| Player | Works for | Job in the chain | Google's product |
|---|---|---|---|
| Publisher ad server | Publisher | Decides which ad fills a slot: direct, guaranteed or auction demand | Google Ad Manager |
| Supply-side platform (SSP) | Publisher | Packages inventory, sets floors and deals, sends bid requests, runs or forwards the auction | Google Ad Manager (Ad Exchange) |
| Ad exchange | The marketplace | Connects many SSPs and DSPs and runs the auction between them; the line between SSP and exchange has blurred | Ad Exchange within Ad Manager |
| Demand-side platform (DSP) | Advertiser | Evaluates bid requests, applies targeting, pacing and bidding rules, returns bids | Display & Video 360 |
| Advertiser ad server | Advertiser | Hosts creatives, serves them into any platform, counts impressions and clicks, records conversions | Campaign Manager 360 |
| Data platform (DMP or CDP) | Either side | Holds audience data and makes it available for targeting or measurement | Audience features inside DV360 and Ad Manager |
| Verification vendor | Advertiser, sometimes publisher | Measures viewability, brand safety and invalid traffic, before the bid or after the serve | Active View for viewability; third parties for the rest |
The ecosystem guide explains each role in depth, how a DSP and an SSP are integrated, why there is an ad server on both sides and how to read the chain of intermediaries between a budget and a publisher. Read it first if any row of the table is unfamiliar.
Auctions and deals in brief
Real-time bidding (RTBAuction per impression in milliseconds.) is the mechanism that allocates an open-market impression. Each DSP with a matching line item returns a price; the exchange ranks the prices and the highest wins. Most exchanges, Google's included, now run first-price auctionsAn auction in which the winner pays the amount it bid., meaning the winner pays what it bid, so DSPs shade their bids downwards to avoid paying more than the auction required. The real-time bidding guide covers the bid request field by field, how a bidder decides, what bid shading does and why timeouts lose auctions that were never visibly lost.
Not every impression is sold in an open auction. Publishers also sell through deals: a private auction open only to invited buyers, a preferred deal at a fixed price with a first look at the impression, or a programmatic guaranteed deal that reserves volume at an agreed price. Each deal carries an identifier that travels in the bid request and tells the DSP it may bid under those terms. The deal types guide compares the four, explains how a deal ID is matched and sets out how pricing and priority differ between them. In practice a plan mixes them: open auction for reach with strict inventory lists, deals for the publishers that matter most.
Data, identity and consent
Targeting in programmatic depends on recognising the person, the context or both. Context comes free with the bid request: the page, its category, the device and the location. Recognising the person needs an identifier that the DSP has seen before, which is where data platforms come in. A data management platform (DMPPlatform that organises audience data for targeting.) was the traditional store for anonymous, cookie-based segments bought from third parties; its role has shrunk as browsers restricted third-party cookiesCookies set by a domain other than the site visited, used to recognise a browser across sites. and as advertisers moved to customer data platforms built on their own first-party records. DV360 also offers Google's own audience segments, built from signed-in activity, which need no cookie match; the DV360 audiences guide covers what is available there.
Identity is now a mixed landscape. Third-party cookies are blocked by default in some major browsers and Chrome's position has moved several times; mobile advertising identifiers depend on user permission; publishers offer their own identifiers; and hashed email addresses underpin several industry schemes. A plan should assume that a share of impressions arrive with no usable identifier and that contextual signalsChoosing where ads appear from the content of the page, app or video being viewed rather than from data about the viewer. are what remain for those.
Consent governs all of it. In the EEA and UK, the IAB Transparency and Consent Framework carries the person's choices as a consent string inside the bid request, and Google requires publishers serving ads to those regions through its platforms to use a certified consent management platform, as its Ad Manager help documents. Without consent for personalised advertising, a DSP may still bid on the context, but audience targeting and frequency capping lose their footing for that impression.
Brand safety and viewability in brief
The open web is large enough that a campaign with no controls will appear next to content the brand would never choose, on sites built only to harvest ad revenue, and in slots that nobody scrolls to. Three kinds of control exist. Inventory controls decide where the ad may run: inclusion lists, exclusion lists, sensitive category settings and the choice of deals. Verification controls, from third-party vendors integrated into the DSP, evaluate each impression before the bid or after the serve for safety, fraud and viewability. Viewability filters bid only on impressions predicted to be seen, as defined by the Media Rating Council's standard and measured by Google's Active View or an accredited vendor.
Every control removes inventory, so reach falls and price rises as controls stack. The brand safety and viewability guide sets out the controls, the difference between safety and suitability, the problem of made-for-advertising sitesA site built to sell ad impressions rather than serve readers: thin or scraped content, a high ratio of ads to content and traffic bought rather than earned. and how to weigh the trade-off. The tutorial on building a programmatic inclusion list builds the strongest of those controls, the guide to writing a brand suitability policy writes down the tolerance the settings should follow, and the tutorial on responding to a brand safety incident covers the day an ad appears beside unsuitable content. Measuring viewability and attention after the fact, as opposed to filtering on it before the bid, belongs to the programmatic measurement section.
Further guides
Further guides put the brand safety controls into practice, from the list of sites a buy may run on to the day something goes wrong:
- Building a programmatic inclusion list — a tutorial for building and maintaining an inclusion list from the objective: sourcing publishers, checking each domain's authorised sellers and supply path, judging candidates against the suitability policy, sizing the reach the list leaves, sharing it as one channel and reviewing it from the placement report.
- Writing a brand suitability policy for programmatic — the short document that fixes the judgement behind the settings: the safety floor kept on for every buy, the brand's tolerance above it set topic by topic, a stance on news and user-generated pages, owners and exceptions, and how it becomes DV360 settings and vendor segments.
- Responding to a programmatic brand safety incident — a tutorial for the day a screenshot arrives: capture the evidence, trace the impression's route, stop delivery at the narrowest level that works, check what was billed, tell the people who need to know, fix the cause and write the record.
Where the money goes: the supply chain
The price an advertiser pays per thousand impressions (CPMCost per 1,000 impressions.) is not what the publisher receives. Between the two sit the DSP's platform fee, the cost of any third-party data segment, verification fees, ad serving fees and the exchange or SSP's share, each deducted along the way. The fees are rarely published and vary by contract; what matters is that a buyer knows what each hop costs and whether every hop is necessary.
Three IAB Tech Lab standards make the chain legible. A publisher's ads.txt fileA file on a publisher's site listing the companies authorised to sell its ad inventory. lists the sellers authorised
to sell its inventory; sellers.json lets each exchange declare who its sellers are; and the SupplyChain
object in the bid request records every intermediary an impression passed through. A buyer can therefore see
whether an impression came directly from the publisher or through resellers, and prefer the shortest path, a
practice known as supply path optimisation.
Following one CPM through the chain
A cosmetics brand pays a £10.00 CPM for an open-auction impression bought through its DSP. The DSP charges a platform fee of 11 per cent (£1.10), a third-party in-market segment costs £0.75, pre-bid verification £0.12 and ad serving £0.06, so £7.97 reaches the exchange. The exchange keeps a 14 per cent share (£1.12), passing £6.85 to the publisher's SSP, which in this case is the same company and takes nothing further. The publisher receives £6.85, or roughly two thirds of what the brand paid. When the brand's trading team compares supply paths, the same publisher's inventory bought through a reseller shows a second exchange hop taking a further £0.80, which is reason enough to prefer the direct path.
Common programmatic problems
Most problems in a programmatic campaign show up as one of a few symptoms. The table maps each to the guide that diagnoses it.
| Symptom | Usual cause | Guide |
|---|---|---|
| Line item delivers nothing | No bid requests match its targeting, deal or creative sizes; or it loses every auction on price | Real-time bidding, Deal types |
| High win rate but poor results | Bids are too generous for the inventory, or the inventory is low quality | Real-time bidding, Brand safety and viewability |
| Spend concentrated on a few unfamiliar domains | Open auction without an inclusion list; made-for-advertising sites optimising to cheap viewable impressions | Brand safety and viewability, Building an inclusion list |
| A negotiated deal is not spending | Deal ID not attached, creatives not approved by the SSP, targeting on the two sides does not overlap | Deal types |
| Impression counts disagree between platforms | Different counting points: bid won, creative requested, creative rendered | DSPs, SSPs and ad servers |
| Audience targeting reaches almost nobody | Identifiers missing because of consent, browser restrictions or a failed cookie match | DSPs, SSPs and data platforms |
| Effective price far above the plan's price per thousand | Fee stack and reseller hops, or data segments priced above their value | Programmatic CPM higher than planned, DSPs, SSPs and data platforms |
| Brand safety settings nobody can explain | Defaults chosen by whoever built the first line item and inherited since; no written tolerance | Writing a brand suitability policy |
| An ad is reported beside content the brand would never choose | A gap in the suitability policy, the inclusion or exclusion list, or a platform setting | Responding to a brand safety incident |
Every row has a cheaper equivalent in the planning stage. Deciding the inventory, the deals, the identifiers to rely on and the fee stack before launch is the subject of the media planning framework that this section leans on, and it is far less work than diagnosing the same questions from a delivery report after the budget has been spent.
