Ringba RTB Integration
Step-by-step guide to connecting Ringba as a real-time bidding router in Lead Distro AI. Let Ringba bid on your inbound calls live so every call goes to the highest paying buyer, using the built-in Ringba preset. Plain English, with the exact fields, endpoint, and a test to prove it works.
Call Tracking is in beta. If you don't see Calls in your sidebar, or you don't see Dynamic routing (RTB) when you add a target where this guide says to look, email support@leaddistro.ai and we'll switch it on for your account.
This guide connects Ringba to Lead Distro AI so Ringba bids on your calls in real time. Each inbound call becomes a live auction: Ringba (and any of your own buyers) offers a price, and the highest bid wins the call. If you're new to bidding on calls, skim RTB for Calls first for the big picture, then come back here for the Ringba specifics.
What you'll need before you start
- A Ringba account with RTB (Real-Time Bidding) turned on.
- Your Ringba RTB ID. This is the unique code for your Ringba RTB endpoint (it looks like
rtb123456). You'll find it in Ringba under your RTB settings. - A Calls campaign in Lead Distro AI. If you don't have one yet, follow Call Tracking Setup to get a tracking number and a campaign first.
- Your target markets in mind. Ringba bids by area, so knowing which states and zips you send calls from helps you read the results.
In Lead Distro AI, Ringba plugs in as a Dynamic Routing target on a Calls campaign. You do not need to switch your whole campaign to Real-Time Bidding to use it. A Ringba router can bid alongside your own buyers in any Calls campaign.
Step 1: Add a target and choose Dynamic routing
Open your Calls campaign, go to the Call Flow tab, click Add, then Add Target. Name it (for example "Ringba") and click Add. In the form that opens, set Routing method to Dynamic routing (RTB). This is where you connect any outside router. It works the same for Ringba, Retreaver, TrackDrive, or a generic webhook.
Step 2: Pick the Ringba preset
Under Router preset, choose Ringba. This fills in almost everything for you the right way for Ringba: it sets the request to GET, turns on SIP support, and sets the reply to read Ringba's bidAmount as the price. You just paste in your details.
Ringba doesn't send a separate yes or no on each call. It just sends a price, and any price above zero means it wants the call. The Ringba preset already knows this, so you don't have to configure it.
Step 3: Paste your Ringba RTB ID
In the RTB ID box, paste your Ringba RTB ID. We build the Endpoint URL for you in this shape, with your RTB ID where it says RTBID (pasting the full Ringba URL into the box works too):
https://rtb.ringba.com/v1/production/RTBID.jsonLeave the method on GET (the Ringba preset sets this). Lead Distro AI attaches the caller's details (their number, state, and zip) to the request for you based on the Ping parameters the preset filled in, so you don't have to build a long URL by hand.
If Ringba gave you a full URL that already includes query parameters like ?CID=...&State=...&ZipCode=..., you can paste the whole thing. Lead Distro AI keeps your caller-detail mappings in the Ping parameters below, so either way Ringba gets the caller ID, state, and zip.
Step 4: Add a key header (only if Ringba gave you one)
If your Ringba RTB endpoint needs a key or token besides the RTB ID, go to Headers, click Add Header, and enter the header name Ringba expects (usually Authorization) and the key as its value. If your RTB ID is all Ringba asks for, skip this step. See RTB for Calls for more on what an RTB key is.
Step 5: Choose how to get the caller's zip
Ringba bids more accurately when it knows where the caller is, so pick a ZIP source:
| ZIP source | What it does |
|---|---|
| Ask the caller | Plays a short prompt asking the caller to punch in their 5 digit ZIP before the auction. Most accurate, but adds a step for the caller. |
| Use carrier ZIP (no prompt) | Silently uses the zip the phone network provides. No prompt, but it's the caller's phone-registration area, not always where they are now. |
| Ask, fall back to carrier ZIP | Asks the caller, and if they don't enter anything, uses the carrier zip. A good balance. |
If you choose to ask the caller, set the ZIP prompt message they'll hear, for example "Please enter your 5 digit ZIP code."
Step 6: Set your reserve, priority, and timeout
- Minimum bid ($) is your reserve price. Lead Distro AI rejects any Ringba bid below this and moves to the next target. Leave it blank or 0 to accept any bid Ringba returns. Ringba is always billed its live bid, so there is no backup price.
- Priority (under Call Settings, further down the form) decides where Ringba sits when bids tie. Lower rings first. Outside routers usually go ahead of your own buyers.
- Timeout (ms) is how long we wait for Ringba to answer before moving on. Default is 1500 (1.5 seconds). Keep it short so callers aren't left waiting. If Ringba is slow or offline it simply doesn't bid, and the call goes to the next highest bidder.
Step 7: Test the connection before you save
Click Test ping below the router settings, fill in the sample values, then click Execute test. It sends Ringba one sample call and shows you whether Ringba answered, whether it bid, and the price and number it returned. Give it sample values so Ringba has something to price:
- Caller number, for example
5551234567. - State, for example
CA. - ZIP, for example
90210.
Fix any red result before you save. If Test ping comes back with a 401 or "unauthorized", the token or header name is wrong (recopy it, watch for extra spaces). If Ringba answers but returns no bid, that usually means no Ringba campaign wants that test caller, try a state and zip you know Ringba buys.
When it looks right, click Add Target. Ringba now bids on every call for this campaign.
How a Ringba call flows
- A caller dials your tracking number. We gather the caller's number, state, and zip.
- We ask Ringba for a live bid and, at the same time, let any of your own buyers bid too.
- Ringba replies with a price (its
bidAmount) and the number or SIP address to send the call to. - The highest bid wins. If Ringba's bid beats your buyers (and clears your minimum), the call connects to Ringba's returned destination.
- The call is billed the winning bid once it passes your minimum duration. Every call's log shows who bid, how much, and who won.
Ringba settles payment on its own side, so a Ringba (Dynamic Routing) call does not draw down a Lead Distro AI wallet. You still pay the usual per-minute call time and monthly number rental.
Good acceptance rules to start with
| Goal | What to set |
|---|---|
| Accept any Ringba call | Leave Minimum bid blank or 0. Ringba's price above zero already means it wants the call. |
| Only take calls worth $20+ | Set Minimum bid to 20. Lead Distro AI skips any Ringba bid under $20. |
| Protect call quality | Set a sensible minimum duration on the campaign so short, junk calls aren't billable. |
Frequently Asked Questions
Do I have to switch my whole campaign to Real-Time Bidding to use Ringba?
Where do I find my Ringba RTB ID?
Why does the Ringba preset use GET instead of POST?
Ringba answered but returned no bid. What's wrong?
Does Ringba support SIP, not just phone numbers?
How is a Ringba call billed?
Can I use both Ringba and Retreaver on the same campaign?
Related Articles
If you have any questions, send us an email at support@leaddistro.ai