What is Ad Server?
Also known as: Advertising server, Third-party ad server
What is an ad server?
An ad server is software that stores ad creative, decides which ad to show each user, delivers the impression, and logs every event for reporting. It is the engine behind every banner, video pre-roll, and native unit you see on the open web. Per Google Ad Manager documentation, the ad call happens in the few hundred milliseconds between page request and render.
Two flavors exist. A first-party ad server runs on the publisher side. A third-party ad server runs on the advertiser side. Both speak the same standards, VAST for video and MRAID for in-app, and pass the impression between each other through tags.
Three jobs sit at the core:
- Store creative and the rules that govern when to show it.
- Match each incoming impression to the best eligible ad.
- Track every impression, click, view, and conversion.
First-party vs third-party ad servers
The same software category splits into two roles depending on who runs it. The publisher runs one to monetize. The advertiser runs the other to measure.
| Dimension | First-party (publisher) | Third-party (advertiser) |
|---|---|---|
| Who operates it | Publisher or SSP | Brand, agency, or trading desk |
| Primary job | Fill inventory and maximize yield | Traffic creative and measure delivery |
| Decides the winning ad | Yes | No, only renders or redirects |
| Typical examples | Google Ad Manager, Kevel, Equativ | Campaign Manager 360, Sizmek, Flashtalking |
| Revenue model | Percent of publisher yield or SaaS fee | SaaS fee per impression served |
The two work in series. The publisher's first-party server picks the winning campaign. If that campaign uses a third-party tag, the call redirects to the advertiser's server, which serves the actual creative and logs the impression. Discrepancies between the two logs (usually 5 to 15 percent) are a normal part of the workflow.
What an ad server actually does
Five jobs run in every ad call. Each one looks small. Together they decide whether a campaign delivers on plan or burns budget.
Creative storage
The server hosts every creative variant the campaign uses. HTML5 banners, MP4 video, native title-image-CTA bundles, audio spots, CTV VAST tags. Per the IAB Tech Lab VAST 4.3 specification, video creative is wrapped with verification, viewability, and tracking pixels at upload time.
Targeting
Targeting rules attach to each line item. Geo, device, browser, time of day, custom audience segments, frequency caps, recency rules. When an impression arrives, the server filters the eligible set in milliseconds.
Delivery and pacing
The server picks the winning ad based on priority tier, bid, and pacing goal. A guaranteed campaign with 10 million impressions over 30 days needs roughly 333,000 per day. The pacing engine keeps delivery on a smooth curve so the campaign does not finish early or under-deliver.
Tracking
Every served impression fires a beacon. Clicks fire a redirect. Viewability vendors (Moat, IAS, DoubleVerify) inject their own measurement pixels through the VAST wrapper. Conversion pixels close the loop on the advertiser side.
Reporting
Logs flow to a reporting layer keyed by campaign, line item, creative, placement, and dimension. Standard metrics include impressions, clicks, CTR, viewable rate, video quartiles, and conversions. Most servers expose log-level data through API or warehouse export.
Major ad servers
Four platforms handle the bulk of paid ad serving outside walled gardens. Each one targets a different inventory mix.
| Ad server | Primary use | Strengths | Best fit |
|---|---|---|---|
| Google Ad Manager | Publisher first-party | Open auction, header bidding, AdX integration | Web publishers with mixed direct and programmatic demand |
| Kevel | Custom retail and marketplace | API-first, no SDK, built for own-and-operated inventory | Retail media networks, marketplaces, sponsored listings |
| FreeWheel (Comcast) | Premium video and CTV | TV-grade workflow, VAST and SSAI support | Broadcasters, CTV apps, OTT platforms |
| Equativ (formerly Smart AdServer) | Independent display and video | Curation, deal IDs, EU data residency | Independent publishers and EU-focused brands |
Per Google Ad Manager documentation, GAM serves more than 1 trillion ad requests per day across the open web. Kevel pitches itself as the headless alternative for retail brands building sponsored placements without the GAM tag stack. FreeWheel dominates premium CTV in North America. Equativ leads the independent EU market after the 2023 Smart-LiquidM merger.
On the advertiser side, Campaign Manager 360 (formerly DoubleClick DCM) is the dominant third-party ad server. Flashtalking and Sizmek (now part of Amazon) compete in dynamic creative and creative-led measurement.
Ad server vs DSP vs SSP
Three pieces of the same supply chain. They get conflated because the lines blurred over the past decade.
| Player | What it does | Who runs it | Decides the bid? | Renders the creative? |
|---|---|---|---|---|
| Ad server (first-party) | Picks and delivers the winning ad on a publisher page | Publisher | No, picks by priority and bid | Yes |
| Ad server (third-party) | Stores creative, tracks impressions across publishers | Advertiser | No | Yes |
| SSP | Sells publisher impressions into auctions | Publisher | No, accepts bids | No |
| Ad exchange | Hosts the real-time auction | Neutral | No, matches bids | No |
| DSP | Buys impressions across exchanges | Advertiser | Yes | Sometimes |
Modern DSPs often bundle ad serving into the platform. The Trade Desk, DV360, and Amazon DSP all serve creative directly. Advertisers running across multiple DSPs still use Campaign Manager 360 as the neutral measurement layer, because each DSP only reports on its own buys.
Real-world example: a campaign trafficked through an ad server
A US auto manufacturer launches a CTV-led brand campaign. The plan splits across direct deals with three broadcasters and programmatic CTV through The Trade Desk.
Setup:
- Third-party ad server: Campaign Manager 360.
- Creative: 6 video variants (15 and 30 second), 4 companion display banners.
- Trafficking: VAST tags exported from CM360, dropped into each broadcaster's first-party server (FreeWheel) and into The Trade Desk.
- Verification: IAS viewability and brand safety pixels wrapped into every VAST tag.
The flow on a single impression:
- A user starts a Hulu episode. Hulu's first-party FreeWheel server picks the winning campaign from its line item pool.
- The winning line item is the auto brand's direct deal. FreeWheel redirects to the CM360 VAST tag.
- CM360 serves the actual MP4, fires the impression beacon, and passes the IAS pixel.
- CM360 logs the impression, video quartiles, and any clicks back to its reporting layer.
After 30 days, CM360 reports 18.4 million impressions, a 94 percent video completion rate, and 76 percent viewable rate across all sources. FreeWheel reports 19.1 million impressions on its side. The 3.7 percent discrepancy is normal. The advertiser pays on CM360 numbers because the third-party server is the source of truth for the brand. [PERSONAL EXPERIENCE] In our experience, discrepancies above 10 percent usually trace to tag implementation errors, not ad server bugs.
Ad servers in 2026
Three forces are reshaping the category. Each one changes what the server actually does.
CTV pulled the workflow upstream. Per AdExchanger coverage, server-side ad insertion (SSAI) now handles the majority of premium streaming impressions. The first-party ad server stitches ads into the video stream on the server before it ships to the device. The result is fewer ad-blocker losses and tighter frequency control. FreeWheel, Google Ad Manager, and Magnite all ship SSAI products.
Retail media broke the GAM monopoly. Kevel, Topsort, and Citrus Ad built API-first servers for marketplaces that need sponsored product placements. The traditional ad server tag stack does not fit retail, where the unit is a search result, not a banner. [UNIQUE INSIGHT] The retail ad server is the first new ad serving category in a decade. It exists because GAM cannot model a sponsored listing as a billable line item without heavy custom work.
Identity loss reshaped tracking. Third-party cookie deprecation in Chrome, App Tracking Transparency on iOS, and EU consent rules cut the data the third-party ad server can collect. Modern stacks lean on hashed email IDs (UID 2.0, RampID), server-to-server postbacks, and clean-room joins. The conversion pixel still fires. The user behind it is now a hashed token, not a cookie.
The ad server stayed essential. The plumbing changed. Pick the one whose feature set matches the inventory you actually need to serve, publisher tools for owned inventory, third-party tools for cross-channel measurement.
Related terms
Frequently asked questions
What is the difference between an ad server and an ad network?
An ad server is the technology that stores creative and serves impressions. An ad network is a business that aggregates publisher inventory and resells it. The network uses an ad server under the hood. You can run an ad server without being a network. You cannot run a network without an ad server.
What is the difference between a first-party and a third-party ad server?
A first-party ad server runs on the publisher side and decides which ad fills each impression. A third-party ad server runs on the advertiser side and tracks impressions, clicks, and conversions across many publisher sites. Per Google Ad Manager documentation, the two work together through standard tags.
Do I need an ad server if I run Google Ads?
No. Google Ads handles serving and tracking inside its own walled garden. Brands need a separate third-party ad server when they run direct deals with publishers, buy through multiple DSPs, or want unified measurement across Google, Meta, and the open web. Campaign Manager 360 is the most common third-party ad server for that use case.
How does an ad server pick which ad to show?
The ad server scores every eligible line item against the impression. Inputs include targeting rules, frequency caps, priority tier, pacing goals, and bid price. The highest-scoring ad wins. Per the IAB Tech Lab VAST 4.3 spec, video ad servers also negotiate format, bitrate, and verification wrappers in the same call.
What is the difference between an ad server and a DSP?
An ad server stores and delivers ad creative. A demand-side platform buys impressions through real-time auctions across exchanges. The DSP decides what to bid. The ad server decides what to render. Most modern DSPs include built-in ad serving, but advertisers running multi-DSP plans still use a separate third-party server for unified measurement.