In-stream video
Pre-roll, mid-roll and post-roll inside your own player via VAST.
Six formats through one integration. Our own auction and anti-fraud, direct in-house sources, and impression-level logs behind every line of the report.
Sign-up is three screens: email, password, code.
Ad formats
One async tag, our 14 KB dependency-free player or a Prebid adapter in your header auction. Six display modes out of the same script, plus classic display and pop.
Pre-roll, mid-roll and post-roll inside your own player via VAST.
Video where there is no video: the unit builds its own slot in the article.
Rides in from the corner and follows the reader down the page.
Sits in the content flow, plays on view, collapses when it ends.
The page scrolls, the creative stays: a window cut into the article.
Pinned to the viewport corner, dismissible, never blocks the text.
Takes the viewport on a transition, hands it straight back.
A fixed slot you place yourself, sized by you.
Our Prebid adapter bids in your header auction alongside everyone else, before the ad server call.
IAB sizes through an async tag, rendered in a sandboxed srcdoc iframe.
Native-looking notification, delivered without the browser prompt.
Opens behind the active tab, surfaces when the reader is done.
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.
Pricing models
Pay per impression
The default for video, CTV and display. Bids normalize to a single currency at bid time, and the revenue share is fixed at the impression.
Pay per click
For push, pop and native, where the click is the event that matters. Click ids travel into your tracker through postbacks.
Pay per action
Postback-driven, on your side of the funnel. AppsFlyer, Keitaro, Binom and Voluum carry the conversion back to us.
Billing ticks, CPC against CPM
What makes us different
A multi-level stack runs on every single request: bot signatures, datacenter ASNs, geo mismatch, duplicates, rate limits, Tor exits and managed lists. Shadow mode shows what would be cut before you cut it.
Geo down to city, device, OS, browser, language, connection type, frequency caps, audience segments, per-placement allow and block lists.
Rules watch delivery and act on it: bid, budget pacing, source scoring, quarantine and rotation. The operator sets intent, the platform holds it.
Both models are first-class across every format. Bids normalize to a single currency at bid time, and the revenue share is fixed at the impression.
Behavioural segments with time windows, built in-house. You see what the traffic is made of, not a vendor's black box.
Rebuild reach on audiences that already met the brand. No vertical lock-in: the mechanism is the product, the use case is yours.
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 and QPS controls. Connect your own demand stack and bid alongside house campaigns.
Real-time bidding
A supply call arrives, normalizes into one canonical request and fans out to connected demand. Bids come back, the auction clears, the winning creative renders. Nothing about that path is hidden from the people on either end of it.
What runs here
Category is read from site.cat and site.sectioncat on the way in. A refusal is written to the funnel log with its reason code, so the number you see and the number we see come from the same row.
Accepted
Mobile apps and games
In-app video, rewarded, interstitial, banner and native through our SDK or s2s.
Connected TV
Pre-roll and mid-roll pods, measured on impressions and completion.
Web media and content
In-stream, out-stream, six player display modes, banner and HTML.
Utilities and tools
Push, in-page push and popunder, capped per session.
Refused inbound
reason code: non_mainstream
Tracking
Postbacks carry click id, campaign, placement and payout into the stack you already run. No re-keying, no spreadsheet reconciliation at the end of the month.
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.
Questions
Let's meet
Affiliate World Mexico
Affiliate World Asia
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.
ask@adbustr.com