Monetisation

Header bidding: every bidder in one auction, from one tag

Header bidding lets several SSPs bid on each impression before your ad server decides, so Google Ad Manager has to beat the best outside price. Fusion is a header bidding wrapper: one tag runs Prebid, Prebid Server and Amazon alongside Google AdX and Open Bidding, with bid throttling, timeouts and reporting managed for you.

How it works

One auction, every bidder

  1. 01
    Bidders compete first
    When the page loads, the tag asks your Prebid SSPs and Amazon for bids at the same time, in the browser or on our Prebid Server, within a set timeout. Bid throttling leaves out SSPs that rarely bid for that user.
  2. 02
    The best bids go to Google Ad Manager
    Winning header bids are passed to your ad server as key-values, ready to compete in the final auction.
  3. 03
    Ad Manager picks the winner
    Header bids compete with Ad Exchange, Open Bidding and your direct campaigns. If nothing fills, a second ad server or your own fallback creative can take the slot.
Demand sources

Prebid, Amazon and Google, side by side

Each source reaches buyers in a different way. Fusion runs them together and reports on all of them in one place.

Demand sources in Fusion: where each auction runs, its effect on the page and whose contracts it uses
SourceWhere the auction runsEffect on the pageWhose contracts
Prebid.jsIn the visitor's browserUses browser resources, so keep the SSP count and timeout in checkYour SSP contracts, ours, or both
Prebid ServerOn Content Ignite's serversMinimal: the heavy lifting happens server-side, with no extra set-upAny partner marked "Prebid Server" in Fusion
Amazon TAM / UAMOn Amazon's servers, called from the pageMinimalOurs (approved per publisher) or your own APS account
OpenWrapIn the browser (PubMatic's Prebid build)As Prebid.js; can't run alongside PrebidOurs, set up by our ad ops team, or your own PubMatic account
AdX and Open BiddingInside Google Ad ManagerNone beyond the ad requestThrough your Google Ad Manager or ours
Your demand, ours, or both

Keep your contracts, use ours, or mix them

Fusion doesn't ask you to change how you work. Choose per site which ad server and demand to use.

Plug & Play: our demand

Use our Google Ad Manager and SSP relationships. Our team manages demand, and you are paid a revenue share on Net30 terms, with invoices raised for you each month.

Self-Service: your demand

Connect your own Google Ad Manager and SSP contracts for a CPM fee. Prebid needs price-bucket line items in your GAM (or GAM 360 header bidding trafficking); Amazon sets up its own.

Hybrid: both

Put both ad servers in your ad stack. If the first doesn't fill, the tag passes the impression to the next, with no passback tags or extra set-up in GAM.

Not sure which suits you? Google Ad Manager with Fusion explains each set-up, and ourmanaged ad operations team can run either for you.

Control

Header bidding without the maintenance

The settings that usually take weeks of development are a few clicks in Fusion, and every change is measured.

FAQ

Header bidding questions, answered

What is header bidding?
Header bidding is an auction that runs before the ad server. When a page loads, several SSPs (supply-side platforms) are asked to bid on each ad slot at once, and the best bid is sent to the ad server, usually Google Ad Manager, to compete with its own demand. Because Google has to beat the best outside price, publishers typically see more competition and higher CPMs.
What is a header bidding wrapper?
A wrapper is the code and settings that run the header auction: which bidders take part, how long they have to bid, and how winning bids reach the ad server. Fusion is a header bidding wrapper built on Prebid, delivered through one tag and managed from a drag-and-drop ad stack.
What is the difference between header bidding and Google Open Bidding?
Header bidding (Prebid, Amazon) collects bids before the ad server is called, from SSPs you choose. Open Bidding is Google's server-side equivalent, where exchanges bid inside Google Ad Manager alongside Ad Exchange. They work together: in Fusion, header bids compete with AdX and Open Bidding in the same Google Ad Manager auction.
What is the difference between Prebid.js and Prebid Server?
Prebid.js runs the auction in the visitor's browser. Prebid Server moves it to servers hosted by Content Ignite, which takes the load off the browser. In Fusion you don't set anything up: partners marked "Prebid Server" run server-side as soon as you add them to your ad stack.
How many SSPs should I run?
Enough for competition, but not so many that latency rises and returns diminish. More SSPs can lift CPMs and fill; too few limits competition and demand diversity. Bid throttling removes SSPs that underperform for each user, and SSP Insights shows bid and win rates per partner so you can decide who stays.
Does header bidding slow down my site?
Client-side header bidding uses browser resources and can affect Core Web Vitals if it is overloaded. Fusion limits this with Prebid Server, Amazon's server-side auction, bid throttling and a tuned timeout, and ad units can be set to load and refresh only when they are in view. See Core Web Vitals.
Can I use my own SSP contracts and Google Ad Manager?
Yes. Fusion works with your SSP contracts and Google Ad Manager (Self-Service), ours (Plug & Play), or both, where one ad server gets first look and the other a second look. If you use your own GAM with Prebid, you'll need Prebid line items set up once; Amazon creates its own.
Can I run Prebid and OpenWrap together?
No. OpenWrap is PubMatic's version of Prebid.js, so they are alternatives. We recommend Prebid directly, because Fusion gives you more control over each partner, including experiments between different demand set-ups.

See how your header bidding stacks up.

A free healthcheck reviews your Prebid version, SSP line-up, timeout and Amazon set-up, or sign up and add your first SSPs today.