FlowTracker tracked links carry the click id and your full campaign context into the Whop checkout, send the conversion back server-side, and pull your Whop ad spend into the same report as your revenue. Ads only, nothing else in your Whop touched.
A Whop checkout is a different domain to your funnel, which is where most attribution quietly breaks. The tracked link carries the context across, and FlowTracker posts the conversion back with it attached.
The tracked link captures fbclid, gclid and ttclid at the moment of the click and hands them through to your Whop checkout, so the sale lands on the ad that caused it instead of on direct traffic.
Campaign, ad set, ad, tracked link, geo, channel, tags and your own custom properties travel with the event into Whop, so the data you segment on in FlowTracker is the same data you can read in Whop.
FlowTracker sends the conversion server-side with the same event_id the Whop Pixel used in the browser. Whop matches them and counts one conversion, so ad blockers cost you data but never double count you.
Spend, impressions, clicks, results, ROAS, CTR, CPC, CPM, cost per result, frequency and reach are pulled per campaign, ad group and individual ad, hourly through monthly.
Whop ad spend sits in the same report as your product revenue and affiliate commission, so the number you look at is what you actually kept, not just what came in.
A Telegram join, a first reply, an application submitted. Map any FlowTracker event to a Whop standard event or a custom name so optimisation sees the whole funnel, not only the final purchase.
FlowTracker writes ad events into Whop and reads ad reports out of it. It does not create, edit or read your products, plans, memberships, licences, payouts, affiliate programme or community content. If you already run your business on Whop, nothing about how you run it changes. The only thing that changes is that you can finally see which ad paid for each sale, and what that ad cost.
No code, no pixel surgery, no developer.
Paste a Whop API key and your business id. FlowTracker asks for read access to ad reports and write access to events, and nothing beyond that.
Build the link in FlowTracker the way you already do. It captures the click id, stamps the campaign context, and forwards both through to the checkout URL.
Choose which FlowTracker events fire into Whop and which Whop event each one becomes. Standard names such as lead, complete_registration, view_content, add_to_cart, schedule, submit_application and contact are there, and custom names are accepted.
Whop ad spend and results land next to your revenue in FlowTracker Reports, broken down by campaign, ad group and ad, so you can kill the losers on the same screen you found them.
No. It runs alongside it. The Whop Pixel keeps doing browser-side tracking, and FlowTracker sends the same conversions server-side with a matching event_id so Whop deduplicates them and counts one conversion, not two.
Only the advertising context attached to the event: the click ids captured by the tracked link (fbclid, gclid, ttclid), campaign, ad set and ad, the tracked link itself, the FlowTracker visitor id, and the customer identifiers you already collect such as email, phone, country and external id. Nothing from your inbox threads or CRM notes is sent.
No. This integration is scoped to advertising. FlowTracker does not create, edit or read products, plans, memberships, licences, payouts, affiliates or community content on Whop. It writes ad events and reads ad reports, and that is all.
Spend, impressions, clicks, results, ROAS as reported by the ad platform, click-through rate, cost per click, cost per mille, cost per result, frequency and reach. They arrive broken down by campaign, ad group and individual ad, and can be bucketed hourly, daily, weekly or monthly.
Whatever your Whop ad account is running. Whop Ads buys on Meta today with more platforms being added, and FlowTracker reads whatever is in the account rather than connecting to each platform separately.
Yes. Any event FlowTracker sees can be mapped to a Whop standard event such as lead, complete_registration, view_content, add_to_cart, schedule, submit_application or contact, or to a custom event name of your own. A Telegram join or a first reply in the inbox can fire into Whop the same way a purchase does.
No. You paste a Whop API key and your business id, choose which events map to which Whop events, and point your tracked links at your Whop checkout. There is no code to deploy.
Connect Whop, point your tracked links at the checkout, and watch every sale find its way back to the ad that paid for it.