For publishers
Adbustr aggregates your remnant video supply into a single exchange that routes performance demand directly to it. Supply is transacted today over our web endpoints as OpenRTB site inventory — VAST, VPAID, banner, ADM, popunder and server-to-server. Floors and demand routing you control per zone, Net-45 settlement, and zero hidden mediation tax.
Why publishers choose Adbustr
We don't resell — we exchange. Your request fans out in parallel to every eligible DSP inside your tmax and clears second-price by default, never below your floor. One hop, one supply chain object, no mediation cascade eating your margin.
Net-45 from end-of-month, on impressions already reconciled against our own event logs. Your payout is revenue multiplied by the revenue share configured on your endpoint, with per-country overrides applied by ISO2 — read from configuration, never hardcoded, and written into the contract before you send a single request.
VAST tag, JS/iframe banner, VPAID, ADM JSON, popunder feed or OpenRTB server-to-server. Our Unity and Android SDK is in pilot and not yet transacting app-object inventory. No mandatory exclusivity: run us alongside your existing mediation stack.
Why we're different
The ad-tech industry trained publishers to expect undisclosed net revenue, clawback settlement, post-bid fraud reporting, and exclusivity demands. We rebuilt every one of those defaults.
Dimension
Most SSPs
Adbustr
Revenue share
Black-box net revenue · effective rate discovered after the fact
Base share on your endpoint plus per-country (ISO2) overrides · stated in the contract
Settlement
Net-30 with rolling clawback windows
Net-45 from end-of-month on reconciled impressions · adjustment terms fixed in the contract
Traffic quality
Post-bid IVT reporting · the invalid impression was already paid for
Pre-bid: IP/UA presence, browser allow-list, IAB25 / IAB25-3 / IAB26 block — every rejection reason-coded in the log
Control
One floor, one switch · take the waterfall as configured
Per-zone and per-DSP floors, BidRate, ReqFilter, DSP allow/block, tmax, maxqps
Mediation friction
Exclusivity or a heavier rev-share as the price of waterfall access
Runs alongside your existing mediation stack · no exclusivity
Supply path visibility
schain truncated · undisclosed resellers · opaque bid stream
SupplyChain object (schain 1.0) on every demand request · published ads.txt, app-ads.txt, sellers.json
Integration paths
Every path below terminates in the same auction, with the same supply chain object and the same reporting. Pick the one your player, wrapper or app already speaks — you don't rebuild your stack to reach our demand.
What you control
Configuration is modelled as Publisher → Zone → per-DSP settings, and it lives in a hot-reloaded snapshot: changes take effect without a restart and without waiting for a release window. Zone-level settings can extend the defaults or replace them outright.
Floors
bidfloor per zone and per DSP, in your currency. Bids normalized to the base currency below that floor never enter the auction.
Demand routing
DSP allow-lists and block-lists per zone. BidRate normalizes how aggressively each partner bids at ranking time; ReqFilter throttles the share of requests a given DSP sees.
Latency budget
tmax set at publisher, zone or request level — 300–500 ms by default. Fan-out is parallel and late responses are discarded, so your player never waits on a slow bidder.
Load
maxqps caps the request rate we accept on your endpoint. Anything we don't fill comes back as 204 No Content, so your player falls through to its next line immediately.
Live toggle
Demand fan-out flips on and off instantly through the config snapshot, with no restart. While it's off we still accept and log your traffic — fail-safe by default.
Revenue share
A base percentage on your endpoint plus per-country (ISO2) overrides. Payout is revenue times the share that applies to the request's geo.
Brand safety
Advertiser-domain block-list (badv) at publisher level, IAB categories declared on the zone, and imp.secure carried through so HTTPS inventory gets HTTPS creatives.
Reporting
Impressions, clicks, wins and losses are logged per request and surfaced in your dashboard by day, zone, format, geo and demand partner — plus a reporting API for your own BI.
Settlement cycle
We use the monthly cycle to reconcile delivered impressions against our own event logs — every impression, click and win notice is recorded per request — then settle on day +45. Adjustment terms are written into the contract, not discovered in the statement. Tier-1 SSP cadence, not arbitrage Net-7 hustle.
What moves eCPM
Anyone quoting you a headline eCPM before seeing your traffic is quoting someone else's inventory. What you earn is set impression by impression, by the bids that clear against your floor. These are the levers that actually move it — and where each one is configured.
Lever
What it moves
Where it's set
Format and environment
In-stream video, VPAID, banner, ADM and popunder clear against different demand pools and different creative economics.
Zone format
Geography
Country is resolved per request from the client IP. Demand selection and revenue share both branch on ISO2, so the same impression prices differently by market.
GeoIP · per-country (ISO2) share
Floor granularity
A single blanket floor leaves money on the table. Floors set per zone and per DSP let you push high-intent inventory up without suppressing fill on the rest.
bidfloor (zone / PubConfig)
Demand coverage
How many DSPs are eligible for the zone after geo, device and allow / block filtering. BidRate normalizes how aggressively each partner bids; ReqFilter throttles the share of requests they see.
DSP lists · BidRate · ReqFilter
Auction timeout
Fan-out is parallel, but responses arriving after tmax are discarded. A tighter tmax buys player latency at the cost of auction depth; 300–500 ms is the default working range.
tmax (publisher / zone / request)
Traffic quality
Requests without device.ip or device.ua, user agents outside the browser allow-list, and IAB25 / IAB25-3 / IAB26 categories are rejected before fan-out, each with a reason code in the funnel log. See our Anti-Fraud Policy for what these checks do and do not cover.
Inbound request validation
Clearing model
Second price by default (at=2), bounded below by your floor and above by the winner's own bid. First price (at=1) is available where a demand partner requires it. The clearing price per request is in your event logs.
Auction config
We don't publish benchmark eCPM ranges. Effective CPM is priced per impression by the bids that clear against your floor, so a headline number tells you nothing about your inventory. Realized eCPM by day, zone, format, geo and demand partner is in your dashboard and reporting API from the first day of traffic.
Revenue model
Slide in your monthly impressions, pick the dominant format and audience geo. The output is a directional model built on indicative industry assumptions — not a rate card and not a quote. Your revenue share, including per-country terms, is agreed during onboarding and stated in the contract.
Revenue estimator
Mid-range eCPM × your monthly impressions, cleared in an impression-priced auction. Your payout is this gross less the revenue share set in your contract. Formats shown are the video paths we serve today; in-app formats are not modelled because app-object bidding is not live.
Estimated gross auction revenue
$42,000
~ $504,000 annualized gross
What we accept
Adbustr aggregates the long tail of video supply that the largest mediation platforms underserve. If your inventory is video-shaped and reachable over one of our web endpoints, we can route demand to it. One technical caveat, stated up front: every request we surface to buyers today carries an OpenRTB site object. App-object bidding — and with it app.bundle targeting and app-ads.txt resolution — is not implemented yet, so CTV and in-app supply monetises through the web paths in the meantime.
In-app SDK — pilot
Built for production gaming, OTT and CTV environments: Unity 2021.3 LTS+, Android minSdk 21, and zero external dependencies — nothing in your dependency graph you didn't already have. Rewarded video, interstitial and native, authenticated with your application key and identified by sid and zone. The SDK path is in pilot: requests it generates are transacted as site inventory until app-object bidding ships, so app.bundle targeting is not available to buyers yet.
SDK technical specs
Drop into existing build. No mandatory exclusivity. Runs alongside any major mediation adapter without conflict.
Mediation compatibility
Integration in three steps
01
Send us your supply profile: platforms, formats, geo mix, monthly volume, and which integration path you want. We typically respond within one business day.
02
We complete a streamlined Know-Your-Business review focused on app legitimacy, ads.txt/app-ads.txt presence, and technical fit. Most legitimate publishers complete this in under 72 hours.
03
We issue your publisher and zone configuration plus the endpoint for your chosen path. Integration guides cover the VAST, banner, ADM, popunder, OpenRTB and SDK contracts; a GET on your OpenRTB endpoint answers as a ping, so you can validate connectivity before demand fan-out is switched on.
Qualification
We're selective on the way in so we can be predictable on the way out. Every publisher gets the same integration paths, the same controls and the same settlement cadence — the variability we control is who qualifies.
Below threshold? We onboard a small batch of growth-stage publishers per quarter via our pilot program — same integration paths, same controls, same Net-45, lower volume bar. Mention "pilot batch" in your inquiry.
Brief us on your supply and we'll respond within one business day with an inventory and pricing fit analysis.