Connected DSPs
Several buyers can bid on the same impression.
Header bidding & OpenRTB
Standards-based programmatic demand
MS Ads Network speaks OpenRTB 2.6 to connected DSPs, runs second-price auctions with per-unit floors, and keeps the supply path transparent with ads.txt and sellers.json.
Overview
Open, standards-based demand
Your ad requests are sent to connected DSPs as OpenRTB bid requests, so several buyers compete for each impression instead of one closed network.
Capabilities
What you get
OpenRTB 2.6
Banner, native, push and pop requests to connected DSPs.
ads.txt & sellers.json
An ads.txt line for every approved site.
Server-side feeds
XML/JSON demand feeds as backfill when no DSP wins.
Prebid.js adapter Coming soon
Client-side header bidding adapter.
How it works
Under the hood
FAQ
Header bidding & OpenRTB questions
Can I connect my own DSP?+
Yes — DSP partners connect through an OpenRTB endpoint; contact us for the spec.
Do you support Prebid?+
A Prebid.js adapter is planned and marked as coming soon.
For publishers
What OpenRTB means for you
Your inventory is offered to several buyers at once instead of one closed network. Standard requests and transparency files make it easier for new DSPs to buy from you.
XML/JSON backfill
Server-side feeds can fill requests when no DSP wins.
Supply transparency
ads.txt, sellers.json and the SupplyChain object show buyers the full path.
FAQ
Frequently asked questions
Do I need to set up header bidding?
No. Our tag handles the auction server-side. A Prebid.js adapter is planned for publishers who want client-side header bidding.