Ad Server
An ad server is the system that stores ad creatives, decides which ad to show for a given impression, delivers it, and records the resulting impressions, clicks, and conversions.
Key takeaways
- An ad server decides which creative to serve and delivers it to the page or app.
- Publisher-side (first-party) ad servers manage inventory; advertiser-side (third-party) ad servers manage creative and measurement.
- It is the system of record for impressions, clicks, and delivery.
- Header bidding feeds winning bids into the publisher ad server to compete with direct sales.
Two sides of the ad server
A first-party (publisher) ad server manages a publisher's own inventory, prioritizing direct-sold campaigns and programmatic demand. A third-party (advertiser) ad server hosts the buyer's creative, applies universal frequency capping across publishers, and provides independent counting. The two exchange tags and reconcile counts.
Decisioning and the system of record
For each impression the ad server runs decisioning "” choosing among eligible line items by priority, targeting, and value "” then serves the creative and logs the event. Because it counts delivery, the ad server is the reconciliation point where buyer and seller numbers are compared.
| Two types | Publisher (first-party) and advertiser (third-party) |
|---|---|
| Core function | Decision, deliver, and count ads |
| Role of record | Source of truth for delivery |
| Interacts with | SSPs, DSPs, header bidding |
Frequently asked questions
What is the difference between a first-party and third-party ad server?
A first-party (publisher) ad server manages the seller's inventory and decisioning; a third-party (advertiser) ad server hosts the buyer's creative and provides independent frequency capping and counting.
How does an ad server relate to an SSP?
The ad server makes the final serving decision; the SSP sources programmatic demand that competes inside the ad server against direct-sold campaigns, often via header bidding.