EvlPixel

Meta pixel Log in Get started

Fanvue marketing: the decisions, in order

Organic posting is paid in hours, paid traffic per click, and Fanvue’s affiliate programme out of money that already arrived. Which to use is the first decision. Then where to post, what has to exist before any spend, what a fan is worth, what to measure, and whether to hire anyone. This is that order — with what is knowable at each step, and what has to be assumed.

Which of the three routes to use

Three ways exist to get a stranger onto a Fanvue page, and they differ in when the money leaves. Organic posting is paid in hours, up front. Paid traffic is paid per click, up front. Neither refunds anything if nobody subscribes. Fanvue’s affiliate programme is paid as a percentage of money that has already arrived. Only the third cannot lose, and it is the one fewest people have read the terms of.

Under the Creator Affiliate Programme one creator promotes another’s profile and the promoted creator sets the rate. Fanvue’s Creator Referral & Affiliate Policy caps that rate at 50% of Fan Payments, caps total commission at $50,000 per promoted creator, and applies it to every Fan Payment the referred user generates on that profile — subscriptions, renewals and one-time purchases, not only the first charge. No end date is stated. One creator may act as an affiliate for at most five promoted creators at a time.

The funding clause is where the arithmetic bites. Commission is calculated on the full value of qualifying Fan Payments and paid out of the promoted creator’s net earnings. Those are two different bases in one sentence: the percentage is taken on gross, the money comes out of your 80% net. At the 50% cap you keep 30% of what the fan paid. At ten percent you keep 70%. The rate is not the number to compare. What you retain is.

Two further limits. Attribution for a logged-out click rests on a cookie on the device, with no duration stated, so a fan who clicks on a phone and subscribes on a laptop may not attribute at all; a logged-in click attaches to the Fanvue account instead. And once an offer has been accepted, the policy states that promoted creators cannot currently remove individual affiliate links. A rate set carelessly is not easily unset.

One correction, because the opposite is widely repeated: the ban on paid search advertising sits in the referral scheme and covers referral links. The affiliate promotion standards permit any lawful traffic source, given disclosure. The referral scheme is the separate thing — 5% of a referred creator’s earnings for 12 months, capped at $50,000 — and its window was cut from 36 months in April 2026. These terms move. Read them, not a summary of them.

Where to post, and what each surface allows

Every route below earns or buys the same three stages: someone sees you on a surface you do not own, they tap a link, they pay Fanvue. Only the middle stage is counted by the outside platform, and only the last is counted by Fanvue. Nothing joins the two automatically. Instagram never learns that a fan paid, and Fanvue never learns which reel they watched. The one thing that crosses is a link you made on purpose, before the traffic arrived.

Surface	What it costs	What the rules allow	What you can measure
Instagram and Threads	Hours	Meta’s community standards govern ordinary posts, not its ad rules, and they prohibit content containing usernames or links to pornographic websites	One bio link, so one number for the whole account
TikTok	Hours, plus account risk	The tightest moderation here, and link fields are gated by account status. Check what your own account offers rather than a threshold quoted in a blog post	Bio link only, and the in-app browser is routinely misfiled as a bot
Reddit	Hours, plus account seasoning	Paid links are ordinary rather than tolerated. Rules are set per subreddit and vary more between communities than between platforms	One link per subreddit, so earnings per subreddit
X	Hours	Adult content is permitted when consensually produced and labelled, and labelled posts are held back from recommendation surfaces. Reach is the price of the permission	One link per post, cleanly
YouTube	Production hours	The upload rules are looser than the link rules. The external links policy bans links to pornography, and counts obfuscated URLs and verbally directing viewers as links	One link per video, joined to YouTube’s own click data
Meta ads	Money	The reverse of the organic rule. Ads carrying usernames, links and logos of adult subscription websites are permitted to an 18+ audience; nude and sexually suggestive imagery is not	Everything, but only once conversions are reported from a server
Fanvue Discover	A toggle	Settings, Creator Settings, Profile. Off, and fans cannot find you in Discover or search at all, though the profile stays reachable by direct link	Nothing. It arrives unattributed

Read the Instagram and Meta ads rows together, because the asymmetry is the most useful thing here and almost nobody states it. Meta’s advertising standards permit the link. Its community standards, which govern ordinary posts, do not extend the same allowance. The 18+ carve-out exists because an advertiser sets an audience age, and an organic post has no audience age to set. On the link itself the paid route is the permissive one, and the free route is where accounts quietly disappear. Whether a given profile is read as falling inside those words is Meta’s call, not yours, and both documents get rewritten — so check the current text before building anything on a particular reading of it, and see Meta ads for a Fanvue page for how the separate standards interact.

