From Part 1 you need: your Pixel ID and your Conversions API access token. Don’t have them? Go back to Part 1 →
3 steps
1
Verify your domain (DNS TXT)
Use the domain(s) your landing pages & tracking links are served on — not onlyfans.com.
- Business Settings → Brand Safety → Domains → Add → enter your domain.
- Choose the “Add a TXT record” method.
- Copy the
facebook-domain-verificationvalue into your DNS as a TXT record. - Back in Meta, click Verify (DNS can take a few minutes to propagate).
Why: verification proves you own the domain, so Meta credits your link-click conversions and unlocks Aggregated Event Measurement.
2
Allow-list your tracking domains
- Events Manager → your dataset (the pixel from Part 1).
- Open Settings → “Traffic permissions” (the domain allow-list).
- Add each of your tracking domains.
- Save — events from those domains are now accepted.
Why: the allow-list tells Meta which domains may send events to your dataset. Without it, your landing-page & CAPI events can be dropped or left unattributed.
3
Connect the credentials to OnlyFans Pixel
- In your OnlyFans Pixel dashboard, open Settings → New Configuration.
- Access token: keep “New Token” and paste the token from Part 1 — OnlyFans Pixel auto-loads your available pixels & ad accounts.
- Meta Pixel: pick your pixel in the dropdown (or paste the Pixel ID manually).
- Ad account (optional): select it, or paste it as
act_123456789. - Click Save Configuration — it’s validated and linked automatically.
Saving the configuration errors out
Double-check the Pixel ID and access token. A token that can’t write usually means the System User isn’t assigned to the ad account that owns the pixel — see Part 1, step 5.
Next: launch & optimize
Credentials connected and validated? Part 3 walks through the campaign setup — the right objective, the Subscribe → Purchase switch, and how to read the numbers.