Whop

TrueMetriks tracks every Whop sale and sends it back to your ad platforms. Here is how to set it up.

Set this up with AI

Copy this prompt into ChatGPT, Claude or whichever AI you use. It carries this whole guide, the pages it depends on, and a link to every video, so it can walk you through it one step at a time.

Open as text

Connect Whop to TrueMetriks

Video guide

How to connect Whop to TrueMetriks

Copy your webhook URL from TrueMetriks, create the webhook in Whop, then paste the signing secret back into TrueMetriks. The last two steps fire a test payment so you can confirm it works.

Step 1 - Open the Whop tile in TrueMetriks

In TrueMetriks, go to Settings > Integrations and click the highlighted Whop tile.

Integrations

Connect third-party data sources to fire events into TrueMetriks.

Typeform

Typeform

Connected

Calendly

Calendly

Connected

Microsoft Clarity

Configured (1 project)

stripe

Stripe

Connected

Whop

Not connected

In TrueMetriks, open Settings → Integrations and click the highlighted Whop tile.

Step 2 - Copy your webhook URL

On the Whop page, click the highlighted Copy button next to the Your webhook URL field. The URL looks like https://q.<your-domain>/w/whop. Keep this tab open - you will paste the signing secret back here in step 7.

Whop Not connected

Fire offline conversions when a Whop payment completes. Paste the webhook signing secret and add the URL below as a webhook endpoint in your Whop dashboard.

Your webhook URL

https://q.demo-brand.example/w/whop

Webhook signing secret

ws_...
Click the highlighted Copy button to copy your Whop webhook URL, then paste it into Whop's Endpoint URL field.

Step 3 - Open the Developer section in Whop

Open your Whop dashboard in another tab. In the left sidebar, click the highlighted Developer link, then scroll down to the Webhooks section.

  • Home
  • Payments
  • Users
  • Balances
  • CardsNew
  • Ads
  • Support chats

Pinned

  • Products
  • Checkout links
  • Invoices

All tools

  • Marketing
  • More
  • Developer
  • Settings
In your Whop dashboard, click Developer in the left sidebar.

Step 4 - Create a webhook

On the Webhooks page, click the highlighted + Create webhook button in the top right.

Webhooks

Send data and events that occur on Whop to third-party platforms. Docs

URL API version Secret Events Created

No webhooks yet

On the Webhooks page, click the highlighted + Create webhook button in the top right.

Step 5 - Configure the webhook

Fill in the Create webhook form:

  • Endpoint URL - paste the webhook URL you copied from TrueMetriks in step 2.
  • API version - leave it on V1.
  • Events - check payment_succeeded, refund_created and refund_updated, and nothing else.

payment_succeeded brings in every payment, and the two refund events take refunds off their payment. Do not also check membership_activated or invoice_paid - those would double-count the same payment.

Create webhook

Endpoint URL

https://q.demo-brand.example/w/whop
This URL should accept a raw payload. Discord or Slack URLs will not work.

API version

V1

Events

All
  • membership_activated
  • invoice_paid
  • payment_created
  • ✓payment_succeeded
  • payment_failed
  • payment_pending
  • ✓refund_created
  • ✓refund_updated
Paste your webhook URL, keep API version on V1, check payment_succeeded, refund_created and refund_updated, then Save webhook.

Click Save webhook.

Step 6 - Copy the signing secret

Whop creates the webhook and shows it in the table. Click the highlighted Secret value (ws_...) to copy it.

URL API version Secret Events Created
https://q.demo-brand.example v1 ws_3f9a…c1d8 1 7s ago

Showing 1 to 1 of 1

Click the highlighted signing secret to copy the ws_... value.

Step 7 - Paste the signing secret in TrueMetriks and click Connect Whop

Switch back to the TrueMetriks Whop tab. Paste the ws_... value into the Webhook signing secret field, then click the highlighted Connect Whop button.

Whop Not connected

Fire offline conversions when a Whop payment completes. Paste the webhook signing secret and add the URL below as a webhook endpoint in your Whop dashboard.

Your webhook URL

https://q.demo-brand.example/w/whop

Webhook signing secret

•••••••••••••••••••••••••••••••••••••
Paste the ws_... signing secret from Whop, then click the highlighted Connect Whop button.

Step 8 - Connected

The page flips to the connected state with a green Connected pill and the date you connected.

Whop Connected since 31/05/2026

Fire offline conversions when a Whop payment completes. Paste the webhook signing secret and add the URL below as a webhook endpoint in your Whop dashboard.

Your webhook URL

https://q.demo-brand.example/w/whop
Whop is now connected. Every payment_succeeded webhook fires a Purchase event into TrueMetriks.

Step 9 - Send a test event