What has to exist before the first pound of spend

Paid traffic multiplies the rate at which a page converts a stranger. It does not discover that rate. Spend against an unknown conversion rate and you buy an unknown number of subscribers at a very knowable cost.

Must exist before spend	What breaks without it
At least 20 pieces of content live	Fanvue’s own stated threshold before promoting actively. A near-empty page converts a curious visitor at close to zero, and spend multiplies that rate rather than replacing it.
Discoverability on, intro video uploaded	The only distribution the platform gives away, and the intro video is what surfaces there. With the toggle off a fan cannot find you in Discover or search at all.
A price decided on deliberately	$3.99 to $100 a month, and it sets the numerator of every calculation below. Fanvue’s own guidance is inconsistent — one help article says $5 to $30, another $10 to $30 — so treat the low-to-mid tens as a band, not a formula.
One tracking link per source, created before the traffic	Acquisition is first-click, and a user is only counted against the first link they clicked. A fan who arrives before the link exists is unattributed permanently.
A naming scheme for those links	No update endpoint is documented, so name and channel are fixed at creation. Deleting and recreating gives a link with clicks at zero and earnings null.

The fourth row separates a page that can be measured from one that cannot, and it costs nothing on the day it is set up. Retrofitting it costs every fan acquired in the meantime — what Fanvue’s tracking links measure covers the object field by field.

What a fan is worth, and where the number comes from

The figure that caps a bid is not the subscription price. It is net revenue per acquired fan across that fan’s life, and ads are paid for in gross money before any of it arrives. Three things sit in between.

The platform fee. Fanvue’s creator earnings policy sets the standard Creator Earning Rate at 80% of gross revenue from paid-for services, with 20% retained as platform fees. Promotional Earning Rates exist, and the policy defines them as temporary, fixed-period uplifts. Model on 80%, and model on any better rate expiring.

The clearing delay. Funds sit through a standard seven-day pending period, extendable to twenty-eight, and payout requests are initiated within ten business days. Ad platforms bill on a different schedule, so a campaign profitable on paper can still be a cash-flow problem — which caps scaling speed more often than creative does.

Where the number comes from. A tracking link carries an earnings object with gross and net totals and an engagement object with acquired and total subscribers. No new software is needed for a first estimate.

value per acquired fan  =  earnings.totalNet / engagement.acquiredSubscribers

  totalNet             lifetime total, no timestamp, no currency field
  acquiredSubscribers  first-click, this link only

Three caveats apply, and they do not cancel out.

• The earnings total has no time dimension. On a three-week-old link it understates a fan’s life; on a two-year-old link it blends cohorts that behaved nothing alike.
• It counts money from everyone who clicked, not only the fans the link acquired — which is why totalSubscribers and acquiredSubscribers are separate fields. Where they diverge, the ratio reads high.
• The earnings object states no currency and no units, unlike the webhook payloads. Fanvue settles creator earnings in USD cents whatever the fan paid in, so USD cents is the reasonable inference — still an inference, so reconcile it against a real payout.

The estimate has a known direction of error: high on links that mostly re-engage existing fans, low on links younger than two billing cycles. It is still far more than cost per click tells you, and it needs no integration.

The one number to measure first

Cost per acquired subscriber, per link. Not return on ad spend, not cost per click, not follower growth. Every other candidate needs either attribution that does not exist yet, or a time series Fanvue does not expose.

Per link rather than per channel, because the channel field is not a campaign field. Reporting granularity is a naming decision made at creation and nothing else, and Fanvue states tracking links are unlimited — so one link per creative rather than one per platform. Two shapes matter, and their names are close enough to lose an afternoon to.

what the API returns for a tracking link
  linkUrl                         "spring-promo"     a bare code
  externalSocialPlatform          "instagram"        one of eight: facebook,
                                                     instagram, other, reddit,
                                                     snapchat, tiktok, twitter,
                                                     youtube
  engagement.acquiredSubscribers  41                 first-click, this link only
  engagement.totalSubscribers     63                 anyone who clicked and is
                                                     subscribed right now
  earnings.totalGross / totalNet                     lifetime, null on a new link

what arrives on the webhook for a payment
  tracking.link_url   "https://fanvue.com/handle?fvc=spring-promo"
                      a full URL, platform-wide last touch, not scoped to you
  tracking.metadata   scoped to you, and the only safe attribution key

