What is an ad server? It is the software that decides which ad fills an ad slot, delivers that ad to the browser and records the impressions and clicks that follow. Its decisions run on rules called line items.
A reader opens a news page and sees a banner for a shoe sale. Later the same slot shows a different ad. Nothing is broken: the ad server made a fresh choice each time the page asked. This guide covers that decision and delivery work, and it sits inside the wider picture of what is ad tech. Auction mechanics are left to separate guides.
The ad server in plain terms
An ad server is the decision and delivery engine of digital advertising. A page or app asks it for an ad, it checks which campaigns are eligible, picks one, and points the browser to the creative. It then logs what happened. Most confusion about ad servers comes from mixing up that job with neighbouring tools, so the table below sets the common misunderstandings against what actually happens.
| Common misunderstanding | What actually happens | Planning use |
|---|---|---|
| The ad server sends the ad itself | The server sends the browser the location of the requested ad, rather than the ad itself, using a 302 redirect. | When an ad fails to appear, check the delivery decision and the creative location as separate problems. |
| Clicks are counted only on the advertiser’s website | Ad servers use 302 redirects to track activities such as ad requests and ad clicks, so the count starts before the visitor lands. | Treat the ad server’s click total as a record of redirects it handled, not of what happened on the landing page. |
| The ad server is the same as an auction platform | The ad server chooses among eligible campaigns using its rules. Bidding is a different step that can feed into it. | Keep delivery settings and bidding questions apart when diagnosing results. |
| Only publishers need an ad server | Publishers and advertisers each use one, for different purposes. | Decide first which side of the transaction you are managing. |
The redirect behaviour follows the IAB Tech Lab glossary, and Google Ad Manager’s use as a publisher ad server is noted in an IAB Tech Lab analysis.
Misconception: the ad server hands over the ad
The ad server usually does not transmit the ad file to the page. The IAB glossary describes the 302 redirect as the process of a server sending a browser the location of a requested ad, rather than sending the ad itself. That small design choice explains why ad servers can sit in the middle of a request without carrying heavy creative files.
The ad serving process step by step
The ad serving process follows a consistent order, whichever vendor runs it.
- Page load. The browser loads a page that contains an ad slot with a tag pointing at the ad server.
- Ad request. The tag asks the ad server for an ad to fill that slot. This request is one of the activities the server can track through its redirect.
- Decision. The server compares the request with its line items, discards those that are not eligible and chooses among the rest by priority and other delivery rules.
- Redirect. The server answers with the location of the chosen creative, not the creative itself.
- Creative fetch. The browser follows that location, retrieves the creative and displays it.
- Logging. The server records the outcome so that reporting can show what was delivered.
Because the decision happens on every request, the same slot can show different ads on different page loads. That is normal behaviour, not a fault, and it is why an ad server needs clear rules to choose from.
Line items, targeting and priority
A line item is the unit the ad server actually delivers. It ties a creative or set of creatives to the conditions under which they may appear, such as targeting, schedule and importance relative to other line items. Campaign planners think in campaigns, but the server decides at line item level.
What a line item controls
- Targeting. This sets which requests a line item is eligible for. Audience segments, for example those built in a data management platform, can be one input; the guide on what is a data management platform covers where such segments come from.
- Creative. This is the ad the line item will point the browser to when it wins the decision.
- Priority. This ranks the line item against others that match the same request.
Priority as an ordered fallback
Priority works like a ranked list of options. When several line items match a request, the higher-ranked one is favoured, and lower-ranked ones serve when higher ones cannot. For a campaign owner, the practical lesson is that a line item can be correctly built and still deliver little if a higher-priority line item keeps taking the same requests.
Line items also appear in header bidding setups, where bids are represented inside the ad server so they can compete with directly sold campaigns. The guide on what is header bidding explains the bidding side. IAB Tech Lab has noted that it is unclear if and how Google’s policies will evolve for Prebid line items, so teams relying on that arrangement should watch vendor documentation.
How an ad server counts impressions and clicks
An ad server counts an ad event when its own systems log it. Per the IAB glossary, ad servers use 302 redirects to allow them to track activities such as ad requests or ad clicks. The click path therefore runs through the server first, then on to the advertiser’s destination, which lets the server record the click on the way.
Misconception: one total settles every dispute
An ad server’s report is a record of what that server logged. It is the reference most campaigns are managed against, but it is still one system’s view. Check which system a number comes from before comparing it with analytics on the landing page or with another vendor’s report, and compare like with like, for instance requests with requests and clicks with clicks.
Reporting is also where delivery problems show up. A line item that is not pacing as intended often points back to targeting that is too narrow or to a higher-priority line item absorbing the requests, which sends the reader back to the line item settings above.
Publisher ad server and advertiser ad server
A publisher ad server sits on the sell side and manages the inventory a site or app offers. An advertiser ad server sits on the buy side and manages the creatives and measurement for a brand’s campaigns. The publisher’s server decides what fills its own slots; the advertiser’s server supplies and tracks the ad being delivered.
Examples of ad servers
Google Ad Manager is a clear example on the publisher side, since publishers can use it as their ad server. IAB Tech Lab also notes that Google Ad Manager will facilitate many types of buying and selling on publishers’ first-party data, which shows the publisher ad server doing more than filling slots: it becomes the place where a publisher’s own audience data is put to work. Other vendors offer sell-side and buy-side products too, and their documentation is the best place to confirm exactly what each does.
Choosing between them
- Publishers need the sell-side server, because it controls which line items compete for their slots and how inventory is prioritised.
- Advertisers and agencies need the buy-side server when they want one place to manage creatives and read delivery across the sites carrying their ads.
- Teams on both sides should expect the two systems to log separately, so reporting questions need a named system of record.
Frequently asked questions
| Question | Answer |
|---|---|
| Does an ad server run auctions? | Its core job is choosing and delivering ads using line item rules. Bidding is a separate step that can feed into those rules. |
| Is an ad server the same thing as ad tech? | No. Ad tech is the whole field of tools that buy, sell and measure digital ads. An ad server is one component, the one responsible for decision and delivery. |
| Is Google Ad Manager the only ad server? | No. It is one example publishers can use. Other vendors offer ad servers for both publishers and advertisers. |
| Why would an ad not appear even though its line item is set up? | Another eligible line item may outrank it, or its targeting may match too few requests. Reviewing priority and targeting settings is the sensible starting point. |
