Bid-Probability Pruning 13 Server Traffic Shaping Client Prebid Server Shaping Module Dropped Demand Partners 1 request 2 all bidders 3 low-prob dropped 4 pruned set 5 OpenRTB 6 bids 7 winner P_
Bid-Probability Pruning Server Traffic Shaping 13 Each bidder endpoint allows finite QPS. Every low-value call displaces a high-CPM one. At processed-auction-request, modules score bid probability per bidder — publisher, geo, device, fill history — and prune unlikely bidders from imp[].ext.prebid.bidder to pack the QPS budget with highest-probability, highest-CPM. FIELD NOTES → Low-fill traffic displaces high-CPM slots in the shared QPS budget → ML shaping cuts ~20% of calls with near-zero revenue loss → No native QPS cap — most hosts limit at the load balancer P_ atd.postindustria.com/13

How It Works

Each bidder endpoint allows finite QPS. Every low-value call displaces a high-CPM one. At `processed-auction-request`, modules score bid probability per bidder -- publisher, geo, device, fill history -- and prune unlikely bidders from `imp[].ext.prebid.bidder` to pack the QPS budget with highest-probability, highest-CPM.

Field Notes

  • Low-fill traffic displaces high-CPM slots in the shared QPS budget
  • ML shaping cuts ~20% of calls with near-zero revenue loss
  • No native QPS cap -- most hosts limit at the load balancer

Questions about Bid-Probability Pruning?

Get expert guidance from our team. We'll help you implement it.