Publishers can connect directly to DSPs

"Will this actually make me more money?"

We are not going to quote you an uplift percentage. Nobody can honestly quote one before seeing your traffic, and a number invented for a landing page tells you nothing about your inventory.

What we can tell you is the mechanism, and you can judge it.

Enrichment comes first, before the auction, on every request. Every request is geo-resolved in real time with Floxis GeoIP, down to country, region and city — a request without geography is one buyers cannot target or price properly. Server-side and pixel user sync lifts your match rates, and it works with the IDs you already run: UID2, ID5, RampID, hashed email. A buyer that recognises the user bids more often, and higher, on the very same impression. Same traffic, same page, same impression — worth more, because more buyers can price it.

Then the auction decides what to do with it. Your demand partners are called with a 200–300 ms bid timeout, and floors, scoring, blocking and shaping run inside that window, learned per segment. Every lever runs Off → Shadow → Enforce, measured against a live holdout — arm 0, the exact status quo. Your manual floors always win; the engine only ever raises above your minimum. If a test arm's bid rate falls below 80% of the holdout, Enforce auto-reverts to Shadow. Uplift is proven, not assumed.

There is no language model anywhere in that path, deliberately. A language model cannot run inside a 200 ms auction. Statistics decide; language models explain, afterwards.

"How much work is this for my team?"

The integration work is the part we take. Standard partners connect over the protocols above; a non-standard partner gets an adapter we build and maintain, with white-glove onboarding.

OpenRTB for publishers, Prebid.js and Prebid Server — what actually happens to one request

1. 1 It arrives. Your page, app or player calls Floxis over OpenRTB 2.5/2.6, through Prebid.js, through Prebid Server, as a VAST call or a JS tag. Display, video, native, audio or CTV.
2. 2 It gets enriched, before the auction. Floxis GeoIP resolves country, region and city, added to every request with no integration work on your side. Server-side and pixel user sync attaches the IDs you already run.
3. 3 It runs inside your limits. Per-endpoint QPS, spend caps and timeouts keep every partner inside its limits. Allow and block lists across domain, bundle, publisher, CRID, IP, device and ad markup filter exactly what you want, where you want. Supply Path Control lets you define and enforce preferred demand paths server-side, while respecting auction priorities and partner relationships. By default we append our node to the supply chain and leave the rest of it intact.
4. 4 The auction runs, and clears at your rate. Floors, scoring, blocking and shaping run inside the 200–300 ms demand bid timeout. You set the rate per endpoint and it is applied when the bid clears — not reconciled afterwards in the reporting layer.
5. 5 It goes back to your ad server. The winning bid returns to your ad server, which retains final decision-making and delivery.
6. 6 About a minute later, it's on the record. Every bid, win and drop is logged and exportable, with drop reports that show exactly why a request was filtered.

After that you operate it from your own dashboard — floors, rates, per-endpoint QPS, timeouts, shaping, filtering — and we keep doing the integration work as you add partners.

The Floxis AI assistant is the extra pair of hands underneath that. Ask your exchange why something changed and get an answer you can open and check: it reads your own log-level data — partner health, drop reasons, unsold inventory, live configuration — and does the finding-out, so your team does the deciding. Read-only: it investigates and recommends, you make the change.

"What happens when it goes wrong?"

You get the record, not an explanation. Every request, bid and drop is logged and exportable, about a minute after it happens, with drop reports that show exactly why every request was filtered. Win rate, latency and drop reasons are broken out per demand partner, so a degrading partner shows up as a row, not a hunch. When a partner disputes a number, it is settled against the log-level record on both sides of the auction instead of argued. Full log-level data. No hidden ad-tech tax, no black box.

On traffic quality: Floxis invalid-traffic filtering runs on your traffic as standard. If you already run your own provider, we integrate it on top. For creative verification, you bring your provider and we integrate that.