The friction
A lost bid is a mystery: no visibility into what was received or answered.
With Moja
The lifecycle log holds every event of the request, parameters included.
Platform · Real-time bidding
The marketplace, with the lights on.
RTB is where calls become trades: a ping arrives, a bid answers it, a call follows or doesn't. Moja runs that loop and — unlike most of the category — shows you every event of every request, so you can see why a trade happened.
RTB runs on the same tracking and routing foundation, which is why every bid decision is inspectable after the fact.
The working path
From input to next step.
Ping to bid to call, and the accounting around each step.
- 01
A ping arrives; a bid answers.
Inbound requests carry the caller's parameters — caller ID, geography, and whatever the publisher passes. Your bid logic decides bid or no-bid against your targets and budgets, and the response goes back while the caller is still on the line.
- 02
Every request is logged, end to end.
Each request keeps its full lifecycle: the HTTP exchange, the parameters received, the bid decision, the target and caller ID allocated, the call that followed, and the payout. When a buyer disputes a call or a publisher's quality slips, the answer is in the log — not in a support ticket to your platform.
- 03
Ratios police the traffic.
Ping-to-call and converted-to-call ratios are computed per campaign and per publisher, with health flagged inline. A publisher pinging thirty times per connected call looks profitable in volume reports and terrible here — which is the point.
- 04
Anomalies get flagged before you go looking.
Pings, bids, and errors trend on one chart with anomalies marked as they occur. A bidding integration that silently starts erroring shows up as a flag on the timeline, not as a quiet week of lost revenue.
Product specifics
The controls behind the work.
The RTB toolkit, stated plainly.
Ping-post bidding
Inbound request → bid decision → call, with per-step visibility.
Lifecycle logging
Full HTTP exchange and parameters retained per request, both directions.
Ratio health
Ping-to-call and converted-to-call ratios by campaign and publisher.
Anomaly detection
Pings, bids, and errors trended with anomalies marked.
Geographic targeting
State-level targeting on inbound requests.
Number allocation
Target numbers and caller IDs tracked per request, with status and duration.
Payout tracking
Buyer, target, duration, and payout on every connected call.
Campaign & publisher tables
Per-entity breakdowns of the same numbers, one click deep.
Why connect it
Change the working pattern.
RTB platforms mostly report outcomes. This one shows its work.
The friction
Publisher quality judged monthly, from spreadsheets, after the spend.
With Moja
Ping-to-call and conversion ratios per publisher, flagged live.
The friction
Integration failures discovered when revenue dips.
With Moja
Error trends with anomaly markers, visible the hour they start.