> ## Documentation Index
> Fetch the complete documentation index at: https://onlytraffic.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Ad Platform Pixels

> Run RevShare Smart Link traffic with Meta and TikTok smart campaigns: server-side conversion events, event mapping, health checks and delivery logs.

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 on the **Ad Platforms** page: [partner.onlytraffic.com/marketer/pixels](https://partner.onlytraffic.com/marketer/pixels).

This works alongside [Callbacks](/partners/revshare-callbacks): a campaign can send events to your tracker and to your pixels at the same time.

<Info>
  Pixels attach to **Smart Link campaigns**. If you drive traffic through regular campaign links, switch to [Smart Links](/partners/revshare-smart-links) first: the click IDs pixels need (`fbclid`, `ttclid`) are captured during the Smart Link redirect.
</Info>

## How it works

<Steps>
  <Step title="Add a pixel">
    On the **Ad Platforms** page, add your Meta or TikTok pixel: the pixel ID and a Conversions API / Events API access token from the platform's Events Manager.
  </Step>

  <Step title="Attach it to a campaign">
    In your Smart Link campaign settings, select the pixel in the **Ad Platforms** field next to the postback editor. One pixel can serve many campaigns.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>
</Steps>

## Supported platforms and events

| Event                | Fires when                                          | Meta default | TikTok default    |
| -------------------- | --------------------------------------------------- | ------------ | ----------------- |
| New Subscriber       | A fan subscribes through your Smart Link            | `Subscribe`  | `Subscribe`       |
| New Transaction      | An attributed fan spends money                      | `Purchase`   | `CompletePayment` |
| Dialog (3+ messages) | An attributed fan exchanges 3 or more chat messages | `Lead`       | `Contact`         |

Each event can be remapped to another standard platform event or disabled in the pixel form.

**Purchase value is your share.** Transaction events carry a USD value equal to your RevShare commission from that transaction, so value-based bidding optimizes for what you actually earn.

## What gets sent

| Field              | Content                                                                |
| ------------------ | ---------------------------------------------------------------------- |
| Click ID           | `fbc` built from the captured `fbclid` (Meta) or raw `ttclid` (TikTok) |
| External ID        | The fan's OnlyFans ID, SHA-256 hashed                                  |
| IP and user agent  | Of the original ad click                                               |
| Landing page URL   | The OnlyFans page the click landed on                                  |
| Event ID           | Deduplication key, safe against retries                                |
| Value and currency | Your commission in USD, on transaction events                          |

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. It is refreshed when you save, by a daily background probe, and by every live send, so an expired token is flagged within minutes. The badge 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 your commission 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.