Multi-format RTB exchange · rtb.adbustr.com
Supply intake, auction, rendering, anti-fraud, analytics: one codebase, built and operated by our own engineering team. One integration; every request logged, every hop declared.
Sign-up is three screens: email, password, code.
Standards the exchange speaks
One OpenRTB 2.5 wire contract inbound and outbound, a SupplyChain object on every request, and seller declarations served at their canonical locations. See Transparency for the full list.
What you plug into
VAST tags, async banner tag, a 14 KB dependency-free player with six display formats, mobile SDK, Prebid, server-to-server feeds. Everything normalizes into one canonical request.
House campaigns and external DSPs compete in one real-time auction; bids normalized to a single currency at bid time; the decision takes tens of milliseconds.
schain on every request, published sellers.json, per-request verdict and reason in analytics. Partner numbers and ours reconcile line by line.
Under the hood
Four mechanisms of the exchange, named in enough detail that you can hold them against your own logs from the first day of traffic.
Bot UA, datacenter ASN, geo mismatch, duplicate requests, rate limits, Tor exits, managed lists (in shadow or block mode per endpoint). You see what would be cut before you cut it.
ClickHouse event pipeline; hourly marts power console reports nearly in real time: down to placement, creative and rejection reason. CSV export included.
We recheck every property on schedule and show the status in the console; buyers never guess.
Double-entry ledger, revenue share fixed at impression time, automated payouts with net terms.
Built for three sides of the exchange
Connect a site, an app or CTV inventory; get tags, player code or an OpenRTB endpoint; watch fill, eCPM and rejection reasons per placement. Payouts on schedule.
Banner, video, CTV, push, pop, native. Targeting by geo, device, OS, language, frequency, audience segments. Moderated inventory, transparent spend.
One OpenRTB endpoint, schain 1.0, cookie sync, QPS controls.
The console
Sign-up is three screens: email, password, code. The console opens immediately; traffic starts after review.
We are the exchange, not a reseller of one — so the path from publisher to DSP has a single node in it, and that node is us. A SupplyChain object travels with every outgoing request, seller and app declarations are served at their canonical locations, and every impression, click and win notice is written to our own logs against the request that produced it. Partner numbers and our numbers reconcile line by line.
sellers.json is live. app-ads.txt is current. schain ships with every bid request.
Integrating supply, evaluating us as a demand partner, or reviewing the wire contract before you commit engineering time: you will be talking to the team that wrote the exchange, not to a reseller.
Sign-up is three screens: email, password, code. The console opens immediately; traffic starts after review.
a@adbustr.com