The OnlyFans Conversions API: server-side tracking that reports
A browser pixel can't see what happens on onlyfans.com. The Conversions API (CAPI) sends your subscriptions and purchases to Meta from a server, so they land in Ads Manager and your campaigns can optimise on them.
What is the Conversions API?
The Conversions API (CAPI) is Meta's server-to-server way of reporting conversions. A JavaScript pixel runs in the visitor's browser, where a growing share of traffic blocks it, throttles it, or strips it out. CAPI skips the browser. Your server sends the event straight to Meta with the match keys (fbclid, fbp, hashed contact data) it needs to attribute the conversion to the right ad.
Why OnlyFans funnels can’t live without it
The conversion you care about happens on onlyfans.com. That's the subscription, the PPV unlock, the tip on a paid message. It's also a page you can't add a pixel to. A browser pixel on your landing page sees the click and nothing after it. CAPI covers the rest. When the fan subscribes or spends, the event is sent server-side and matched back to the click that started it.
Which channel sends what
- PageViewthe visitor lands on your tracked page
- Leadearly intent signal before the redirect
- Subscribethe fan subscribes on OnlyFans
- Purchase · with valuetips, PPV & renewals, sent with revenue
Browser pixel alone vs pixel + CAPI
A pixel-only setup reports a shrinking slice of the truth. Add CAPI and the funnel becomes measurable end to end.
| Capability | Browser pixel only | Pixel + CAPI |
|---|---|---|
| Sees the landing-page click | ✓ | ✓ |
| Sees the OnlyFans subscription & purchase | ✗ | ✓ |
| Survives iOS / ATT restrictions | ✗ | ✓ |
| Survives ad blockers & ITP | ✗ | ✓ |
| Match keys captured at click time | ✗ | ✓ |
| Event de-duplication (shared ID) | — | ✓ |
How to set up the OnlyFans Conversions API
- Advertise a tracked landing pagePoint ads at a landing page that redirects to OnlyFans, not the raw OF link.
- Add your Pixel ID + CAPI tokenPaste them into the Meta settings once per creator.
- Events fire automaticallyPixel sends PageView/Lead; the server sends Subscribe/Purchase via CAPI with match keys captured at click time.
- Optimise on conversionsBuild subscriber lookalikes and read true ROAS instead of guessing.
Frequently asked questions
What is the Conversions API for OnlyFans?
The Conversions API (CAPI) is Meta's server-to-server channel for sending conversion events without the browser pixel. It matters for OnlyFans because the subscription and payment happen on onlyfans.com, where no pixel can run. The events are sent from a server instead, carrying the visitor's match keys.
Do I still need the Meta Pixel if I use CAPI?
Yes. They work together. The pixel fires top-of-funnel events (PageView, Lead) on your landing page, and CAPI sends the deeper conversions (Subscribe, Purchase) server-side. Send both with a shared event ID so Meta de-duplicates them and your match quality stays high.
What events should I send for an OnlyFans funnel?
Usually PageView and Lead from the pixel, then Subscribe and Purchase through CAPI when the fan subscribes or spends. Put a value on Purchase so Meta can optimise for revenue and not just count conversions.
How do I set up CAPI without coding?
Run your ads to a tracked landing page, then paste your Meta Pixel ID and a Conversions API access token into the settings once. The platform sends the server-side events for you. No custom server or developer needed.
