Is your lead distribution software a marketplace, or do we control our own buyers?
It is a private lead distribution platform, not a marketplace. Many companies use the platform, but each has its own private tenant (account space). Your buyers and call centers live inside yours and get leads only from you. There is no shared marketplace, and no outside party ever sees your leads.
Can I run a lead aggregator business on this?
Yes. That is the model the platform is built around. Partners post leads under their own campaigns and keys. Your contracts decide which buyers each lead is sold to. The same lead can go to one buyer only, to every eligible buyer, or to a set number of them. The price is recorded on each sale next to the routing decision behind it. The optimization and anomaly views watch margin per sale for drift.
Related: Waterfall Routing
What distribution logic is supported?
Common rules include priority, round robin, weighted random, and price. Other rules use quality, available supply, or past revenue. Filters, schedules, balances, and caps decide which buyers can take the lead before ranking.
Related: Waterfall Routing
Are there distribution rules beyond priority and round robin?
Eight in total: price, priority, weighted random, round robin, quality tier, scarcity-weighted, revenue-per-lead, and weighted revenue-per-lead. Scarcity-weighted paces delivery by how scarce leads are in each state and ZIP right now. So hard-to-fill areas are not drained by whichever buyer has the largest cap. The two revenue-per-lead rules rank buyers on what they actually return per lead over a recent window, not on their posted price.
Related: Waterfall Routing
Can different lead types have different rules?
Yes. Rules live on the offer, so each lead type runs as its own offer with independent rulesets, caps, and buyer lineups.
What happens when a buyer is at capacity or offline?
Automatic waterfall. The engine moves to the next eligible buyer in real time, and every step is logged so you can see exactly why each lead landed where it did.
Related: Caps & Capacity
Can we prove why a lead went to one buyer and not another?
Every contract the engine checks gets a record: eligible, skipped, or rejected. The record names the reason and shows what each filter expected and what it found. The full list stays on the lead, so any routing decision can be rebuilt months later.
Related: Waterfall Routing
How granular can buyer filters get?
Three layers per contract: location (state allow or exclude lists plus ZIP-prefix targeting), demographics, and custom rules on any field in your lead data, including nested fields. Rule types include equals, in, not in, contains, greater than, less than, and empty or not empty.
Can we filter on a relative date, like a bankruptcy older than two years?
Yes. Date rules accept relative terms such as “2 years ago” or “6 months ago”. A contract’s rules then stay correct on their own. Nobody has to edit a fixed date every month.
Can we stop sending leads to a buyer outside their business hours?
Yes. Each contract carries a weekly hours-of-operation schedule evaluated in that buyer’s own timezone, including overnight windows that cross midnight.
Can we cap a buyer by volume and by spend, and whose timezone do caps use?
Both, and each is set on its own. Each contract can have a lead-count cap and a dollar spend cap for hourly, daily, weekly, and monthly periods. Periods reset in your account’s timezone, not UTC.
Related: Caps & Capacity
Under a burst of traffic, can a buyer be pushed past its cap?
No. The cap counter goes up at the moment of sale, and the limit is checked in that same step. So two leads arriving at the same time cannot both slip through. If that sale later fails, the cap slot is given back on its own.
Related: Caps & Capacity
Can we map our field names to each buyer’s field names without custom code?
Yes. Delivery is set up per contract. Each buyer gets its own field mapping and default values. There are over 50 built-in transformers for things like letter case, math, dates and age, timezones, text changes, encoding, if-then rules, and state expansion. All of it is set from the UI.
Related: Integrations
How do you know whether a buyer accepted or rejected a lead?
We check the body of the buyer’s response against rules you define, not just the HTTP status. So a 200 response that says “rejected” inside counts as a rejection. Values from that response are saved on the sale, including the buyer’s own lead ID and any changed price they send back.
Related: Integrations
Can we test a buyer integration before sending live traffic?
Yes. A test delivery sends a real request through the same mapping path used in production, with the same transformers and defaults. It shows you the exact URL, headers, and body that were sent, next to the buyer’s response.
Related: Integrations
Do you retry a failing buyer endpoint, or keep sending into a black hole?
Failed deliveries can be retried, with a longer wait after each try (exponential backoff). Delivery health monitoring pauses an endpoint that keeps failing instead of wasting leads on it.
Related: Integrations
What happens if every eligible buyer rejects the lead?
The lead falls through to your configured DQ contracts, so it can still be sold rather than discarded. An operator can re-deliver it or hand-pick a buyer for it afterwards.
Related: Waterfall Routing
Still have a question?
Pricing is one monthly plan plus published usage rates. Use the setup tools and guides. Some buyer connections need custom field mapping or API work.