Black Friday came early.Early-access pricesuntil Nov 8.Black Friday: early-access prices until Nov 8.Early-access price ends in0d00h00m00sClaim the deal
One Whop company API key powers both halves. ClickFlare pulls Whop Ads spend at campaign, ad group and ad level, and sends tracked conversions to Whop's Events API as one of eight standard events, with a stable event ID that stops duplicates.
Company API key with 3 permissions, for CAPI and cost
What syncs
Conversions out; campaign, ad group and ad spend in
Sync schedule
Conversions per event; cost every 60 to 5 min by plan
Key parameters
fbclid, wacid, wasid, waid, utm_whop
Works with
Website, App and Phone Call action sources
Good to know
Whop rejects events more than 28 days old
Ad platform
One key, both ways
8 Whop events
Whop Ads judged on the conversions Whop can't see
Postback sales reach Whop
A sale an affiliate network confirms hours after the click never touches a browser. ClickFlare sends it to Whop server to server.
No double-counted events
The default Event ID combines click ID, transaction ID and conversion type, so Whop keeps a re-sent conversion only once.
Spend at three levels
Whop's wacid, wasid and waid let ClickFlare line up pulled spend with each campaign, ad group and ad.
How it works
From ad click to profit per campaignattributed revenueattributed salesa matched conversion
01
Your ad
Visitor clicks
Ad on Whop
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 Whop
Through the Conversion API or postback
05
Cost API
Spend pulled in
Whop cost matched to each campaign
01
Your ad
Whop 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 Whop
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
Whop 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
Whop
Offer or call
The network tracks the action
04
Whop
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
Whop
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
Ad platform
wacid, wasid and waid: how Whop spend finds the click
Whop adds its campaign, ad group and ad IDs to the landing URL. The Whop template captures them in tracking fields 1 to 3, ClickFlare matches pulled spend to them, and you can map them straight into Events API parameters.
Purchase needs a payout above zero
Email and phone sent unhashed
CAPI connected in the campaign editor
Today, one campaign
example
Spend pulled from Whop
cost
$412.30
Conversions recorded
today
38
Sent back to Whop
per event
38/38
Profit
campaign
$227.70
Example numbers. Cost and conversions sit in the same report row.
Captured on every Whop click
key macros
fbclid, wacid, wasid, waid, utm_whop
captured
From the Whop 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 Whop 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.
8
Standard Whop events
3
API key permissions
28 days
Max event age
2.3B
Events tracked
Setup
Connected in four steps
You need a Whop business running ads, a company API key with company:basic:read, event:create and ad_campaign:basic:read, and a ClickFlare account.
Create the Whop API key In Whop, open the right business, go to Developer and click Create API key. Leave expiration and IP allow-list blank, choose Custom permissions, select all three and copy the key.
Add the Whop Conversion API In ClickFlare, open Integrations → Conversion API and select Whop. Click New Pixel, enter an account name and the key, set the Action Source and map events. Click Next and save.
Connect it to your campaign Open your Whop campaign in the campaign editor, select the Whop integration under Conversion API Integrations and save the campaign.
Add the cost integration In Integrations → Cost Tracking, select Whop, enter the API key and set Integration Timezone to your Whop timezone. Assign traffic sources created from the Whop template.
app.clickflare.com/integrations
WH
Whop
Ad platform
Connected
Whop account connected
Signed in from ClickFlare
Cost syncing
Spend matched to campaigns
Conversions sent back
Your chosen events
Whop template selected
Macros pre-filled
Tracking URL in Whop
Click ID captured
Conversions reported
Payout included where supported
Whop connected
Credentials saved in ClickFlare
Conversion event set
Click ID passed to the feed
Revenue syncing
On the feed's schedule
Whop added
Offer URL carries the click ID
Postback set in Whop
Payout and event included
Conversions arriving
Matched to the click
Whop connected
Click ID kept to checkout
Events mapped
View, cart, checkout, purchase
Purchases tracked
Order value in reports
Ready to track
Don't map a sale Whop processed to Purchase. Whop already records purchases made through its checkout, so mapping it again counts the sale twice.
{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Does ClickFlare integrate with Whop?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. ClickFlare sends conversions to Whop Ads through the Whop Events API and pulls Whop Ads spend through a cost integration, both with one company API key."}}, {"@type": "Question", "name": "Is it the same API key for cost and the Conversion API?", "acceptedAnswer": {"@type": "Answer", "text": "Yes, as long as it has all three permissions: company:basic:read, event:create and ad_campaign:basic:read."}}, {"@type": "Question", "name": "Can I send a custom event name to Whop?", "acceptedAnswer": {"@type": "Answer", "text": "No. Whop accepts its eight standard events. Map each ClickFlare conversion to the closest one."}}, {"@type": "Question", "name": "Do I still need the Whop pixel on my landing page?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. Whop requires its pixel on external landing pages before an ad can go live. The Conversion API adds the conversions the pixel can't see."}}, {"@type": "Question", "name": "Why doesn't my cost match Whop for a given day?", "acceptedAnswer": {"@type": "Answer", "text": "Almost always the Integration Timezone. Set it to the same timezone as your Whop account."}}, {"@type": "Question", "name": "Why are some conversions missing in Whop?", "acceptedAnswer": {"@type": "Answer", "text": "Whop rejects events more than 28 days old, such as a late affiliate postback. There is nothing to fix on ClickFlare's side."}}]}
Your Whop Ads campaigns, tracked to the sale.
One key for spend and events. Free 14-day trial and free migration from any tracker.