PROGRAMMATIC / Header bidding

Let demand compete. Keep your inventory in focus.

Explore a Prebid integration built around your placements, demand relationships and page experience.

Explore traffic & setup examples
PUBLISHER CONNECTIONmybestclick

Header bidding

Map your inventory
Validate the connection
Test and compare
A connected process. One step at a time.Illustration
HOW IT WORKS / 01
Map your inventory

Share your domains, ad units, sizes, current ad server and consent setup.

UNDERSTAND THE CHANNEL

What is header bidding?

Header bidding lets multiple demand sources bid for an ad opportunity before the publisher’s ad server makes its final selection. It is an auction workflow, not an ad format.

TYPES, PLACEMENTS & EXAMPLES

Three ways to connect an auction.

Header bidding describes how demand competes for a placement. These examples show different connection arrangements around the same publisher experience.

01BROWSER / PREBID.JS

Client-side display auction

A reader opens an article with a banner placement. Prebid.js requests bids from configured partners in the browser, then makes eligible bid information available to the publisher’s ad server for the final selection.

The placement keeps its page position. Check the configured sizes, auction timeout and actual rendering alongside the bids received.

02SERVER / PREBID SERVER

Server-side bidder connection

Instead of contacting every bidder directly, the website sends an auction request to Prebid Server. The server communicates with its configured demand partners and returns bids into the publisher’s selection workflow.

Confirm the server host, consent signals and bidder parameters. Moving requests off the browser still requires a compatible rendering setup.

03CLIENT + SERVER

A combined auction setup

A publisher uses browser connections for some bidders and a server connection for others. Both paths feed the planned auction workflow, while the visitor sees the selected creative in one ordinary page placement.

Compare the arrangements using the same placements and reporting definitions. More connections do not automatically mean better revenue or page performance.

Illustrative configurations. Bidder access, adapter support and the publisher’s ad server determine the final setup.

A PRACTICAL START

From your inventory
to an agreed integration.

01

Map your inventory

Share your domains, ad units, sizes, current ad server and consent setup.

02

Validate the connection

Agree the adapter, bidder parameters, demand access and auction timeouts.

03

Test and compare

Start with a measured placement test and compare yield alongside page performance.

CONTROL AND CLARITY

Know what you’re
working with.

Your integration controls

  • Placement and size mapping
  • Bid floors and auction timeouts
  • Demand eligibility
  • Browser and consent context

Measure what matters

Evaluate bid rate, win rate, rendered impressions, revenue and page experience together. A winning bid is not the same as a rendered impression.

Adapter compatibility and demand access are confirmed during onboarding. Connecting Prebid does not automatically grant access to every demand partner.

BEFORE YOU START

Your questions,
answered.

Can I keep my existing ad server?+

We review the current ad server and auction flow before recommending an integration. Share your setup with the publisher team.

Is header bidding the same as OpenRTB?+

No. Header bidding describes the auction arrangement. OpenRTB is a protocol used to exchange bid requests and responses.

A BETTER CONNECTION STARTS HERE

Let’s talk about header bidding.

Tell us about your website, audience and current setup. We’ll map the next step together.

Talk to our team
YOUR PRIVACY CHOICES

Choose whether to allow the optional services below. They stay blocked until you opt in. You can change or withdraw your choice at any time using Cookie settings.

Cookies policy · Privacy notice