What is an ad server?

What an ad server does

Everything upstream of an ad server — planning, targeting, bidding — produces a decision. The ad server is what executes it. Four jobs, in order: store the creative, select which one to return for a given request, deliver it to the surface, and log the impression and any interaction that follows.

That logging role is why ad servers matter more than their plumbing suggests. They are the system of record. When a publisher's numbers and an advertiser's numbers disagree, the two ad servers are usually where the data discrepancy originates, because each is counting at a slightly different moment in the delivery sequence.

First-party and third-party ad servers

There are normally two in the path, and they belong to opposite sides of the transaction.

• The publisher's ad server (first-party) decides which of the campaigns sold against a placement should fill it, enforces priorities and frequency, and reports delivery to the publisher.
• The advertiser's ad server (third-party) holds the creative, applies the advertiser's own frequency and rotation rules across every publisher they buy, and gives the advertiser one count that is not the publisher's count.

Ad serving inside an AI assistant

The four jobs survive; the assumptions behind them do not.

A display ad server returns a creative asset — an image, a script, a VAST tag. An assistant cannot render an asset into a sentence. What it needs is structured content the model can present in its own voice and format: a product, a claim, a link, a disclosure. Serving is therefore closer to returning a record than returning a file.

Timing changes too. A page can call an ad server after the content has painted. An assistant is composing a single response, so the decision has to resolve before or during generation. There is no late fill.

And the frequency logic has no page to hang on. Capping is per conversation and per user rather than per pageview, because a long session is one continuous surface rather than a sequence of discrete loads.

How to tell an ad server from an SSP or a DSP

A DSP decides what to bid. An SSP decides what to offer and at what floor. An ad server decides what to actually return once those decisions are made, and counts it. A platform can perform more than one of these roles, but the roles are distinct — and when reporting disagrees, knowing which system counted what is how the disagreement gets resolved.