Black Friday came early.Early-access pricesuntil Nov 8.Black Friday: early-access prices until Nov 8.Early-access price ends in0d00h00m00sClaim the deal
PCB
Perform[cb] conversions,on the click that drove them
ClickFlare records every Perform[cb] conversion and payout on the click, campaign and traffic source behind it. Later events, such as a purchase after a trial, can report in their own column, so you judge sources on everything they earn.
Offers, landers and traffic sources by real payout
Works with
CPA, CPL, CPS, CPI and CPC offers and Offer Groups
Good to know
Some app installs arrive without a click and can't be matched.
Affiliate network
Real-time payouts
Event conversions
Perform[cb] payouts on the click that earned them
Ready template
ClickFlare's PerformCB template comes with the click and payout already mapped, so the postback is built for you.
Events in their own column
Later events count in a separate column and don't replace the main conversion, so you see the full value of each source.
Offer Groups still attribute
The click travels on the link, whichever offer Perform[cb] picks, and you can see which offer in the group converted.
How it works
From ad click to profit per campaignattributed revenueattributed salesa matched conversionautomated actionyour dashboardsclosed revenue
01
Your ad
Visitor clicks
Ad on Perform[cb]
02
ClickFlare
Click recorded
Every click gets its own ID
03
Your offer
Conversion
Lead, sale or custom event
04
ClickFlare
Sent back to Perform[cb]
Through the Conversion API or postback
05
Cost API
Spend pulled in
Perform[cb] cost matched to each campaign
01
Your ad
Perform[cb] click
Placement, device and country come along
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 Perform[cb]
So its optimization sees the result
01
Your ad
Visitor clicks
Any traffic source
02
ClickFlare
Click recorded
Every click gets its own ID
03
Your article
Keyword block
Click ID passed to the feed
04
Results page
Paid click
Conversion fired to ClickFlare
05
Perform[cb] API
Revenue matched
Pulled on a schedule and reconciled
01
Your ad
Visitor clicks
Any traffic source
02
ClickFlare
Click recorded
The click follows the visitor to the offer
03
Perform[cb]
Offer or call
The network tracks the action
04
Perform[cb]
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
Every click gets its own ID
03
Perform[cb]
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
01
Your ad
Visitor clicks
Form, call or landing page
02
ClickFlare
Click recorded
Every click gets its own ID
03
Perform[cb]
Lead or call stored
The ad stays linked to the lead
04
Perform[cb]
Qualified or closed
Workflow or call rule fires
05
ClickFlare
Revenue recorded
Tied to the ad that drove it
01
ClickFlare
Event happens
Click, conversion or custom event
02
Webhook or API
Data goes out
Or comes back in
03
Perform[cb]
Your workflow
Rules, apps or an AI assistant
04
Perform[cb]
Action
Alert, update, pause or scale
05
ClickFlare
Back in reports
Changes show in your data
01
ClickFlare
Report data
Campaigns, sources, offers
02
ClickFlare API
Your numbers go out
Secured with your API key
03
Your setup
Scheduled refresh
A sheet, script or connector
04
Perform[cb]
Data lands
Tables refreshed on schedule
05
Perform[cb]
Dashboards
Blended with your other data
Affiliate network
Every Perform[cb] conversion lands on its click
ClickFlare tags your Perform[cb] link with each click. When the visitor converts, Perform[cb] reports the conversion and payout back, and ClickFlare adds it to the click, campaign and traffic source behind it.
Payout recorded the moment Perform[cb] reports it
One postback for all traffic, or per offer or vertical
Events report in their own column
Today, one campaign
example
Spend pulled from Perform[cb]
cost
$412.30
Conversions recorded
today
38
Sent back to Perform[cb]
per event
38/38
Profit
campaign
$227.70
Example numbers. Cost and conversions sit in the same report row.
ROI per placement
example
Placement A · mobile
cost
$38.20
Placement A
revenue
$71.40
Placement A
ROI
+87%
Placement B · desktop
ROI
−42%
Example numbers. Keep the placements that pay and cut the ones that lose money.
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 Perform[cb] 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.
One lead, followed to revenue
example
Lead created
day 0
$0.00
Qualified
day 2
+$25.00
Deal closed
day 14
+$480.00
Renewal
day 45
+$120.00
Example values. Each stage can be its own event type in ClickFlare.
A scheduled report refresh
example
Campaigns
in the report
1,240 rows
Cost, revenue, profit
per campaign
included
Refresh
your schedule
done
Dashboards fed
Perform[cb]
3
Example numbers. You choose the breakdowns, date range and schedule.
One event, end to end
example
Conversion recorded
event
sent
Event delivered
Perform[cb]
received
Workflow ran
Perform[cb]
done
Team notified
your apps
done
Example run. What happens after the event is up to your workflow.
2.3B
Events tracked
Setup
Connected in three steps
You need a ClickFlare account with your own tracking domain and an approved Perform[cb] affiliate account.
Add Perform[cb] as your affiliate network Pick the PerformCB template in the ClickFlare campaign editor. It prepares the postback for you.
Add your offer or Offer Group link Create a link for the offer or Offer Group in Perform[cb] and add it to your campaign. ClickFlare tags it with each click.
Add the postback in Perform[cb] Add the ClickFlare postback in Perform[cb]'s tracking pixels for your main conversion. Conversions then land on each click.
app.clickflare.com/integrations
PCB
Perform[cb]
Affiliate network
Connected
Perform[cb] account connected
Signed in from ClickFlare
Cost syncing
Spend matched to campaigns
Conversions sent back
Your chosen events
Perform[cb] template selected
Macros pre-filled
Tracking URL in Perform[cb]
Click ID captured
Conversions reported
Payout included where supported
Perform[cb] connected
Credentials saved in ClickFlare
Conversion event set
Click ID passed to the feed
Revenue syncing
On the feed's schedule
Perform[cb] added
Offer URL carries the click ID
Postback set in Perform[cb]
Payout and event included
Conversions arriving
Matched to the click
Perform[cb] connected
Click ID kept to checkout
Events mapped
View, cart, checkout, purchase
Purchases tracked
Order value in reports
Click ID stored in Perform[cb]
Hidden field or call data
Workflow or rule set
Fires on the stage you choose
Conversions arriving
With payout and event type
API key created
Settings, then Security
Report pull scheduled
Dimensions and date range set
Perform[cb] dashboards live
Refreshed on schedule
Connection set up
Webhook, API key or MCP
Events chosen
Only what the workflow needs
Workflow running
Tested end to end
Ready to track
Perform[cb] fires every pixel that applies. Use one scope for the ClickFlare postback, so the same conversion isn't sent twice.
Pass each conversion on through ClickFlare or Perform[cb], not both, so it counts once.
Frequently asked questions
Perform[cb] integration FAQ
Does ClickFlare integrate with Perform[cb]?
Yes. ClickFlare has a ready PerformCB template. Perform[cb] sends each conversion and its payout by server-to-server postback, and ClickFlare matches it to the click.
Is Perform[cb] the same as Clickbooth?
Yes. Perform[cb] is the former Clickbooth, and its links still run on Clickbooth's tracking domain. The same template covers it.
Can ClickFlare track Perform[cb] event conversions?
Yes. Add a second postback for events in Perform[cb], and they report in their own ClickFlare column without replacing the main conversion.
Should the postback cover all my Perform[cb] traffic?
Use one postback for all traffic if everything runs through ClickFlare. Otherwise set it per offer, Offer Group or vertical. Pick one, so conversions don't double.
Does it work with Perform[cb] Offer Groups?
Yes. The click follows the visitor to whichever offer Perform[cb] picks, and you can see which offer in the group converted.
Do app install offers report to ClickFlare?
Yes, when the conversion carries the click. Some app conversions arrive without a click because of Apple's App Tracking Transparency, and those can't be matched.
No items found.
Related integrations
More templates that plug into the same ClickFlare account.
{"@context": "https://schema.org", "@graph": [{"@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Does ClickFlare integrate with Perform[cb]?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. ClickFlare has a ready PerformCB template. Perform[cb] sends each conversion and its payout by server-to-server postback, and ClickFlare matches it to the click."}}, {"@type": "Question", "name": "Is Perform[cb] the same as Clickbooth?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. Perform[cb] is the former Clickbooth, and its links still run on Clickbooth's tracking domain. The same template covers it."}}, {"@type": "Question", "name": "Can ClickFlare track Perform[cb] event conversions?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. Add a second postback for events in Perform[cb], and they report in their own ClickFlare column without replacing the main conversion."}}, {"@type": "Question", "name": "Should the postback cover all my Perform[cb] traffic?", "acceptedAnswer": {"@type": "Answer", "text": "Use one postback for all traffic if everything runs through ClickFlare. Otherwise set it per offer, Offer Group or vertical. Pick one, so conversions don't double."}}, {"@type": "Question", "name": "Does it work with Perform[cb] Offer Groups?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. The click follows the visitor to whichever offer Perform[cb] picks, and you can see which offer in the group converted."}}, {"@type": "Question", "name": "Do app install offers report to ClickFlare?", "acceptedAnswer": {"@type": "Answer", "text": "Yes, when the conversion carries the click. Some app conversions arrive without a click because of Apple's App Tracking Transparency, and those can't be matched."}}], "dateModified": "2026-11-12"}, {"@type": "BreadcrumbList", "itemListElement": [{"@type": "ListItem", "position": 1, "name": "Integrations", "item": "https://www.clickflare.com/integrations"}, {"@type": "ListItem", "position": 2, "name": "Networks & Feeds", "item": "https://www.clickflare.com/integrations/networks-feeds"}, {"@type": "ListItem", "position": 3, "name": "Perform[cb]"}]}]}
Every Perform[cb] conversion, on its click.
Main and event conversions matched to the click and source behind them. Free 14-day trial, no credit card, free migration from any tracker.
![Perform[cb] logo](https://cdn.prod.website-files.com/6a55f10c49e0c5bc5d9a2d51/6af5d9a13a4c637c6a109edd_6a608e8615056e6c1bedc3dc_Group-1597882244.svg)
