Lead quality cannot be captured in a single number. Four KPIs tell the story together: whether your leads get accepted, why they get rejected, how fast they arrive and what they ultimately generate. Each has its own definition, and only by reading them side by side in your dashboard do you see the full picture of your operation.
accepted leads ÷ delivered leads
The share of delivered leads that a buyer in your operation actually accepts. This is the most direct measure of quality: a high acceptance rate means what you deliver matches what the buyer expects. Always measure per source and per buyer separately, since an average hides both your best and your weakest channel.
Rejection rate with reasons
rejected leads ÷ delivered leads, broken down by reason
The mirror image of acceptance, but only useful once every rejection carries a recorded reason (duplicate, out of target group, incorrect data, no valid consent). Without a reason you know that something went wrong, not what. With a reason you see exactly where to course-correct.
time between request intake and delivery to the buyer
How fast a request moves through your platform from intake to a buyer. Turnaround time affects quality directly: a lead that arrives too late is often already cold. Measure the median and the outliers: a good average can hide a long tail of slow deliveries.
Revenue per channel / buyer
revenue ÷ delivered leads, per channel and per buyer
The value a channel or buyer actually generates per lead. Only with this can you weigh volume against quality: a channel with high volume but low acceptance and low revenue often costs your operation more on net than a smaller, cleaner channel.
A KPI is only useful once you can break it down by origin. These four steps turn an average across your whole operation into a steering instrument per source.
01
Label every request at the source
At intake, attach a traceable source and label ID to every request: channel, landing page, campaign and publisher. Without that label your platform cannot break down a single KPI by origin afterwards.
02
Measure per source, not on the average
Calculate acceptance rate, rejection and turnaround time for each source and label ID separately. The average across your whole operation steers you the wrong way as soon as sources differ sharply in quality.
03
Record a reason for every rejection
Require that a buyer supplies a structured reason on rejection. Those reasons form the basis for traceable course-correction, and for an honest conversation with the publisher.
04
Compare over a fixed window
Look at the same period and the same minimum volume per source. An acceptance rate over twenty leads says little; over roughly 15,000 requests a month you see reliable patterns in your operation.
Put the KPIs side by side per source in your dashboard and the differences jump out immediately. Channel C may deliver the most volume, but accepts less than half, costs the most time and generates the least. An average across your whole operation would have quietly smoothed that tail away:
| Source / label | Acceptance | Rejection | Turnaround | Revenue / lead |
| Channel A · green label | 92% | 8% | 4 min | € 41 |
| Channel B · blue label | 78% | 22% | 11 min | € 27 |
| Channel C · orange label | 54% | 46% | 38 min | € 12 |
A rejection rate without context leads to a standoff: the buyer says “bad leads”, the publisher says “unjustified rejection”, and you as the lead generator are stuck in the middle without proof. Traceable provenance breaks that deadlock. Because every request carries a recorded source, a label and a consent record from intake in your platform, every rejection can be traced back to exactly where the lead came from and what was actually delivered.
Tie the structured rejection reason to that, and rejection becomes auditable instead of a disagreement. You see that rejections from channel C are 70% “out of target group” (a setup problem at the source), while rejections from channel B are mostly “duplicate”, which calls for deduplication. Each reason points to a different fix. And because the provenance sits traceably in your platform’s audit trail, that analysis is not contestable but demonstrable, to both your publishers and your buyers.
Volume is a tempting measure because it can always go up. But every rejected lead costs processing, trust and turnaround time, and drags down revenue per lead in your operation. Whoever steers on volume unintentionally rewards exactly the sources that deliver the most noise.
Steering on quality flips the incentive. You assess each source on acceptance rate, rejection reasons, turnaround time and revenue per lead, and in your platform you shift budget and routing toward the sources that perform on those KPIs. A smaller, cleaner channel with 92% acceptance and a high revenue per lead is almost always worth more than a large channel that sees half its deliveries fail. The act of measuring itself changes behavior: once a publisher knows rejection is traceable and visible, delivery improves at the source, before you even need to step in.
OXIAE is the operating system for lead generators: it labels every request on arrival with source, channel, campaign and publisher, and records consent and provenance by default, under your own brand. Acceptance rate, rejection with reason, turnaround time and revenue per channel and buyer therefore sit real-time per source and label in your dashboard, not as an average across your whole operation, but broken down all the way to the channel.
Because every rejection carries a structured reason and every event lands traceably in the audit trail, steering on quality in your platform becomes a matter of reading the numbers instead of investigating them. You then tie routing and payouts to those KPIs, so the publishers who deliver clean, accepted leads actually get priority and value, fully automated, within your own operation.
Note: the figures in this guide are illustrative and only serve to clarify the KPIs and how they relate to each other. Which acceptance rate, turnaround time or revenue per lead is achievable or healthy in your operation depends heavily on market, channel and target group, so use your own measured values as the benchmark.