EvlPixel
Fanvue → Meta Conversions API

Your ads are flying blind.

Someone clicks your ad, lands on Fanvue, and subscribes three hours later. Meta never finds out. EvlPixel closes that loop — deterministically, in real time, for the whole lifetime of every fan you buy.

  ad click  ─→  /r/abc1234          fbclid, ip, user-agent captured
              ─→  fanvue.com/creator?fvc=…&metadata[fvp_cid]=c8k2m9x
              ─→  fan subscribes
              ─→  webhook: tracking.metadata.fvp_cid = c8k2m9x
              ─→  Meta CAPI: Subscribe  $9.99  predicted_ltv $175.00

Two events, two different worlds

The click happens on your domain. The conversion happens on Fanvue’s. Nothing links them — and Fanvue never exposes a fan’s email, so the usual trick of hashing it on both sides is off the table.

On your domain

The click

You can see fbclid, IP address, user-agent and UTM parameters. You cannot see who they become.

On fanvue.com

The conversion

A webhook naming a fan UUID and an amount. No click id, no email, nothing tying it back to an ad.

So we make Fanvue carry the receipt

Fanvue’s tracking links accept arbitrary per-impression metadata and echo it back on the conversion webhook. EvlPixel stamps its click id on the way out and reads it back on the way in — a real join through a third party, not a guess.

Deterministic attribution

Your click id round-trips through Fanvue’s own tracking links and comes back on the conversion webhook. Not an IP-and-timestamp guess.

Lifetime value, not first purchase

Attribution sticks to the fan. Every renewal, unlock and tip for months afterwards stays credited to the ad that brought them.

Real time, not polling

Fanvue pushes signed webhooks the moment something happens. Events reach Meta in seconds, with retries and an outbox behind them.

Every event mapped

Subscribers, renewals, purchases, tips and message milestones — each to a Meta standard event you choose, with value and currency.

Credentials encrypted

Meta tokens and Fanvue OAuth secrets are AES-256-GCM envelopes. A database dump alone cannot impersonate anyone.

Runs on the edge

One Cloudflare Worker. No servers, no queues to babysit, and a redirect fast enough that nobody notices it.

Live in an afternoon

Four steps. No servers, no SDK to install, nothing to deploy on your side.

Connect Fanvue

Authorise a creator account over OAuth. Webhooks register themselves, and the signing secret is stored encrypted.

Add your Meta pixel

Pixel ID and a Conversions API token. Send a test event and confirm Meta accepts it before a cent of spend goes out.

Point your ads at a tracking link

Each link is backed by a native Fanvue tracking link. That backing is what carries the click id across the boundary.

Watch revenue land

Conversions appear with the attribution tier that matched them, and what Meta said when it received them.

Stop optimising against nothing

Connect a creator, add a pixel, and see where the money actually comes from.

EvlPixel
Server-side conversion tracking for Fanvue creators.