Skip to main content
If you buy Meta or TikTok traffic for RevShare, you can feed real OnlyFans conversions back into the ad platform and let its smart campaigns optimize on subscribers and revenue instead of clicks. Pixels are managed in the partner cabinet under Tools → Pixels: partners.onlytraffic.com/tools/pixels. This works alongside Callbacks: a campaign can send events to your tracker and to your pixels at the same time.
Pixels attach to Smart Link campaigns. If you drive traffic through regular campaign links, switch to Smart Links first: the click IDs pixels need (fbclid, ttclid) are captured during the Smart Link redirect.

​
How it works

1

Add a pixel

On Tools → Pixels, add your Meta or TikTok pixel: the pixel ID and a Conversions API / Events API access token from the platform’s Events Manager.
2

Attach it to a campaign

On the campaigns page open the campaign’s actions menu (the … button in its row), choose Postbacks and tick the pixel under Ad platforms. One pixel can serve many campaigns.
3

Drive traffic through your Smart Link

Meta and TikTok append fbclid / ttclid to your ad URLs automatically. The redirect captures them along with the visitor’s IP and user agent.
4

Conversions flow back

When an attributed fan subscribes or spends, we send the event server-side to the platform, matched by click ID, hashed fan ID, IP and user agent.

​
Supported platforms and events

Each event can be remapped to another standard platform event or disabled in the pixel form. The Click event is TikTok-only: it gives the campaign learning phase signal volume while conversions are still rare. Purchase value is the fan’s payment. Transaction events carry a USD value equal to what the fan paid (tip, message, post, subscription). On RevShare your commission is a fixed share of that amount, so value-based bidding ranks campaigns the same way it would on your earnings, and CPL tracking-link campaigns (where you are paid per sub, not per transaction) still send a meaningful value.

​
What gets sent

Access tokens are stored encrypted, masked in all logs, and never displayed again after saving.

​
Testing and health

  • Put a Test Event Code from the platform’s test tool into the pixel form to verify delivery end to end, then clear it to go live. Test traffic never reaches ads reporting.
  • Every pixel shows a health badge. Saving the pixel and the Check action send one test event (a PageView on Meta, a custom HealthCheck event on TikTok) marked with a test event code, so it stays out of reporting: Meta uses your code or an internal one, TikTok needs a code from Events Manager and without one the pixel stays “Not checked” until the first live send. The badge is also refreshed by every live send and by a daily background probe of quiet pixels, so an expired token is flagged within minutes. It shows the platform’s own error text; regenerating the access token fixes the most common failures.

​
Monitoring deliveries

The Postback Requests page in your cabinet logs every send, pixel events included: the exact request, the platform’s response, the HTTP status and retry attempts. Failed deliveries carry the platform’s error message in the response body. Delivery rules match callbacks: events leave within about a minute of the conversion and are retried up to 3 times if the request cannot complete.

​
Practical setup for smart campaigns

  • One pixel per ad account; attach it to every Smart Link campaign that receives traffic from that account.
  • Optimize Meta for Subscribe or Purchase, TikTok for Subscribe or CompletePayment.
  • Keep Purchase mapped to New Transaction: those are the events that carry the payment amount as the value.
  • Do not strip query parameters with URL shorteners between the ad and the Smart Link, or the click IDs are lost and match quality drops.