Connect your own Whop account
Connect a Whop account you already own with a company API key, and pick the ad account Koast launches into.
If you already run ads through your own Whop company, connect it with a company API key. Koast then launches, edits and reports on that Whop ad account like any other. This is different from a Koast ad account, which Koast creates for you through our partner Whop. See Create a Koast ad account.
Before you start
Create a company API key in your Whop dashboard, under Developer. Whop starts every new key with no permissions, so tick all 13 of these:
| Permission | What stops working without it |
|---|---|
ad_campaign:basic:read | Reading your campaigns, ad sets, ads and targeting options. |
ad_campaign:create | Creating and duplicating campaigns, ad sets and ads. |
ad_campaign:update | Editing, pausing, resuming and deleting them. |
ad_campaign:stats:read | All spend, impressions and clicks. |
company:basic:read | Identifying your company and reading its settings. |
company:balance:read | Reading the ad account and its balance. |
company:update | Saving account settings. |
social_account:read | The identity your ads run under, its posts and lead forms. |
social_account:create | Connecting a social account. |
social_account:delete | Disconnecting one. |
audience:basic:read | Listing your custom audiences. |
audience:update | Creating, editing and deleting audiences. |
access_pass:basic:read | Listing your Whop products as ad destinations. |
Tick all 13
A key with missing permissions still connects. Whop doesn't tell Koast what a key can do, so Koast only finds out when it tries to use one and the call comes back refused. These are Whop's own permission names and Whop can rename them, so match them by what they do. Without ad_campaign:stats:read, for example, campaigns launch fine but Koast can't read results at all, and spend, impressions and clicks stay empty everywhere.
Connect the key
Open Settings, then Whop under Integrations. If this brand has no Whop key yet, Import from Whop in the brand switcher brings you here too.
Select Add API Key.
Paste the key into Company API key and select Connect.
Under "Choose the Whop ad account you want to integrate with this workspace.", pick the account from Ad account.
Select Confirm Selection. The page refreshes.
If the brand you're in already runs a Meta ad account, Koast puts the Whop account in a new brand of its own and switches you to it. Otherwise it lands on the current brand.
To bring in more ad accounts from the same key, use Import from Whop in the brand switcher. Each one becomes its own brand.
Replace or disconnect the key
The connected tab shows Currently integrated with your ad account, and two actions:
- Replace API Key swaps in a new key, for example one with more permissions.
- Disconnect deletes the stored key. Your ad accounts stay in Koast, but launching, Agent Tasks and reporting for them stop. Ads already live on Whop keep running, and Koast can't pause them until you reconnect. You'll need a new API key to do that, because the old one is gone.
Good to know
- You pay Whop directly. Ad spend on your own Whop account is billed by Whop. Koast doesn't charge it and doesn't need a card or a signed agreement for it.
- Server-side conversion keys don't work on an imported Whop account. The Koast pixel's server-side keys only work on Koast ad accounts.
- Anyone in your organization can open the Whop tab.
- What works on Whop. Most launch settings do. Carousels, lead forms and a few others don't. See What works on Meta and what works on Whop.