Skip to main content
The Whop Pixel is a JavaScript snippet that you add to your website. It measures page views, links visitors to their purchases, and attributes conversion events back to your ads. Once installed, you’ll see your website in the Websites page.

Install the Whop Pixel

1

Get your Whop Account ID

Find it from your Whop Dashboard - the part of the URL after dashboard/, starting with biz_. Looks like biz_xxxxxxxxxxxxx.
2

Install the snippet

Paste this snippet inside the <head> of every page in your funnel — landing pages, advertorials, checkouts, and thank-you pages, not just your homepage. Replace biz_xxxxxxxxxxxxx with your own account ID.
Pixel snippet
Building your funnel on a platform instead of raw HTML? Use the dedicated install guide instead of pasting the snippet into a page builder text block.
3

Track events

If your funnel has important steps outside Whop checkout, like a lead form, call booking, or application, add whop.track calls to track those events.The most common setup is to fire events either:
  • when a form submits successfully
  • on the thank-you page or confirmation page the visitor sees after submitting
Tracking events
It’s important to include any information you have about the customer at every stage of the funnel. If you accept a lead with a name, email and phone number, include those in the event fired to Whop.

Standard events

The Whop Pixel includes a set of standard event names for common stages of a funnel. Each one optionally accepts a value (number) and currency ISO 4217 code).

Custom events

If Whop’s standard events don’t cover your funnel’s needs, or you want to track specific stages of the customer journey, you can fire custom events.
Custom event
Keep names short and stable, and reuse a small set. Whop stores names up to 250 characters.

Where to put the tracking call depends on what happens after the action

  • The action doesn’t redirect (e.g. a form that submits in place and shows an inline success message). Fire the event in the action’s success handler, such as the form’s onSubmit callback, after it succeeds:
Track on submit (no redirect)
  • The action redirects (e.g. a form that sends the visitor to a new page on submit). Fire the event on the page they land on, such as the thank-you or confirmation page. Make sure the pixel snippet is installed on that page too.

Give each event an ID

Pass an event_id with any event that could reach Whop more than once. For example, if you fire an event when landing on a thank you page, ensure that event is fired once per real conversion, not once per page view. Whop counts each event_name and event_id pair once, so a retry, a page refresh, or the same conversion sent from two places collapses into a single event.
Event with an ID
The ID identifies one single event, not the type of event. Every lead needs its own. Send "lead" as the ID for every lead and Whop treats them all as one event, so hundreds of leads show up as one. Use a value your own system already has for that one action — a lead ID, order number, or form submission ID. Reuse that value only when you’re sending that same action again. A retry counts as the same action. So does the same conversion mirrored from your server. A value made up at fire time is new every time, so it won’t stop duplicates. If the same conversion can come from both your website and your server, send the same event_id from both so it lands as one event.

Attach customer information

Always send as much customer information as you have available. This helps Whop match events to customers and improve conversion tracking. These fields can be attached to any event type and are optional. Send only the fields you have.
Lead with customer fields
Send these as plain text. A hashed email gets dropped because it isn’t a valid address. A hashed phone number gets stored as meaningless digits and matches nobody.
Don’t track purchases, subscriptions, or trials. Whop records every checkout view, purchase, subscription, and trial start server-side with zero configuration. The pixel won’t accept duplicates. Only send events Whop can’t see. Examples include leads and bookings on your own infrastructure.