Ringba knows which calls your buyers paid for. Google Ads is still counting the ones they rejected.
When your own Google or Meta ads feed a Ringba campaign, the call is routed, scored and paid inside Ringba, and the ad platforms only learn what Ringba is set up to tell them. Pick the wrong upload event or skip the number pool, and bidding learns from hang-ups and repeat callers. We carry the click ID through Ringba's number pool and make sure only the calls your buyers convert reach Google Ads and Meta.
Free30 minutesNo obligation
Ringba · what breaks
What goes wrong with Ringba and your ads
- 01
"Google Ads counts calls our buyers rejected"
With Google's own call conversions running beside Ringba, any call that passes the minimum length you set counts, whether or not the buyer accepted it or the caller failed the IVR, and Smart Bidding buys more of that traffic.
- 02
"The upload says Payout, but we get paid on Conversion"
Ringba uploads one event or the other: a target conversion that earned revenue, or a publisher payout. Pick the wrong one and a Medicare or mass tort campaign optimizes toward calls that cost you, not calls that pay you.
- 03
"Meta can't match our callers to our ads"
Ringba's call-only Facebook integration sends little beyond phone number, state and country, and Ringba warns the match rate may be low. Meta then can't learn which ads make a debt relief or junk car line ring.
- 04
"Our buyer fixed the revenue. Google kept the old number."
Ringba's docs say manual revenue or payout edits don't reach Google Ads, so a regraded rehab or insurance call never updates there and your return on ad spend drifts from what you actually billed.
Ringba · the fix
What changes — Ringba
Bidding learns from billable calls
Only calls Ringba marks converted, or paid out, reach Google Ads and Meta, so both chase the callers your buyers accept instead of the ones who simply stayed on the line.
Callers tied to the ad they clicked
The number pool links each call to its landing page session, so the click ID, IP address and user agent travel with it.
One conversion per caller, at the right value
Repeat callers, $0 postbacks and test calls stay out; revenue that changes later gets corrected wherever each platform allows it.
Ringba · architecture
What Ringba actually lets you hook into
All of this is from Ringba's help center. Anything it doesn't document, we test on a live call first.
- 1
Number pools and the call tracking tag
A JavaScript snippet shows each visitor their own number and keeps the session as an impression for up to 6 hours. Via GTM, only one campaign's tag works per page.
- 2
Native Google Ads integration
Set up under Integrations > Platforms. Needs auto-tagging, uploads on Conversion or Payout into an RB- conversion action, and retries failures hourly, up to 10 times.
- 3
Facebook Events integration
Calls go through Meta's Conversions API. The JS-tag version needs a number pool and Meta Pixel; the call-only version uses static numbers at a lower match rate.
- 4
Tracking pixels and the Pixel node
Fire on Incoming, Connected, Completed, Converted, Payout and more, with tag filters. A 10-second timeout and no retry, so a slow endpoint loses the event.
- 5
Webhooks, API and Zapier
Buyers post revenue to a webhook once per call ID within 30 days. The API is in every plan; Zapier connects through a pixel.
Ringba · diagnose
Where Ringba tracking breaks, in diagnostic order
Double counting first, then what Ringba never received; from inside Google Ads both look like a bidding problem.
- 01
Count the sources reporting each call
Ringba's integration plus Google's own calls-from-ads conversion is the usual pair.
- 02
Look for leftover gclid, gbraid, wbraid or kw URL parameters
Ringba warns that parameters created before the integration can stop conversions firing.
- 03
Open a test call in Call Details
From an ad-tagged URL, the Tags tab should show the click ID and a linked number pool impression.
- 04
Check the upload event and where the value comes from
Conversion or Payout, and whether revenue is set on the target or arrives by webhook.
- 05
Read the pixel response codes
A Pixel Fire event outside the 200s was lost for good.
- 06
Size the number pool
When every number is in use, visitors see the primary number and the call arrives as a Pool Miss with no click ID; short idle limits also reuse numbers sooner and lean on last-impression attribution.
Ringba · prove
The QA evidence — Ringba
Run on real calls to your live landing page and call-only ads, with the RB- conversion action and Events Manager open.
Source of truth
Ringba Call Details report: converted calls by date, with inbound call ID, campaign, target, revenue, payout and the isDuplicate tag
- A test call from an ad-tagged URL, with gclid and the impression on the call's Tags tab.
- The upload confirmed in the RB- conversion action after Ringba's upload delay.
- One Meta event per converted call, with no second copy from a pixel or server container.
- A repeat call from the same phone tagged isDuplicate and held back.
- A $0 buyer postback confirmed absent from every destination.
- Converted calls reconciled one by one against Google Ads and Meta over a closed window.
- Repeated 30 days later and after any routing, target or landing page change.
Ringba · free audit
What we check in the free audit
- Count the sources reporting each call
- Look for leftover gclid, gbraid, wbraid or kw URL parameters
- Open a test call in Call Details
- Check the upload event and where the value comes from
- Read the pixel response codes
- Size the number pool
Checked against
Ringba Call Details report: converted calls by date, with inbound call ID, campaign, target, revenue, payout and the isDuplicate tag
Free30 minutesNo obligation
Ringba · when not to buy
When you don't need this on Ringba
Plenty of Ringba accounts only need a settings check.
- If you only buy calls from publishers and run no ads of your own, ad attribution isn't your problem.
- If you run call-only ads on one platform and the RB- conversion count already matches your converted calls in Ringba, leave it alone.
- If buyers pay on a flat call length and never regrade calls, the native Conversion upload may be all you need.
- If the only fault is a leftover gclid URL parameter in the campaign, deleting it is a fix you can make yourself, and we'll say so.
Ringba · what we deliver
The event map on Ringba
Landing page impression
Number pool session opened with gclid, kw, UTMs and other click IDs stored as Ringba tags. Diagnostic only.
Incoming call
Reporting only. Calls stopped by the spam filter or repeat-caller block never reach an ad platform.
Qualified in the IVR
Gather and menu answers, like ZIP Code or age, saved as tags that decide which calls can count.
Connected to a buyer
Secondary signal for spotting routing gaps; not the bidding conversion.
Converted call
The primary conversion for Google Ads and Meta, fired when the target converts or the buyer's webhook postback lands; we confirm on a live call that the value arrives with it.
Held back and corrected
isDuplicate=yes callers, errored calls and $0 webhook posts excluded; regraded revenue queued for a correction where the platform supports one.
Written guarantee
95%+ tracking accuracy
Measured against Ringba Call Details report: converted calls by date, with inbound call ID, campaign, target, revenue, payout and the isDuplicate tag. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
Ringba questions, answered
Yes. Ringba uploads calls as Google Ads conversions, by number for call-only ads or through a landing page running a number pool, and it requires auto-tagging. They land in an action named RB- plus your campaign name.
Whichever matches how you make money on the call. Ringba sends one or the other per integration, and a campaign uploading payouts optimizes toward calls you paid publishers for, not calls a buyer accepted.
With static numbers, Ringba's call-only integration sends little more than phone number, state and country, so Meta matches fewer calls. A number pool plus the Meta Pixel on the page gives it more to match.
Yes. When the target converts on postback or webhook, Ringba uploads the conversion once the buyer's webhook arrives. Manual revenue edits in Ringba don't reach Google Ads, so regraded calls need a separate correction, and we check on a live call whether the revenue value lands too.
Ringba tags a caller ID seen in the campaign in the last 365 days with isDuplicate=yes, and pixels can filter on it. Whether a duplicate still converts depends on your target and buyer settings, which we check.
Yes, as a Custom HTML tag on DOM Ready. Ringba notes only one campaign's tag works per page that way, so a page tied to several campaigns needs a different install.
More on Ringba
- Enhanced ConversionsEnhanced Conversions enrich the conversions that already fire. First we make sur…
- Meta CAPIA one-click CAPI integration sends thin events. That's why your Event Match Qual…
- Cross-Domain TrackingYour checkout provider is the best performing traffic source in your GA4 account…
RELATED GUIDES
Booking tools beside Ringba, and what their bookings feed
- Patient PrismPatient Prism says who booked. Your Google Ads still pays for every caller.
- CallSourceCallSource knows which calls booked an estimate. Your Google Ads doesn't.
- LiineLiine shows which ads book patients. Your ad accounts still bid on calls.
- CallTrackingMetricsCallTrackingMetrics says every call is a lead. Your crew knows better.
- WhatConvertsGoogle Ads is counting every WhatConverts call, hang-ups and all. It should only learn from the leads you'd quote.
- CallRailCallRail conversion tracking that counts booked jobs, not every ring
Free · 30 min
Get your Ringba calls counted the way you get paid
WhatsAppFree30 minutesNo obligation
