Transparency
We wrote the exchange ourselves: the wire contract, the auction, the anti-fraud checks, the logging layer. So transparency here is not a promise about a black box, it is the same set of artifacts we operate on, published for anyone integrating with us.
Public files
The obligation runs both ways. A scheduled robot rechecks the ads.txt and app-ads.txt of every connected property, matches the declarations against the domains and app bundles that actually reach our endpoints, and writes the result into the publisher console. A declaration that does not resolve is a supply path we do not open.
Standards we comply with
How we treat traffic quality
Filtering happens before the auction, not after the invoice. Every request that reaches a downstream DSP has passed our inbound contract checks and the nine realtime anti-fraud checks, and every request that did not is still logged, with the reason it was stopped. The policy below states each control by name.
Nine realtime checks run on every inbound request, among them bot user agents, datacenter IP and ASN ranges, geo mismatch, duplicate requests, rate limits, Tor exits and managed lists. Each endpoint runs them in shadow or in block mode, so a partner can see exactly what would be cut before anything is cut.
Before any of that costs compute: device.ip and device.ua are mandatory, the user agent must resolve to our browser allow-list, and adult and illegal content categories (IAB25, IAB25-3, IAB26) are rejected on mainstream endpoints. Advertiser-domain blocklists (badv) are applied at the publisher level. What survives is enriched (GeoIP, browser and device classification) and routed to eligible demand.
Supply sources are re-scored hourly on a 0 to 100 scale, with quarantine before a ban, and the score is visible in the console rather than applied silently. Our impression and click pixels, win notices and per-request logs are structured for reconciliation by third-party verification partners engaged by our counterparties, and findings raised against our supply trigger a root-cause review.
Per-request audit trail
Each inbound OpenRTB request is written to a per-request funnel table in ClickHouse: request id, endpoint, publisher, format, geo, domain, selected demand feed, verdict (bid or no-bid), the reason code behind it, the winning price and the revenue share applied. Impression and click pixels, plus nurl, burl and lurl notices, land in the same store. When a partner asks why their traffic did not monetise, the answer is a query, not an opinion.
Reporting
Authenticated per-partner API over the same aggregates our own dashboards read: impressions, spend, revenue share and fill, broken down by publisher, zone, DSP, format, country and day.
Publisher and advertiser cabinets expose the numbers behind the invoice, sourced from the aggregation layer rather than a separately maintained marketing view.
Our counts are reconciled against DSP-side statistics, and Adbustr publishes the delta rather than absorbing it silently. Discrepancies are worked as engineering tickets against the raw logs.
Audit access
Active DSP partners may request log-level data access for reconciliation purposes under our standard audit protocol. Brand advertisers may request inventory breakdowns specific to their campaigns. Serving and data infrastructure run on dedicated servers inside an isolated private network; operator access goes through our own VPN, and a Data Processing Agreement covering GDPR and CCPA obligations is available on request.
See it on your own traffic
Every artifact on this page has a counterpart inside the console: the reason code behind each no-bid, the ads.txt verification status of each property, the cleared price behind each impression and the revenue share applied to it. Open an account and read them against your own requests.
Sign-up is three screens: email, password, code. The console opens immediately; traffic starts after review.