ProductsLinkTroubleshooting
"The click is in our numbers but Club shows nothing"
Link and Club track two different, deliberately separate facts — a click is not a sale, and Link never becomes one.
Symptom
The traffic dashboard shows the click, the redirect worked, the fan landed on OnlyFans — but Club's fan list, revenue dashboard, or source-attribution screen shows nothing for them.
Cause
This is not a bug in either product — it's the boundary working as designed. Link owns the click/impression event and the link it pointed at; it never decides whether that click turned into a sale, how much money moved, or which fan the payment belongs to. See Boundaries for the full split. Concretely:
- A click becoming a subscription, a tip, or a PPV sale is Club's
OfConversion/OfTransactionmachinery — Link's click row has no revenue field to populate. - Which fan a source or campaign belongs to is resolved by Club, reading Link's raw click/link data as input, not by Link itself.
- Not every click converts. A visitor who clicks and never subscribes is a normal, expected outcome, not a missing-data bug.
How to check
- Confirm the click itself is real first: the traffic dashboard and the domain's own click
report both draw from the same
Clickrows Link's redirect layer writes — if it's not there, the problem is upstream of Club entirely (redirect, bot filter, retention window; see Traffic troubleshooting). - If the click is confirmed and the fan genuinely did subscribe, the gap is in Club's resolution, not Link's event — that's Club's attribution surface, not this product's.
- Telegram-gate traffic is the one path where Link writes a join key Club consumes
directly (
tg_bot_starts); if that specific path looks broken, check Telegram gate troubleshooting for the webhook/rule side first.
What's next
A traffic-source rule matches but the fan still isn't attributed — the same Link/Club split, for source rules specifically.