Skip to main content
Thanks to ClickFlare’s API integration with Whop, you can automatically pull the cost data of your Whop Ads campaigns into ClickFlare. Spend lands next to the clicks and conversions ClickFlare already tracks, so profit, ROI and CPA are accurate without manual cost uploads. In this article we go through the setup step by step.

​
What you’ll need for the integration

ClickFlare account

An active account

Whop Ads business

A business running ads

Whop API key

Created in Whop
One key per business. Whop generates API keys per business, and the same key powers both the Whop Conversion API and the Whop cost integration. If you run several Whop businesses, create a key in each and register each business in ClickFlare separately.

​
How the Whop cost integration works

ClickFlare connects to Whop’s API with your key and retrieves the spend of the Whop Ads campaigns in that business, at all three levels:
  • Campaign level
  • Ad group level
  • Ad level
So you can break cost down by Whop campaign, ad group or ad in your ClickFlare reports, not only see a campaign total. Only spend is fetched from Whop. CPC, CPM, CTR, ROI and the other performance metrics are calculated inside ClickFlare, from Whop’s cost and the clicks and conversions ClickFlare tracks through your campaign URLs. This keeps every metric consistent in one report.

​
Where to find your Whop API key

1

Open the right business

Log in to Whop and select the business you run ads from in the business switcher at the top left. The key belongs to the business that is open.The Whop dashboard with the business switcher at the top left and Developer at the bottom of the sidebar
2

Go to Developer

Click Developer at the bottom of the left sidebar. The Company API keys section lists the keys for this business.The Company API keys section of the Whop Developer page, with the Create API key button
3

Create the key

Click Create API key and fill in the form:The Create API key form in Whop
4

Choose the permissions

Open Inherit permissions from role and choose Custom.The role dropdown with Owner, Admin, Moderator and CustomUse Search permissions to find and select these three:Select all three even if you only set up one integration today. The same key then works for both.
5

Copy the key

Save the key and copy it straight away. Afterwards the list shows only a masked version such as apik_NiPR…1185.

​
Setting up the Whop cost integration

1

Open the Cost Tracking integrations

In ClickFlare, go to Integrations in the left-side menu and open the Cost Tracking tab. Click Add integration.The Cost Tracking tab of the Integrations page, with the Add integration button
2

Select Whop

Select Whop from the list of available integrations.The New Integration picker with Whop among the cost integrations
3

Enter the details

Fill in the form:
  • Name — a recognisable name, for example the Whop business name.
  • Workspace — Public to use it across your account, or a specific workspace. See Managing cost and CAPI integrations in workspaces.
  • API Key — the Whop company API key.
  • Integration Timezone — set it to your Whop timezone.
If the integration timezone differs from Whop’s, each day’s spend is split across the wrong days, and cost in ClickFlare will not match Whop for any given day or hour.
Click Save.The Whop cost integration form with Name, Workspace, API Key and Integration Timezone
4

Optionally, assign traffic sources

ClickFlare asks which Traffic Sources should use this integration. Select your Whop traffic source configurations here, or skip the step and assign the integration later from the traffic source settings.The Traffic Sources dialog with an optional Select Traffic Sources field
Select only traffic sources created from the Whop template. Spend cannot be matched to campaigns running on a different traffic source.
Click Save.
5

Add the integration to your traffic source

If you skipped the previous step, open your Whop traffic source and select the new integration under Cost Integration.
If the integration is not assigned to the traffic source, ClickFlare does not pull cost for its campaigns, even though the integration itself is saved and enabled.

​
Verify cost data sync

After you save, ClickFlare starts syncing cost from Whop automatically.
  1. Open an active Whop campaign in your ClickFlare reports.
  2. Look at the Cost column.
  3. Compare it with the spend in Whop’s ads reporting for the same day, allowing for the sync delay.
Sync frequency. How often cost updates depends on your ClickFlare plan and whether you have a faster cost-update add-on. It ranges from every 60 minutes down to every 5 minutes. See Cost updates.

​
How cost matching works

Whop adds its own IDs to the URL a visitor lands on after clicking a Whop ad: wacid for the campaign, wasid for the ad group and waid for the ad. ClickFlare captures them through the Whop traffic source template and uses them to line up the spend it pulls with the right campaigns, ad groups and ads. When you create the traffic source from the template, these parameters are already in place: The New Traffic Source form created from the Whop template, with the Whop parameters pre-filled
Do not remove or rename the wacid, wasid and waid parameters. Without them ClickFlare cannot tell which Whop campaign, ad group or ad a click came from, and the pulled spend cannot be matched.
To create the traffic source, see How to add a traffic source from a template.

​
Frequently asked questions

Yes. One company API key per Whop business covers both, as long as it has all three permissions: company:basic:read, event:create and ad_campaign:basic:read.
Yes. Create a key in each business and add one cost integration per key. Assign each integration to the traffic source configurations that run that business’s ads.
It pulls spend. Clicks and conversions are tracked by ClickFlare itself, and combined with Whop’s cost for full performance reporting.
Almost always the Integration Timezone. It must be the same as your Whop timezone. Edit the integration and set it to match.

​
Troubleshooting

For the general checklist, see Cost not pulling.