Skip to main content
Use this setup when customers discover an offer on your site and pay through Whop. It connects the content or campaign that created demand to the purchase and subscription events reported by Whop.

​
Before you start

You need access to the landing site, Datalyr’s Whop source, and the Whop business receiving payments. Choose the acquisition platforms you want to measure and the purchase event you will use for optimization.

​
1. Track the landing experience

Install web tracking on every page that can introduce or sell the offer. Verify a pageview before changing the checkout. Track meaningful steps such as offer views or checkout starts only when they help you answer a real funnel question.

​
2. Pass identity into Whop

When creating a supported checkout, use getWhopCheckoutMetadata() from the Web SDK and pass the returned values into the checkout flow. This creates the bridge between the anonymous visitor and the transaction Whop later reports. Do not invent or cache your own visitor identifier. Request the metadata when the checkout begins so the current visitor is used.

​
3. Connect Whop revenue

Open Sources → Whop, complete the connection, and configure the webhook shown in the setup flow. Whop should remain the authority for purchases, recurring payments, refunds, and membership changes.

​
4. Connect acquisition platforms

Connect the ad accounts used to promote the offer. Create a conversion rule for the first successful purchase or another event that reflects your actual optimization goal. Avoid sending routine renewals as new-customer purchases unless that behavior is intentional.

​
5. Verify end to end

Open the landing page in a private window with test campaign parameters, proceed through checkout, and complete a test purchase. Confirm:
  • The landing visit and checkout belong to the same journey
  • The purchase has the correct value, currency, customer, and transaction ID
  • The acquisition source is retained
  • The selected ad destination receives the test conversion
  • A refund or renewal updates the same customer when tested

​
Common problems

  • Unattributed purchases: checkout metadata was omitted or created before Datalyr initialized.
  • Visits are missing: tracking is not installed on the first landing page or is blocked by consent configuration.
  • Duplicate revenue: the same purchase is being sent by Whop and custom application code.
  • Wrong optimization counts: recurring events are included in a new-customer conversion rule.

​
You are done when

One test buyer has a continuous journey from campaign visit to Whop purchase, with correct revenue and a verified conversion in the intended destination. See Whop revenue for connection and checkout metadata details.