Buyer tools

Is that supply path
paying for its QPS?

rCPM — also called RevCPM — is the QPS efficiency metric. Revenue per million bid requests. Not per impression. Per request, including every one that never bid.

$
Total revenue earned from the path
Total requests sent over the same period
rCPM
$27.78
Revenue per 1,000,000 bid requests
Per thousand requests
$0.0278
The same figure on a per-mille basis, if you need to compare
Requests per $1
36,000
How much throughput it takes to earn a dollar
rCPM = ( Revenue ÷ Bid Requests ) × 1,000,000
Why it matters

Every request costs QPS.
Only some of them pay for it.

QPS is finite

Throughput is the constraint, not inventory.
  • Both sides pay to process a request — the seller to send it, the buyer to evaluate it
  • Below a certain rCPM a path costs more to listen to than it returns

Impression CPM hides waste

It only counts the requests that won.
  • A path can post a healthy CPM while burning millions of requests that never bid
  • rCPM counts the misses, so two paths with identical CPMs can look very different

It exposes duplication

Resold inventory shows up in the maths.
  • The same impression offered through several hops multiplies requests without adding revenue
  • Falling rCPM at flat revenue is a supply path problem, not a demand problem

There is no universal “good” rCPM — it moves with channel, format, geo and season. What matters is the trend on a given path, and how it compares against the others competing for the same throughput.

Where HBX fits

We shape traffic so your rCPM goes up.

Traffic shaping
Requests with no realistic chance to win are never sent
rCPM controls
Thresholds set per bidder, so you decide the floor
Atomic QPS
Counted exactly — no overages, no silent throttling
Supply path targeting
Filter on s-chain node count and direct vs resold
Setup Deal Build a list in Forage