Publisher Ad Server Software

Header Bidding vs Ad Server: How They Work Together and What Publishers Need

S
SaaSPodium Editorial TeamUpdated:
Header Bidding vs Ad Server: How They Work Together and What Publishers Need - SaaSPodium

Advertisement

Header bidding is an auction technique that lets several demand sources bid on an impression before the ad server call. A publisher ad server then decides which ad to deliver, applying direct deals, rules and the winning bid. They are complementary parts of one ad stack.

Publishers often hear the question phrased as a choice, header bidding or ad server. It is not a choice. The ad server is the system of record that decides and delivers ads, while header bidding is an upstream auction that feeds it extra bids.

Understanding the split helps you diagnose revenue, speed and reporting problems. It also clarifies what to ask when you evaluate platforms in the Publisher Ad Server Software category.

Header bidding implementations in browsers are commonly built with the open-source Prebid project, and bid requests commonly follow the OpenRTB standard. Privacy rules matter too: see the GDPR guidance on cookies and the European Data Protection Board for consent obligations. One widely used ad server is Google Ad Manager.

What Does a Publisher Ad Server Do?

A publisher ad server stores your ad inventory, applies targeting and delivery rules, selects which ad to show and records impressions and clicks. It is the central decision and reporting layer for everything that runs on your pages or apps.

Core jobs include managing direct-sold campaigns, setting priorities and pacing, capping frequency, running quality filters and producing revenue reports. Platforms listed in our directory include Google Ad Manager, Revive Adserver, AdButler, Kevel and Epom.

For a fuller definition, see What Is a Publisher Ad Server? Features, Pricing and How to Choose One.

What Is Header Bidding?

Header bidding lets multiple ad exchanges or demand partners bid on an impression at the same time, before the ad server makes its call. The highest bids are passed to the ad server so they can compete with other demand.

In a typical browser setup, a script on the page requests bids from several partners in parallel, waits a short timeout and passes the results as key-values into the ad server request. Server-side variants move some of that work off the browser to reduce page load impact.

The advantage is competition: more bidders see each impression on equal terms, which can raise prices compared with a rigid sequence of calls. The cost is added complexity, latency and the need to monitor each partner.

Header Bidding vs Ad Server: Key Differences

The ad server decides and delivers, while header bidding gathers extra bids to inform that decision. One cannot replace the other: without an ad server there is no delivery and reporting, and without bids there is less competition.

Role

Header bidding is an auction mechanism. The ad server is the decision engine and system of record.

Where it runs

Header bidding runs in the page, in an app, or on a server. The ad server runs as a hosted or self-hosted service that the page calls.

What each affects

  • Revenue: header bidding adds competition, the ad server enforces priorities and floors.
  • Speed: header bidding adds a wait time, the ad server adds a call.
  • Reporting: the ad server usually holds the main numbers, so reconcile partner reports against it.
  • Control: the ad server governs direct deals, brand safety and frequency rules.

How the Two Fit Together in the Ad Flow

A common sequence is: the page loads, header bidding collects bids, the ad server receives the request with those bids as line items or values, picks the winner, and the creative is delivered and measured.

Ad servers differ in how they accept header bidding results. Some publishers create price-bucket line items for bids, while others use more direct integrations. Ask any vendor how it ingests bids, how it reports them and what limits apply.

Effective Revenue Gain = (New eCPM − Old eCPM) ÷ Old eCPM × 100%

Here eCPM is the effective revenue per thousand impressions. Compare the same pages and periods before and after adding partners, and adjust for any traffic loss caused by slower pages.

Latency, Privacy and Operational Tradeoffs

Every added bidder can add latency and privacy exposure. Set a strict timeout, limit the number of partners to those that deliver value and make sure consent signals reach every party that receives user data.

Slower pages can reduce viewability and user engagement, which offsets higher bids. Test timeouts and partner counts, and remove underperformers.

Consent is a legal topic as well as a technical one. Where consent is required, your consent management setup must pass choices to partners before bids are requested. Confirm obligations with your legal advisor.

Choosing the Right Setup for Your Publication

Small publishers can start with an ad server and a few demand partners, while larger ones add header bidding to broaden competition. The right setup depends on traffic, sales model, technical capacity and privacy obligations.

A simple decision path

  • Direct-sold only: start with an ad server that handles campaigns and reporting well.
  • Mix of direct and programmatic: add a small set of header bidding partners and monitor latency.
  • API-driven or custom products: consider a flexible platform such as Kevel.
  • Local news or magazines: consider products positioned for that audience, such as Broadstreet.
  • Budget-constrained: open-source Revive Adserver is free but requires self-hosting skills.

If you are replacing a system, our plan How to Migrate to a New Publisher Ad Server covers the steps, and Best Publisher Ad Server Software compares platforms.

Frequently Asked Questions

Do I need an ad server if I use header bidding?
Yes. Header bidding collects bids, but you still need an ad server to apply rules, serve direct campaigns, deliver creatives and report results.

Does header bidding always increase revenue?
No. It can increase competition and prices, but added latency, fees and operational overhead can offset gains. Test against a control and measure revenue and page speed together.

How many header bidding partners should a publisher use?
There is no universal number. Start small, measure each partner's bid rate, win rate and latency, and keep only partners that add revenue without hurting user experience.

Advertisement