What is Floxis AI Booster?
Floxis AI Booster is the premium optimization engine for a demand endpoint. It learns what each buyer bids on and wins, sends more of that traffic and less of the rest, and adds learned price floors and blocking of weak segments on top. It is tested against your current endpoint and is in early access today, not open to every client.
What problem does it solve?
Most buyers cap the requests per second they accept, and most of what an exchange sends never gets a bid. When a cap binds, the requests that get through are effectively picked at random, so a request the buyer will never answer takes the place of one it would have bid on.
Even without a binding cap, every unanswered request costs both sides parsing and connection time, and buyers notice. Our guide to RTB traffic shaping covers the economics in more detail.
What does AI Booster do?
It runs three things on the endpoint you choose.
- Per-buyer scoring. It ranks each request by how likely that buyer is to bid on it, sends more of what the buyer bids on and wins, and sends less of the rest.
- Learned floors. It sets price floors per segment from what that buyer’s traffic has actually cleared at.
- Segment blocking. It blocks segments with poor demand economics for that buyer.
It also backs off by itself if results get worse. All of it is measured against your current setup.
How does it work, one bid at a time?
- A bid request arrives from your supply and is matched to a demand endpoint.
- AI Booster scores it against what that buyer has bid on before: format, geography, device and similar traits.
- Requests the buyer is likely to answer are sent. Low scorers are sent less often.
- The floor and blocking levers apply to the request’s segment.
- The buyer’s response, or its silence, feeds back into the score for the next request.
- Results are compared with your original endpoint, which keeps running without AI Booster.
Scoring is per buyer. What one buyer bids on says nothing about another.
What do you control?
You switch AI Booster on or off from the Demand list, per partner or per endpoint. Switching it on creates a copy of the endpoint that receives a share of traffic, 20 percent by default, and you can change that share while it runs. Your original endpoint keeps the rest.
Results come with a significance read. Nothing is promoted automatically: you decide whether to keep AI Booster on or switch it off, and switching it off returns you to the original endpoint.
Every Floxis client already has a basic Optimizer switch per endpoint. AI Booster is the premium engine on top of it, and it is the part in early access.
What does it not do?
- It does not set bid prices for the buyer.
- It does not guarantee more revenue. Where an endpoint is nowhere near its cap, the likely gain is fewer wasted calls, not more money.
- It does not detect fraud. Floxis IVT filtering is a separate layer, on by default.
- It cannot find demand that is not there. If a buyer almost never bids on an endpoint, there is little to learn from.
- Your manual floors still win. The engine only raises a floor above the minimum you set.
What should a CTO know?
AI Booster sits in the path where Floxis already decides where a request goes, and it learns from the bid responses Floxis already sees. There is nothing to install on the publisher side and no new data feed to hand over.
We have not published latency figures for it, so we do not quote any. Ask on the demo and we will bring measured numbers for your traffic mix.
What should a CEO or CFO know?
The money question is whether capacity and price floors are working on requests that earn. The risk question is what happens if it does not work. The paired original endpoint answers the second, because it keeps a share of traffic running the old way and the gap is visible. Switching it off is one setting.
We are not publishing uplift numbers yet. Early access means results are still being built, and we will not put a figure on a page before it is real.
Who is it for?
Publishers, networks and agencies running their own exchange on Floxis, especially those whose buyers enforce a QPS cap or who send large volumes of traffic that rarely bids. For the wider picture of how shaping fits with floors and margins, read our yield optimization guide and our bid floors guide.
How do you get started?
AI Booster is offered by request during early access. Book a demo, tell us which buyers you want to test it on, and we will set up the split with you.
FAQ
Is Floxis AI Booster available to every client?
No, it is in early access and offered by request. Every client already has the basic Optimizer switch, and AI Booster is the premium layer on top.
Will AI Booster increase my revenue?
It might, but we do not promise it. Where a buyer’s cap binds, sending better requests can raise revenue. Where it does not, the main benefit is fewer wasted calls. The paired test shows which case you are in.
Can I test it before using it on all my traffic?
Yes. AI Booster runs on a copy of the endpoint that gets a share of traffic you set, and your original endpoint keeps the rest.
Does AI Booster replace my price floors?
No. Your manual floors always win. AI Booster adds learned floors per segment, and it only raises above the minimum you set.
What happens if it performs worse than my current setup?
You switch it off and traffic returns to your original endpoint. Because that endpoint keeps running alongside it, you see the shortfall while it is happening.