EvlPixel

Meta pixel Sign in Get started

Meta Pixel for Fanvue

Fanvue gives creators no way to install a tracking script, so the browser pixel never fires where the money happens. This is what actually works instead, and why.

Why the browser pixel cannot work

A Meta pixel is a script that runs on a page you control. On Fanvue you control no pages: the profile, the subscribe flow and the checkout are all rendered by Fanvue on fanvue.com, and there is no field anywhere in the creator settings to paste a pixel ID into.

So the conversion happens somewhere your pixel cannot reach. You can point ads at a Fanvue link and watch clicks accumulate, but Meta never learns that any of those clicks became a paying subscriber. The optimiser has nothing to optimise towards, and every campaign looks equally bad.

What works instead: the Conversions API

Meta's Conversions API accepts events from a server rather than a browser. Nothing has to run on Fanvue's pages — something just has to know the conversion happened and be able to describe who it happened to.

That splits the problem into two halves:

1. Knowing about the conversion. Fanvue's public API sends real-time webhooks: creator.subscription.activated when someone subscribes, creator.payment.succeeded for every purchase, renewal and tip.
2. Knowing which ad click it belongs to. Harder, and where most tools quietly give up.

The attribution problem, honestly

When Meta sends someone to your link it appends fbclid. That parameter is the only thing tying a visitor to an ad. If your ad points straight at Fanvue, the parameter lands on fanvue.com and is gone.

So the click has to pass through a domain you control first:

ad click → your-domain.com/r/spring  ← fbclid, IP and user agent captured here
                                     → fanvue.com/creator

Now you have the click. The remaining question is how to recognise the same person hours later, when Fanvue reports a subscription — using a webhook that identifies the fan by a UUID you have never seen, and that never includes their email address. Fanvue documents purchaser.email as always null, so the usual trick of hashing the email on both sides is unavailable.

The weak answer

Most tools match on IP address and timing: same IP, roughly the right moment, call it a match. On mobile traffic, where carrier-grade NAT puts thousands of people behind one address, this produces confident-looking numbers that are partly fiction.

The reliable answer

Fanvue has its own tracking-link system, and it echoes arbitrary per-impression metadata back on the conversion webhook. So a click identifier can be sent out with the visitor and read back when they convert — a real join through Fanvue itself, rather than a guess:

→ fanvue.com/creator?fvc=fv-123456&metadata[cid]=c8k2m9x

webhook: { "type": "creator.subscription.activated",
           "tracking": { "metadata": { "cid": "c8k2m9x" } } }

That identifier points back at the stored click, which holds the fbclid. From it the Conversions API event is assembled with a correctly reconstructed fbc — built from the click's own timestamp, not the send time, because using "now" tells Meta every click just happened and corrupts the recency signal attribution depends on.

What gets reported

Fanvue event	Meta event	Value
Click on a tracking link	ViewContent	—
New subscriber	Subscribe	subscription price
Subscription renewal	Purchase	amount charged
PPV unlock or media purchase	Purchase	amount charged
Tip	Purchase	tip amount
Fan sends a first message	Contact	—
Fan sends a third message	Lead	—

One detail worth getting right: the initial subscription charge arrives from Fanvue twice — once as a subscription event, once as a payment. Reporting both doubles the revenue credited to a single ad. It should be sent once.

Lifetime value, not first purchase

A subscriber worth $9.99 on day one may spend $500 over six months. If only the signup is reported, Meta learns to find cheap subscribers who never buy again. Attribution has to stick to the fan so every later renewal, unlock and tip stays credited to the ad that brought them — and the Subscribe event should carry a predicted_ltv reflecting what fans from that link actually went on to spend.

Common questions