Whop to Meta Conversions API.
Send every Whop sale to Meta so ads optimize on real revenue. Each payment reaches your Meta Pixel with the ad click attached.
What gets sent.
| DATALYR event | When it fires | Sent to Meta as | What it carries |
|---|---|---|---|
| purchase | A Whop payment succeeds: one-time, first subscription payment or recurring | Purchase | Whop's creator-facing total (excludes buyer fees), currency, the ad click, and hashed email |
| subscribe | A membership activates. Optional rule | Subscribe | The membership, with no value |
| payment.refunded | A refund succeeds | Not sent | The rule editor blocks a refund trigger aimed at a purchase event |
How it's matched.
DATALYR checks these in order and stops at the first one that finds the ad click.
- The visit DATALYR recorded on your own pages before the Whop checkout
- The customer email, which must match the one used on your site
Meta gets the click ID (fbc, built from the _fbc cookie or fbclid) and browser ID (fbp), plus email, phone and name hashed with SHA-256 when known. DATALYR sends the same event ID the browser pixel uses, so Meta merges the pair into one conversion.
How it works.
- 01
Connect Whop.
Open Sources, select connect on Whop, then enter a restricted Account API key and your biz_ company ID. DATALYR creates the signed webhook and turns on the official Whop Pixel. Tracking must run on every page before the Whop checkout.
- 02
Connect Meta.
Open Sources, select connect on Meta Ads and sign in with Facebook Login for Business. Set the primary ad account. In Conversions, select manage rules, then new rule: trigger event purchase, target platform Meta, your pixel, platform event Purchase. Set value to dynamic and pick the currency.
- 03
Check one conversion.
Complete one low-value Whop purchase from a Meta ad click. Find purchase in Events, then open the newest row in Conversions and read the reply from Meta.
Check it worked.
- In Events, the purchase carries the payment value and the campaign. No campaign means DATALYR found no matching visit: confirm tracking runs before checkout and the same email is used at Whop.
- Set a Test Events code on the rule, then select send test event. The event shows in Events Manager under Test events with the name, value and currency you mapped. Without a code, a test is a real conversion.
- Open the newest row in Conversions. Its status reads sent, and the response body carries Meta's own acceptance field.
View docsWhopMeta AdsConversion delivery
Questions, answered.
Contact usNot the same purchase to the same Meta destination. Whop Ads can send purchases to Meta, and a second sender makes Meta report two purchases. Use DATALYR rules for destinations Whop does not already feed, or disable one of the two Meta paths.
No setup. When you connect Whop, DATALYR creates the signed webhook and turns on the official Whop Pixel on your tracked pages.
The Whop total for the payment, which excludes buyer fees. DATALYR does not subtract processing fees or disputes, so compare it with creator-facing totals after succeeded refunds.

See what really drives revenue.
Real-time attribution, analytics and conversions for every channel, campaign and ad, ready for your team and your agents.