Ringba on your landing pages
Pay per call has a cost the call log doesn't show: every click that sees the number and dials out of curiosity. Ringba counts those calls, routes them and reports them, but it can't keep them from happening. That part is the page's job, and it's what LanderLab is built for: a quiz that asks what your buyer's rules ask, and a call page that only the visitors who pass ever reach.
Together the two cover the whole trail. LanderLab qualifies the visitor and keeps the click ID on the URL. Ringba's tag, which LanderLab installs from your Campaign ID with no snippet to paste, gives that visitor a number from your pool and ties the call to the visit. Ringba then routes the call to the right target, decides whether it converted and fires the pixel that tells your tracker. You end up knowing which ad, which landing page and which variant produced the calls that paid.
Ringba numbers only for callers who qualify
In pay per call you're paid for calls, not form fills, and a buyer pays only once a call runs long enough to qualify. Put the number in front of every click and you pay for the curious callers who hang up early, while your buyer pays for none of them. And a buyer who keeps getting short calls from your source has little reason to keep taking them.
A LanderLab quiz moves the number behind the questions your buyer cares about. On a choice question each answer can go to its own step or to a Custom URL, so the visitor with $6,000 of debt sees another offer and the one with $30,000 lands on the call page. Ringba still counts every call, but now the calls it counts are the ones worth routing.
Ringba tags from the ad, the page and the quiz
Ringba's number pool tag sends the visitor's session with the number request: the full page URL, the UTMs, the referrer, the visitor's state, city and ZIP, the IP and the user agent. Any other parameter on the URL, like your tracker's click ID or a sub ID, is captured as a tag too, with no code.
That's where LanderLab's quiz settings earn their keep. With Forward URL Parameters and Include Quiz Data on, the click ID and the answers ride from the quiz to the call page's URL, named after each field. Ringba tags the call with them, and once you declare a parameter in Ringba it becomes a token like [tag:User:clickid] for routing filters and pixels.
Routing and real-time bidding from real caller data
Ringba routes on what it knows about the call. A caller tagged with a state, a debt amount and an age band can be filtered to the target licensed for that state, sent to the buyer who pays most for that profile, or kept away from a target that can't take it. The more the call carries, the finer the routing can be.
The same data makes your calls easier to sell. Buyers on Ringba's real-time bidding price each call, and a call that arrives already matching a buyer's rules is a call they have a reason to bid on and keep capacity open for.
Calls tied back to the page, the variant and the ad
A Ringba pixel can fire when a call converts or pays out, and with the click ID on the call it posts that conversion back to ClickFlare or your tracker against the exact click. Your tracker passes it on to Meta or Google, and the ad sets learn from calls that paid instead of from page views.
On a page with A/B variants, you pick which variants load Ringba. Run a version that asks visitors to call against one that asks the quiz first, on the same traffic, and compare what each one earns in Ringba next to LanderLab's own count of taps on the call button.
