An adserver is the piece of software that receives a request for an advertisement, decides which advertisement should answer it, and returns the code that renders it. It also counts what happened: impressions, clicks, errors and, where an auction was involved, bids and match rates. Two versions of the same machine exist. The publisher runs one and the advertiser runs another, performing broadly the same job on opposite sides of the transaction, which is why vendors have long sold them as separate products. The term is written both as two words and as one; the industry uses them interchangeably.

The mechanism exists because hard-coding advertisements into web pages does not scale. A campaign booked on Monday and cancelled on Wednesday, rotated across four creatives, capped at three views per person and restricted to one country cannot be maintained by editing HTML. Delivery became a decision made at request time.

How the decision runs

On the open web the sequence begins in the browser. Google's Publisher Tag documentation describes it in six steps: the browser requests the tagging library, the library builds and sends one or more ad requests, the server matches ad units and key-values in the request, it runs an auction to select a creative, it returns the result, and the library renders it in the slot.

What travels in that request is narrow. Google Ad Manager's ad selection white paper lists five items: the HTTP header, which reveals browser, operating system and time; the IP address, which supplies geography; a user identifier, which may be a resettable mobile advertising ID, a publisher-provided identifier or a cookie; custom targeting key-values set by the publisher; and a correlator value marking which requests belong to the same page view.

The server then builds a list of every line item and yield group whose targeting matches. Ineligible entries fall away for frequency capping, day parting or competitive exclusions, and the correlator is consulted so that two advertisers in the same category do not appear beside each other. Ranking is by numeric priority, lower winning. Sponsorship sits at 4, Standard splits across 6, 8 and 10, and Network, Bulk and Price Priority share 12 alongside the Ad Exchange and AdSense types. House sits at 16 and serves, in Google's phrasing, only when remnant, Ad Exchange or Open Bidding demand is unavailable. Dynamic allocation then weighs the CPM of eligible remnant demand against the calculated opportunity cost of guaranteed line items, so that unreserved money is taken without endangering a delivery promise.

Creative selection follows. Wrong sizes and wrong formats are filtered out, a creative already shown on the page is excluded to prevent the same image occupying every slot, and where several remain the line item's rotation setting decides: evenly, weighted, optimised by historical click-through rate, or sequential across as many as 80 numbered creatives.

The constraints are published. An Ad Manager network may hold 600,000 line items in total but only 61,000 active ones, 1,000,000 creatives with 260 per line item, and 800 targeting criteria per entity. A single ad request may contend against no more than 300 line items, with the rest discarded by priority. Single request architecture caps at 30 slots per call, tags at 61,440 characters, and any URL the server generates through macros at 2,048. Mediation chains stop at 50 networks, and Google warns that longer ones add latency because each callout is sequential.

Two servers, two ledgers

The advertiser side runs a different product for a different reason. A brand buying across twelve publishers wants one impression count, one frequency cap and one conversion record rather than twelve. Third-party ad serving supplies that: the publisher's server calls the advertiser's server, which delivers the creative and writes its own log. Google's product in that role, Campaign Manager 360, pairs delivery with Floodlight conversion tags, historically split between counter tags recording that an action occurred and sales tags recording transaction value.

Two ledgers of the same event never agree. Google's own guidance acknowledges variances of up to 20% between Display and Video 360 and Campaign Manager 360, attributing them to counting at different moments, latency, invalid traffic filters applied at different times and third-party tags. The industry response was contractual rather than technical: the 4A's and IAB Standard Terms and Conditions fixed a 10% reconciliation threshold in version 3.0, finalised on February 22, 2010, with the buyer's numbers treated as controlling below it. Counting rules have kept moving since. DoubleClick for Publishers introduced downloaded impressions in November 2016 after operations staff raised rising sell-side and demand-side gaps, and the IAB, MRC and Mobile Marketing Association pushed measurement to begin-to-render.

Origin and evolution

The first central adserver was released by FocaLink Media Services on July 17, 1995, and relaunched as SmartBanner in February 1996. Accounts conflict on what it served: Wikipedia's ad serving entry treats it as the first ad server without qualification, while the ad tech oral history site Paleo AdTech, citing co-founder Dave Zinman, describes the product as built for the demand side, unlike the publisher-facing systems that followed. NetGravity shipped the first locally installed server in January 1996, running advertisements at Yahoo and Pathfinder, and was bought by DoubleClick in 1999, its software renamed DART Enterprise.

DoubleClick launched DART at the end of 1996 and added DART for Advertisers in October 1998, establishing the third-party adserver as a distinct product category. Google completed its $3.1 billion purchase of DoubleClick on March 11, 2008. DFP already held roughly 60% of publisher ad serving and counted nine of the ten largest United States websites as customers; the deal also brought a small exchange later known as AdX, projected in DoubleClick's own 2007 pitch deckto generate just $800,000 that year. The DoubleClick brand was retired in June 2018, DART for Publishers having already become DoubleClick for Publishers and then Google Ad Manager.

Header bidding forced the next change. Parallel auctions in the page moved price discovery ahead of the server, which was reduced to arbitrating between a header result and its own demand. Google shifted Ad Manager to a unified first-price auction in 2019, discontinuing its existing floor rules in the process, then imposed account-level caps on line items from May 1, 2023, narrowing how far publishers could customise the auction.

Ownership of the decision point turned out to be the commercial question in open-web display. On April 17, 2025, a federal court found that Google had illegally monopolised the publisher ad server and ad exchange markets, holding 91% of the first, and had unlawfully tied the two together. Kevel chief executive James Avery testified that a direct, non-preferential connection to Google's exchange would resolve the competitive problem. The Justice Department's final proposal sought more: portable historical DFP data for switching publishers, and ongoing AdX bid-level access for rival servers.

