Ad Demand Integrations
Header bidding partners (SSPs) in Fusion
Ad demand integrations are the header bidding partners, or SSPs, that bid for your ad space before your ad server's final auction. Fusion runs them through Prebid.js in the browser, Prebid Server on Content Ignite's servers, Amazon APS or PubMatic OpenWrap. You add a partner by dragging it into an ad stack, and Fusion handles the on-page set-up and reporting.
Setting it up in Fusion
- 01Choose whose demandUse the SSP relationships Content Ignite has in place, connect your own SSP accounts in Integrations, or mix the two.
- 02Drag partners into an ad stackPartners marked Prebid Server run on our servers with no extra set-up. Amazon APS and OpenWrap go in as single entities.
- 03Fusion deploys it on the pageOn Content Ignite's Google Ad Manager nothing else is needed. On your own GAM, Prebid needs price-priority line items (APS creates its own).
- 04Check what each partner earnsRevenue, bid rates and win rates for each partner are in Fusion reporting and SSP Insights, and you can A/B test partners with experiments.
Header bidding partners in Fusion
Questions, answered
What is the difference between Prebid.js and Prebid Server in Fusion?
Prebid.js runs the header bidding auction in the visitor's browser. Prebid Server moves the auction to servers hosted by Content Ignite, which takes load off the browser. In Fusion you add Prebid Server partners to an ad stack the same way, with no extra set-up.
How many header bidding partners should I use?
Enough for competition, but not so many that pages slow down: header bidding adds work in the browser and can affect Core Web Vitals. SSP Insights shows which partners earn their place, and bid throttling can drop weak SSPs from the auction for a given user.
Can I use my own SSP accounts?
Yes. Connect your own SSP relationships, use the ones Content Ignite has put in place, or mix the two. See header bidding in Fusion for how the auction works.
How are ads.txt lines handled for each partner?
Each integration can carry its ads.txt lines. When it is in an ad stack, publishers see those lines as go-live requirements, Fusion checks every site's ads.txt daily and sends a weekly report of missing lines. See ads.txt Insights.
Want a second opinion on your ad stack?
Get a free Revenue Healthcheck: your ad set-up, header bidding and Core Web Vitals scored and benchmarked against similar publishers.