What is an ad server?

What is an ad server?

An ad server is software that decides which ad to show in each ad placement, delivers it, and records what happened. Every time a page, app or video player has a slot for an ad, the ad server picks the best eligible ad based on campaign rules, targeting and price, sends it to the screen, and counts the impression, click or view.

Publishers use ad servers to sell and manage their inventory. Advertisers and agencies use them to deliver and track campaigns across many publishers. Ad networks use them to run both sides at once.

How an ad server works

1. A placement asks for an ad. A tag on the page, an SDK in an app or a video player sends an ad request with details such as the placement, device, location and page.
2. The ad server finds eligible ads. It filters campaigns by dates, budgets, targeting, frequency caps and brand-safety rules.
3. It runs the decision. Direct campaigns, header bidding bids and programmatic offers are ranked by priority and price. The best ad wins.
4. It returns the ad. The winning creative (image, HTML5, native assets or a VAST video response) is delivered to the placement.
5. It records the result. Impressions, clicks, video completions and conversions are logged for reporting, billing and optimization.

All of this usually happens in well under a second, millions of times a day.

Types of ad servers

• Display ad servers deliver banners, rich media and HTML5 ads on websites. More on display ad serving.
• Mobile ad servers serve ads inside apps through an SDK and on mobile web, including MRAID rich media. More on mobile ad serving.
• Video and CTV ad servers deliver in-stream video and ad pods using VAST and VMAP to players, streaming apps and TVs. More on video ad serving.
• Native ad servers assemble ads from headlines, images and text so they match the look of the content. More on native ad serving.

Modern platforms such as DJAX AdServer combine these formats in one system, so one set of rules decides across all of them.

First-party vs third-party ad servers

A first-party (publisher) ad server is run by the owner of the inventory. It decides which ads appear on their sites and apps, and manages direct sales alongside programmatic demand.

A third-party (advertiser) ad server is run by an advertiser or agency. It delivers the campaign's creatives through each publisher's placements and counts results independently, so the buyer has one consistent source of truth. Third-party ad serving for agencies.

Features to expect in an ad server

• Campaign and line item management with budgets, pacing and priorities
• Targeting by geography, device, audience, context, time and frequency
• Support for display, mobile, video, native and performance formats
• Header bidding and programmatic (OpenRTB) connections
• Real-time reporting and an API
• Billing, roles and permissions, and fraud filtering

Use our ad server buyer's checklist to compare platforms.

Who needs an ad server?

Publishers need one as soon as they sell ads directly. Ad networks need one to connect many publishers with many advertisers. Agencies and advertisers use one to control and verify delivery across publishers. Retailers, streaming services and game studios increasingly run their own to build advertising businesses on their audiences.

Owning vs renting an ad server

You can rent an ad server as a hosted service, usually paying per 1,000 impressions, or own one by licensing software you run on your own infrastructure. Renting is faster to start. Owning gives you control of your data and roadmap and removes per-impression fees, which matters more as volume grows. Compare the costs with our calculator.

Frequently asked questions

Written by the DJAX AdServer team. Updated September 2026.