The funnel, event by event
Each stage of the OnlyFans journey maps to a Meta event. The upper-funnel ones fire in the browser; the ones that matter most — the subscription and the payment — are sent server-side, because they happen on onlyfans.com where no browser pixel can reach.
| Event | Stage | Sent | What it means |
|---|---|---|---|
| PageView | Landing | Browser + server | The fan arrives on your tracked landing page from the ad. This is the top of the funnel and the anchor for every match key that follows. |
| ViewContent | Engaged | Browser | The fan actually engages with the landing content — a signal of real interest, not an accidental tap. |
| Lead | Click-through | Server | The fan clicks through toward your OnlyFans profile. This is the last event you can see before they leave for onlyfans.com — invaluable for early optimization. |
| Subscribe | Subscription | Server (CAPI) | The fan subscribes on OnlyFans. Sent from the server once confirmed on the account, with the match keys from the original click attached. |
| Purchase | Payment | Server (CAPI) | The fan spends — a PPV unlock, a tip, a renewal. The event that actually correlates with revenue, delivered server-side. |
| Predicted Value | Valuation | Browser | An estimate of the fan’s real cross-model spending, sent back to the pixel so Meta has a value to optimize toward from day one. |
That’s six funnel events plus Predicted Value — seven signals in total, so Meta is never guessing from a single data point.
Why the whole funnel, not just Purchase?
It’s tempting to only send the event you care about — the payment. But Meta’s optimizer needs volume to exit the learning phase, and Purchase is the rarest event in the funnel. Firing the upper stages gives Meta enough signal to optimize while the account is still small, then you move the optimization event down the funnel as data accumulates.
Low volume → optimize for an upper-funnel event (Lead / landing click) to escape the learning phase. As Subscribe and Purchase volume grows, move the optimization event down toward the money.
Standard events, kept clean
Every event maps to a Meta standard event where possible — that’s what Meta’s optimization and value-optimization rules are built for. The custom data is deliberately lean: Meta-standard fields only, no internal IDs and no fan PII. That restraint is what keeps the events eligible for value optimization instead of getting quietly filtered out.
Questions
Which event should I optimize my ads for?
It depends on volume. New or low-traffic accounts often start on an upper-funnel event (like Lead or the landing click) to get out of the learning phase, then move down to Subscribe as data builds. High-volume accounts optimize directly for Subscribe or Purchase. The point of firing the whole funnel is that you can choose — and switch — without re-instrumenting anything.
Are these standard Meta events or custom ones?
They map to Meta’s standard events (PageView, ViewContent, Lead, Subscribe, Purchase) wherever possible, because standard events are what Meta’s optimization and value rules are built around. Custom data is kept lean and Meta-standard — no internal IDs or fan PII — which is what keeps the events eligible for optimization.
Why is Purchase sent server-side and not in the browser?
Because the payment happens on onlyfans.com, where no browser pixel can run. Subscribe and Purchase are delivered to Meta from a server via the Conversions API, after the event is confirmed on the account — not guessed in the browser.
What’s the “7th” event?
Predicted Value — a browser-side event that estimates a fan’s real, cross-model spending and sends it back to the pixel, so Meta has a value to optimize toward even though the first subscription is often free. It complements the server-side funnel rather than replacing it.
Fire the whole funnel, optimize on any stage
Get all seven signals into Meta and stop optimizing on a single sparse event.