What Ringba handles
- Call tracking with dynamic numbers and source attribution
- Real-time call routing (a ping tree for calls)
- Target/buyer caps, schedules, and payouts
- Recording and tagging calls for quality and billing
How I integrate Ringba
On the platform I built, Ringba runs as dynamic number insertion driven off the same campaign and publisher data as the form flow. Each landing page loads Ringba's JavaScript tag for its vertical, ACA, Medicare, auto, final expense, debt, and others, which provisions a tracking phone number, and the page swaps that number in so every traffic source shows its own number.
The tag that loads isn't hardcoded. A nightly job calls Ringba's v2 API for each campaign, pulls that campaign's affiliate tracking numbers, and writes them to a mapping the front end reads, so the right number resolves by campaign plus publisher ID. When Ringba adds or changes a number, the site picks it up without a deploy.
The same data the form captures rides along on the call. I push the lead's fields and its consent tokens, the TrustedForm ping URL and the Jornaya LeadiD, onto the call as Ringba tags, so a call is attributed to the same source and carries the same consent proof as a form lead from that visitor.
Calls and form leads in one layer
Most operations bolt Ringba on separately from their form-lead capture, so a call and a form lead from the same visitor look like two unrelated events. Wiring Ringba into the same flow means a call inherits the visitor's source, publisher ID, and consent tokens automatically, so calls and form leads line up under the same attribution instead of two disconnected reports.
FAQ
- Can you run calls and form leads through one system?
- Yes. That's the main reason to integrate Ringba into the distribution platform rather than alongside it.
- Do you handle call attribution back to source?
- Yes. Calls carry source/sub-ID attribution the same way form leads do.