no ad id, ad set or campaign field exists on either

The same link is a bare code on the API object and a full destination URL on the webhook, so joining a payment back to a link means parsing a query string and defending against the bare code arriving instead. Three things the number cannot do, stated now rather than discovered later:

• Renewals arrive with tracking null, so a fan’s later spending is detached from the link that brought them unless something on your side stores the first touch and re-applies it to every event that follows.
• First-click means a retargeting link permanently under-reports against the prospecting link that touched the fan first. Correct for a first-click model, and the wrong number to judge retargeting on.
• link_url is platform-wide last-touch and explicitly not scoped to your creator account, so it can carry another creator’s parameter. metadata is scoped to you. Only the second works as an attribution key, and the webhook reference says outright that the two can legitimately disagree.

Two counting traps cost about a week each when met by surprise. facebookexternalhit fetches every advertised URL to build the ad’s preview card, and a server-side redirect logs that fetch as a click, so the redirect log and the pixel disagree — the redirect log being the one lying. And in-app browsers on Snapchat, TikTok and Instagram name the app in their user-agent, so a filter matching bot, crawler or fetcher discards much of the traffic the ads paid for.

Whether to hire an agency

An agency sells one of three things, and the pitch usually blends all three and prices them as one. Labour: posting volume, chat, editing. Capital and risk: ad spend from their accounts, and the ban exposure attached. Distribution: an audience they already have. Which one is being bought decides whether the fee is cheap or absurd.

There is one diagnostic question and it fits in a sentence. Which tracking link is mine, and what are the acquired subscribers and net earnings on it? An operator running traffic properly answers from Fanvue’s own dashboard inside a minute. One who answers with impressions, reach or engagement is selling clicks, and clicks are the metric least connected to income.

Three more before signing anything.

• Who owns the ad account, the pixel and the domain? If the answer is the agency, the campaign history and trained audiences are theirs, and leaving restarts delivery from zero — a switching cost nobody quotes.
• Are my conversions pooled with other creators’? A shared dataset fits one model on audiences with little in common, and puts your revenue inside an asset someone else owns. Attribution across multiple creators covers why the usual defence of signal volume is weak.
• What happens to the tracking links when the contract ends? They cannot be renamed or transferred, only deleted and recreated, and a new one starts at zero clicks with earnings null.

One red flag rather than a question. Fanvue’s marketing policy governs the promotion of Fanvue itself, and binds users who promote it through referral or other programmes. It prohibits unsubstantiated earnings guarantees, manipulated statistics and fabricated endorsements, and requires claims to be accurate and verifiable. An agency recruiting you with a guaranteed monthly figure is marketing Fanvue to a prospective creator while breaching the policy covering exactly that. It does not make them dishonest. It means the number has nothing behind it — a number with something behind it would not need to be a guarantee.

For an AI persona the arithmetic shifts, because creative stops being scarce and evidence per creative becomes the binding constraint, which changes what is worth paying for in paid acquisition for AI creators.

What measurement buys, and what it costs

Everything above can be done with Fanvue’s dashboard and a notebook. What none of it does is reach outwards. An ad platform buys whatever event it is told to buy, as cheaply as it can. Report nothing and it optimises towards clicks, finding people who tap and do not pay — cheap, plentiful, worthless. Two weeks of delivery data describing a population selected for not buying does not unlearn itself when conversion reporting arrives in week three. Fanvue’s numbers stay inside Fanvue, so however accurate they are, they train nothing.

Closing that gap means reporting the conversion from a server, because there is no browser on the page where it happens. Fanvue conversion tracking has the mechanics; the honest summary of the cost:

• Meta’s Conversions API accepts events up to seven days old, and returns an error for the entire request if any single event is older, processing none of them. A day-40 renewal cannot be reported as a fresh acquisition, and a backfill after an outage fails whole rather than in part.
• Fanvue’s webhook gives purchaser email as null, so there is no hashed email to send as a matching key. Matching rests on external_id, fbc, fbp, IP and user-agent — a valid event, and a weaker one than an email-matched event. Value goes in USD, because Fanvue settles in USD cents whatever the fan paid in.
• The join either lands or it does not. When an identifier written into the tracking link at click time comes back on the webhook, the match is deterministic. When it does not, an IP and user-agent match in a short window is what remains — which on mobile traffic behind carrier-grade NAT is not attribution, and belongs in the log as unattributed.

That is the whole of it. Measurement does not make a page convert, write creative, or make an ad account compliant. It changes one thing: the machine spending the money finds out which people paid.

Common questions