Black Friday came early.Early-access pricesuntil Nov 8.Black Friday: early-access prices until Nov 8.Early-access price ends in0d00h00m00sClaim the deal
ClickFlare passes its click ID to your lander, and Ringba stores it on the call as [tag:User:clickid]. A Ringba pixel posts each converted call back with payout and call ID, and an optional API integration pulls revenue so later payout changes are kept.
If the number pool runs out, calls can't be tied to a click.
Pay-per-call
Call postback pixel
Ringba API revenue
Know which ad made the phone ring
Calls tied to the ad click
Each call carries the ClickFlare click ID, so you see the source, ad and lander behind it, next to your cost.
Save your number pool
ClickFlare Tag Manager can inject the Ringba script only after a quiz step, so numbers go to engaged visitors and attribution holds.
Revenue that stays accurate
The Ringba API integration pulls conversions and revenue, so ClickFlare keeps up if Ringba updates a call's payout after the postback.
How it works
From ad click to profit per campaignattributed revenueattributed salesa matched conversion
01
Your ad
Visitor clicks
Ad on Ringba
02
ClickFlare
Click recorded
A unique cf_click_id is created
03
Your offer
Conversion
Lead, sale or custom event
04
ClickFlare
Sent back to Ringba
Through the Conversion API or postback
05
Cost API
Spend pulled in
Ringba cost matched to each campaign
01
Your ad
Ringba click
Macros fill the tracking URL
02
ClickFlare
Click recorded
Zone, site and device data stored
03
Offer or lander
Visitor converts
On your page or the offer
04
ClickFlare
Conversion logged
With payout and event type
05
Postback
Reported to Ringba
So its optimization sees the result
01
Your ad
Visitor clicks
Any traffic source
02
ClickFlare
Click recorded
A unique cf_click_id is created
03
Your article
Keyword block
Click ID passed to the feed
04
Results page
Paid click
Conversion fired to ClickFlare
05
Ringba API
Revenue matched
Pulled on a schedule and reconciled
01
Your ad
Visitor clicks
Any traffic source
02
ClickFlare
Click recorded
cf_click_id passed to the offer
03
Ringba
Offer or call
The network tracks the action
04
Ringba
Conversion
Lead, sale, call or rebill
05
Postback
Payout in ClickFlare
Matched to the original click
01
Your ad
Visitor clicks
Any traffic source
02
ClickFlare
Click recorded
A unique cf_click_id is created
03
Ringba
Store or funnel
Click ID kept through checkout
04
Events
View, cart, checkout
Each step tracked
05
ClickFlare
Purchase recorded
Order value matched to the ad
Pay-per-call
Click ID on the call, payout on the postback
Add your lander as a ClickFlare offer with clickid={cf_click_id}. Ringba's Number Pool script shows each visitor a unique number and saves the click ID as a URL parameter. When the call converts, a Ringba pixel fires the ClickFlare postback.
clickid URL parameter created in Ringba
Pixel sends payout, call ID and ct
param1–20 for ZIP, number, lander URL
Today, one campaign
example
Spend pulled from Ringba
cost
$412.30
Conversions recorded
today
38
Sent back to Ringba
per event
38/38
Profit
campaign
$227.70
Example numbers. Cost and conversions sit in the same report row.
Captured on every Ringba click
key macros
[tag:User:clickid], payout, txid, ct, param1–20
captured
From the Ringba template in ClickFlare. Use them as report columns and rules.
Revenue for one click
example
Paid click
day 0
$0.00
First revenue pull
+1h
$0.41
Scheduled updates
next days
$0.58
Final pull
last sync
$0.62
Example amounts. Sync timing for Ringba is in the facts above.
Events for one click
example
Lead
day 0
$0.00
Sale
day 0
+$40.00
Upsell
day 1
+$15.00
Refund
day 9
−$15.00
Example events. Each one arrives by postback and is matched to the click.
One visitor's path
example
Product view
step 1
—
Add to cart
step 2
—
Checkout
step 3
—
Purchase
step 4
$68.00
Example order. Each event is tied to the ad that brought the visitor.
20
Extra params per postback
3
Supported tracking setups
2.3B
Events tracked
Setup
Connected in four steps
You need a Ringba account with a campaign, a landing page that shows a phone number and a ClickFlare account.
Add your lander as an offer In ClickFlare, create your landing page as an offer and append clickid={cf_click_id} to its URL, so the click ID reaches the page.
Create the clickid parameter in Ringba In Ringba, go to Integrations, then URL Parameters, and create one named clickid. Open your Ringba campaign and add clickid under URL Parameters.
Create a pixel with the postback Create a custom conversion for calls, then copy your postback from Settings, Tracking URLs. In Ringba, go to Integrations, Pixels, create a pixel and map click_id, payout, txid and ct.
Optional: connect the Ringba API Create an API Access Token under Security in Ringba and add the required URL parameter to every campaign. Then add Ringba under Affiliate Network Integrations in ClickFlare.
Injecting the Ringba script with ClickFlare Tag Manager? Don't also add it to the page by hand, or it runs twice. Tag Manager needs the ClickFlare container script on the lander.
{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Does ClickFlare integrate with Ringba?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. Ringba sends converted calls to ClickFlare through a pixel that fires the ClickFlare postback. An optional API integration also pulls conversions and revenue."}}, {"@type": "Question", "name": "How does Ringba get the ClickFlare click ID?", "acceptedAnswer": {"@type": "Answer", "text": "Append clickid={cf_click_id} to the lander URL in ClickFlare and create a clickid URL parameter in Ringba. Ringba exposes it as the [tag:User:clickid] token."}}, {"@type": "Question", "name": "What happens if my Ringba number pool runs out?", "acceptedAnswer": {"@type": "Answer", "text": "Ringba may still route the call, but tracking fails and the call isn't attributed to the right click. Delaying script injection with Tag Manager helps."}}, {"@type": "Question", "name": "Can I track Ringba calls from Google Ads?", "acceptedAnswer": {"@type": "Answer", "text": "Yes, with direct tracking. ClickFlare stores the click ID in a cookie, and a Tag Manager tag injects the Ringba script and pushes the ID. Reading the cookie takes about 1 to 2 seconds."}}, {"@type": "Question", "name": "Why connect the Ringba API if I already use the postback?", "acceptedAnswer": {"@type": "Answer", "text": "The API pulls conversions and revenue directly, so revenue stays right if Ringba updates a call's payout after the postback fired. It needs a Ringba API Access Token."}}, {"@type": "Question", "name": "Can I send Ringba calls to Facebook or other ad platforms?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. Once a call is a conversion in ClickFlare, you can send it server-side through a Conversion API integration, with data like phone number and ZIP code."}}]}
Your Ringba calls, tracked back to the ad click.
Calls, payouts and ad cost in one report. Free 14-day trial, no credit card, free migration from any tracker.