The Whop Ads integration is currently in beta. It is live and you can set it up today, but it is still being rolled out, so speak to your account manager before you build a campaign around it.
Overview
Some advertisers cannot run their own ad platform pixels. In industries such as telehealth, supplements and financial offers, ad accounts get flagged and shut off, and partners are reluctant to put a brand's pixel on their own domains. The Whop Ads Integration solves that by sending accurate conversion data via server-to-server (S2S) postbacks from your advertising campaigns to Everflow. Everflow then sends the data, along with the click context, to Whop to distribute the data to ad platforms such as Meta (available on Google and TikTok soon).
By using the Whop Ads Integration, you can optimize your campaigns and track your conversions securely without the risk of running browser-side tracking on your website.
How the Whop Ads Integration Works with Everflow
Once you set up the Whop Ads Integration in Everflow, Everflow and Whop work together to send server-side conversion data to track your conversion events.
utm_whop=true to the Offer URL to mark Whop traffic.Why the Whop Ads Integration is Unique
The Whop Ads Integration is supported by the Whop Conversions API (CAPI). There are two main differences between the Whop CAPI and a standard CAPI: automatic data transfer and click context.
1. Automatic Data Transfer
2. Click Context Capture
utm_whop=true automatically to your Offer URL.utm_whop=true on the incoming URL from Whop and stores the required click context without impacting your standard traffic or active efforts.Prerequisites
Ensure that you have following requirements to set up your Whop Ads Integration in Everflow:
event:create write permissionsBefore you begin
Set up your Whop Ads Integration.
No Whop account yet?
You need one before any of the steps below. Creating a business in Whop gives you the Account ID and the Developer area where the API key lives.
If you have an existing Whop account, but you do not have API access, ask your Whop contact.
biz_ followed by alphanumeric characters, such as biz_a12Bc45DEfgH.

event:create permissions.


Do not store the API key in browser code, mobile apps, or public repositories.
Step-by-Step Guide
account_ID is sent on every event.event:create permissions.

{transaction_ID} or {sub_ID}.{payout}, {revenue}, or {sale_amount}, or a hardcoded monetary value.Troubleshooting
utm_whop=true flag on the incoming URL, this means that the traffic didn’t come from Whop.utm_whop=true flag is appended to the incoming URL, then there is a problem with the Everflow JS SDK.Limitations
This integration does not report the sales that Whop processes. Whop records its own checkouts, subscriptions, and trials server-side.
If you have both the Whop pixel and the SDK installed on the landing page, then this setup will result in duplicate record counting.
This integration sends conversion events. The Whop Ads Integration does not touch the rest of the Whop product, and Everflow does not hold Whop's own identifiers for users, members, memberships, products or plans. Whop memberships, products and plans, payments and checkout, and Whop webhooks are all outside its scope.