You can confirm the whole pipeline without a real charge. Back in Whop, open the webhook's three-dots menu and click Test.

  • Edit
  • Test
  • View logs
  • Delete
  • Details ›
Open the webhook's three-dots menu and click Test.

Step 10 - Run the test

In the Test webhook dialog, select payment_succeeded and click Test. A response with "status": 200 and "success": true means TrueMetriks received and accepted the event.

Test webhook

Event

payment_succeeded

Response

{ "body": "{\"status\":\"ok\",\"amount\":6.9,\"currency\":\"USD\",\"email\":\"***\"}", "status": 200, "success": true }
Select payment_succeeded and click Test. A 200 status with "success": true confirms TrueMetriks received the event.

Subscriptions and renewals

Renewals need nothing extra. TrueMetriks labels each Whop payment as a new sale or a renewal.

The first payment of a membership is a new sale. Every later payment on the same membership is a renewal.

A plan change counts as a new sale.

Free trials. When a membership starts with a free trial, the $0 start is recorded and the first paid charge after it is the new sale.

Renewals inside TrueMetriks. A renewal stays a Purchase in your dashboard, so Total revenue includes it. It is credited to the channel that won the subscription's start (the first sale, or the trial signup for a free trial). This applies going forward: payments made before launch are not relabelled.

What your ad platforms receive. A first payment always goes to your ad platforms as a Purchase. For renewals, open Settings > Integrations, click the Subscription renewals tile and pick one under Send renewals to ad platforms as: a custom event (named Renewal unless you change it), a Purchase, or don't send. The tile shows the current choice. The setting is one per site and covers every payment source.

Sites that existed before this setting started on Purchase, so nothing changes for them until they pick another option. Sites created after launch start on a custom event named Renewal.

When renewals go out as a custom event or are not sent, they are not uploaded to Google Ads. When they go out as a Purchase, they upload to Google Ads like any other Purchase.

On Facebook, a custom conversion keyed on Purchase does not fire for a renewal sent as a custom event.

Known limits. A subscription that started before launch keeps its current crediting unless the source supplies a start date. A free trial that is running at launch labels its first paid charge as a renewal for one trial length.

See Revenue for how renewals show in your dashboard.

Refunds

Refunds need the refund_created and refund_updated events from Step 5. If you connected Whop before refunds were supported, open the webhook in Whop, check both events and save.

A refund in Whop is taken off the payment it belongs to. The payment keeps its date and its ad, so the refund lowers revenue, ROAS and profit on the day of the payment. See Refunds on the Revenue page.

A refund counts once it has gone through. A refund Whop reports as pending or failed changes nothing until Whop says it succeeded.

Two refunds of one payment both count.

Refunds never go to your ad platforms. They only change your numbers in TrueMetriks.

Verify

Anytime a payment triggers in Whop, you will see the matching Purchase event inside the TrueMetriks dashboard. The Step 10 test is the quickest way to confirm the wiring - the test payload is sample data, so it will not connect to a real ad journey, but the Purchase still lands in the visitor timeline:

First visit

0 Purchase 1 Direct May 31, 1:45 PM
Timeline Visit info
1 Purchase 1:45:38 PM
currency: USD items: [{"name":"Whop Purchase","price":6… order_id: pay_xxxxxxxxxxxxx value: 6.9
The test Purchase lands in the visitor's visit timeline within seconds, with the value, currency, and order_id from Whop.

If the customer's journey is connected to an ad, we forward that Purchase to every connected ad platform - Facebook CAPI, Google Ads, GA4, TikTok - so the same revenue lands in their reports too.

Frequently asked questions

Which Whop event should the webhook listen for?

payment_succeeded for payments, plus refund_created and refund_updated for refunds. payment_succeeded fires on the initial purchase and on every subscription renewal, so it covers all revenue, and TrueMetriks labels each payment as a new sale or a renewal. Do not add membership_activated or invoice_paid, since they would double-count.

Can I confirm the connection without a real charge?

Yes. Open the webhook's three-dots menu in Whop, click Test, select payment_succeeded, and run it. A response with status 200 and success true means TrueMetriks received and accepted the event.

Does the Whop revenue reach my ad platforms?

Yes. If the customer's journey is connected to an ad, TrueMetriks forwards the Purchase to every connected platform: Facebook CAPI, Google Ads, GA4, and TikTok.

Are Whop refunds taken off my revenue?

Yes, with refund_created and refund_updated checked on the webhook. A refund is taken off the payment it belongs to, on the payment's date, and is never sent to your ad platforms.

Need help with this?

Reach us instantly on WhatsApp, or send us a message and we will get back to you. On workdays we usually respond in less than 24 hours.

or send us a message