Money follows the server because reporting does. Google has said news publishers using Ad Manager keep more than 80% of programmatic revenue, a figure drawn from its own logs. The party that counts the impression also defines the denominator.

Limitations and disputes

Concentration is the first criticism, and now a judicial finding rather than a complaint. Fragility is the second. A Google platform failure in January 2026 cut some publishers' revenue by as much as 90% overnight, with Ad Exchange match rates collapsing; a decision layer that every impression passes through has no graceful degradation.

Measurement is the third. Because the publisher server and the advertiser server count at different points, reconciliation is a permanent operating cost rather than an exception. Coverage is the fourth: walled gardens run their own delivery and admit third-party servers only on restricted terms, so reporting unified across the open web still breaks at their edge.

Disambiguation

An ad exchange matches bids in real time; it prices inventory but does not hold the publisher's booked orders. Google Ad Manager bundles both, an exchange and a server, in one account, which is precisely the combination the courts examined.

A supply-side platform connects a publisher to demand sources and optimises yield across them. It sits below the ad server in the stack, supplying one candidate to a decision the server still makes.

A demand-side platform buys impressions on behalf of advertisers. It decides what to bid; the advertiser's third-party ad server decides which creative and writes the buyer's record of delivery.

An ad network aggregates inventory and resells it. Networks were among the first demand sources ad servers called, and survive as a line item type rather than a rival decision layer.

Recent developments

Remedies landed on September 2, 2026. Judge Leonie Brinkema declined to order divestiture of AdX or the DFP publisher ad server, adopting behavioural obligations instead and ending first look, last look and unified pricing. The memorandum opinion was sealed for fourteen days and a jointly proposed final judgment is due on October 2, 2026, so the operating rules that will govern how Ad Manager treats rival ad servers were not public at the time of writing.

Counting is changing too. AdSense will stop counting unrendered advertisements as impressions from February 17, 2027, aligning with the IAB and MRC standard and reducing discrepancies with buy-side measurement.

Video is where the category is least consolidated. A November 5, 2025 comparison of seven video ad servers placed Google Ad Manager, FreeWheel, Publica, SpringServe, Adtelligent, Aniview and Project Limelight against connected television spending approaching $33.35 billion for the year. Smaller platforms pick outside the incumbents: Equativ became the ad server and primary supply-side platform for the smart television operating system Titan OS in March 2025.

Timeline

  • June 1995: The motherboard for the first central ad server is assembled
  • July 17, 1995: FocaLink Media Services releases the first central ad server
  • January 1996: NetGravity ships the first locally installed ad server, running advertisements at Yahoo and Pathfinder
  • February 1996: FocaLink relaunches its product as SmartBanner
  • End of 1996: DoubleClick launches DART, offering centralised ad serving beyond its own network
  • October 1998: DoubleClick introduces DART for Advertisers, creating the third-party ad server as a product category
  • 1999: DoubleClick acquires NetGravity and renames its software DART Enterprise
  • November 2004: The IAB issues the first global rule for counting online advertisements
  • March 11, 2008: Google completes its $3.1 billion acquisition of DoubleClick
  • 2010: DART for Publishers is rebranded DoubleClick for Publishers
  • February 22, 2010: Version 3.0 of the 4A's and IAB Standard Terms and Conditions formalises the 10% discrepancy threshold
  • November 2016: DoubleClick for Publishers introduces downloaded impression metrics
  • June 2018: Google retires the DoubleClick brand, creating Google Ad Manager and Campaign Manager 360
  • 2019: Ad Manager moves to a unified first-price auction and existing floor price rules are discontinued
  • May 1, 2023: Account-level limits on Ad Manager line items take effect
  • April 17, 2025: A federal court finds Google monopolised the publisher ad server and ad exchange markets, with 91% of the first
  • September 5, 2025: The European Commission fines Google 2.95 billion euros over ad tech self-preferencing
  • December 2025: Google removes unified pricing rules from Ad Manager, restoring buyer-specific floors
  • January 2026: A Google platform failure cuts some publisher revenue by up to 90%
  • September 2, 2026: The court rejects divestiture of AdX and DFP and adopts behavioural remedies
  • February 17, 2027: AdSense stops counting unrendered advertisements as impressions

Summary

Who. Publishers and their ad operations teams operate sell-side ad servers; advertisers and agencies operate buy-side ones. Google runs both of the largest, Ad Manager and Campaign Manager 360. Independents including Kevel, Equativ, FreeWheel, Publica, SpringServe and Microsoft supply the rest, and the Justice Department, seventeen state attorneys general and the European Commission have all made publisher ad serving the subject of enforcement.

What. An ad server receives an ad request, evaluates eligible campaigns against targeting, priority and price, selects a creative, returns the code that renders it, and records the impression, click and error counts that both sides bill against.

When. The first central server appeared in July 1995 and the first locally installed one in January 1996. DART for Advertisers created the third-party category in October 1998, Google acquired DoubleClick in March 2008, and the market reached a court in April 2025, with remedies decided on September 2, 2026.

Where. In the browser through tagging libraries, in applications through mobile SDKs, in video players through VAST responses, and increasingly server-side in connected television, where stitching happens before the stream reaches the device.

Why. Every advertisement placed programmatically or by direct sale passes through a decision made at request time, and whoever makes that decision controls sequencing, pricing and the impression count. That is why the ad server, an unglamorous piece of delivery infrastructure, became the centre of the largest antitrust case in advertising.