Playbook — OnlyFans

OnlyFans Playbook: The Creator-Sub Funnel, With Telegram or Server-to-Server

Running OnlyFans traffic on Leadgram is one creator, one price, and two ways in - and this playbook wires both to the same conversion so you can tell which one actually pays. The live setup targets US and DE: campaign OF — Creator subs, offer CreatorHub Sub ($4, geo US/DE), and a single metric that counts - the creator subscription. Everything below hangs off that.

With Telegram: the bot funnel

The Telegram path starts where your traffic already lives - a bot or a channel. A tracking link carries the click into the bot with its clickId attached, so the person who taps the ad and the person who subscribes are the same row from the first second. From /start onward the Message Flow OF — fan onboarding does the talking: it warms the fan, drops the age check, and hands over the subscribe button, each step timed instead of dumped at once. The subscription fires the conversion that matters; because the click id rode the whole way in, it maps straight back to the campaign, the geo and the sub that produced it. Bind the flow to the bot inside the campaign so even a broken deep-link still resolves.

Bot funnel: tracking link → fan onboarding flow → a paid creator sub.

Without Telegram: landing plus S2S

No Telegram in the funnel? The click lands on Creator preland (/creator-of) instead, and the money end is the offer CreatorHub Sub. Between the two sits the Click Flow OF — age-gate split: it runs the 18+ gate and routes US and DE down their own branch before anyone reaches the offer, so a failed age check never burns a view on the paywall. The subscription happens on the creator's side, off Leadgram, so you report it back yourself: fire a conversion through the events API with the clickId you passed into the lander, and let postbacks forward it to your ad platform. Same conversion, same creator sub - just delivered server-to-server instead of through a bot.

Landing plus S2S: age-gate split → CreatorHub Sub, conversion via events API and postbacks.

From a media buyer's seat

The pain is always attribution: creator subs settle on a third-party page, hours after the click, and by default the ad platform never hears about it. Both setups above close that gap in different lanes - the bot path keeps the click id inside Telegram, the S2S path carries it into the lander and back out through the events API. Setup is an afternoon: one campaign, one offer at $4, one flow, done once per geo. What you get is a Reports table where EPC and ROI on OF — Creator subs sit next to the spend, split by US vs DE, so scaling the winning geo and killing the other is one glance rather than a reconciliation spreadsheet. The two clips below tell that story from the buyer's chair.

How the bot funnel looks from the media buyer's seat.
How the landing plus S2S funnel looks from the media buyer's seat.

Where to go next

Whichever path you run, send back exactly one conversion per subscription. The bot flow already fires the creator sub, so if you ALSO post it through the events API with the same click, you get a second event your optimizer reads as two buyers. Pick one producer per funnel, not both.