Meta Ads tracking

Meta Ads tracking tells you which ad click brought each new OnlyFans subscriber. It then reports that subscriber, and what they pay, to your own Meta pixel and to your own systems. The tracking service runs at trk.theonlyapi.com and is set up from the Meta Ads page of your Xcelerator CRM. Your Only API does two jobs in the chain: it creates the OnlyFans tracking links, and it sends the webhook that says a fan subscribed or paid.

How it works

 ┌──────────┐   ┌─────────┐   ┌───────────────┐   ┌───────────┐
 │ Ad click │ → │ Consent │ → │ Tracking link │ → │ Subscribe │
 └──────────┘   └─────────┘   └───────────────┘   └─────┬─────┘
  landing page   landing page   made via Only API    OnlyFans
                                                         │
 ┌───────────────────────────┐   ┌───────┐   ┌─────────┐ │
 │ Postback  +  Meta pixel   │ ← │ Match │ ← │ Webhook │ ←┘
 └───────────────────────────┘   └───────┘   └─────────┘
  your systems + your pixel     trk service   Only API → trk.theonlyapi.com

Who does what

What the Only API side needs

Open Meta Ads Tracking in the Only API dashboard. Its setup list checks each of these for you.

1. The creator is connected and syncing. Events only exist for accounts the Only API syncs. Fansly can't be used: it doesn't say who joined through a link.
2. Write actions are on for that creator. Creating a tracking link is a write on OnlyFans, so it needs the per-account switch (PATCH …/accounts/{of_user_id}/polling {"allow_of_write_actions": true}). Without it, link creation stops with ONLYAPI_WRITES_DISABLED in the CRM.
3. The tracking connection is approved. The tracking service registers the webhook itself when you press Connect Only API in your CRM (Meta Ads → Settings → Only API); you never create it by hand. The creators sent with it are your CRM's active creators; press Update creators there after adding or removing one. Webhooks to a new domain wait for approval (Webhooks → Approval), so until trk.theonlyapi.com is on the built-in list the connection shows Waiting for approval and delivers nothing.
4. All four events are subscribed. new_subscriber, renewed_subscriber, new_purchase and new_tip. Reconnecting from the CRM restores a missing one.

The tracking service always answers our webhook with a 2xx, even for events it ignores (another creator, a test). Any 4xx would count toward the 5-failure auto-disable, which would switch tracking off for the whole panel.

Check it over the API

Two read-only endpoints back the dashboard page. They read stored data only: no OnlyFans request, nothing counted against your monthly quota.

Status

curl "$BASE/api/crm/$CRM/meta-tracking/status" -H "X-API-Key: $KEY"

{
  "success": true,
  "tracking_domain": "trk.theonlyapi.com",
  "required_event_types": ["new_purchase", "new_subscriber", "new_tip", "renewed_subscriber"],
  "domain": { "allowlisted": false, "approved_for_panel": true, "state": "approved_for_panel" },
  "webhooks": [
    {
      "id": 41,
      "url": "https://trk.theonlyapi.com/webhooks/onlyapi/t_8f2c",
      "status": "approved",
      "is_active": true,
      "consecutive_failures": 0,
      "auto_disable_after": 5,
      "missing_event_types": [],
      "health": "healthy",
      "deliveries": {
        "last_24h": { "delivered": 37, "retrying": 0, "retried": 1, "failed": 0 },
        "last_7d": { "delivered": 212, "retrying": 0, "retried": 3, "failed": 0 },
        "last_success_at": "2026-10-13T09:41:07.512000",
        "last_failure": { "at": "2026-10-13T02:10:44.100000", "result": "retried", "response_code": 503,
                          "reason": "The receiver had an error (HTTP 503). We retry automatically." },
        "next_retry_at": null
      }
    }
  ],
  "creators": [
    { "of_user_id": "482687148", "username": "examplecreator", "platform": "onlyfans",
      "supports_tracking_links": true, "write_actions": true, "polling_enabled": true,
      "last_polled_at": "2026-10-13T09:40:12", "events_7d": { "new_subscriber": 41, "new_purchase": 9,
      "new_tip": 3, "renewed_subscriber": 12 } }
  ],
  "summary": { "connected": true, "delivering": true, "all_events_subscribed": true,
               "creators": 1, "creators_with_write_actions": 1 }
}

Times are UTC, written without a zone suffix, like the rest of the API. The signing secret is not included; GET /webhooks/{id} returns it to the key holder as before.

Delivery log

curl "$BASE/api/crm/$CRM/meta-tracking/deliveries?limit=50&result=failed" -H "X-API-Key: $KEY"

{
  "success": true,
  "deliveries": [
    {
      "id": 90211, "webhook_id": 41, "at": "2026-10-13T09:41:07.512000",
      "attempt": 1, "max_attempts": 6, "result": "delivered", "response_code": 200,
      "reason": null, "reply_excerpt": null, "next_retry_at": null,
      "event": { "id": 5512093, "type": "new_purchase", "occurred_at": "2026-10-13T09:40:58",
                 "creator": { "of_user_id": "482687148", "username": "examplecreator" },
                 "fan": "Fan #a1b2c3", "value": 25.0, "test": false }
    }
  ],
  "has_more": true,
  "next_before": 90211
}

Each row is one attempt. A failed attempt is retried after 5 s, 30 s, 5 min, 30 min and 2 h (6 attempts in all); reason says what went wrong in plain words. A row with "event": {"type": "test"} came from POST /webhooks/{id}/test.

Privacy

• Fans are anonymous tags. The dashboard page and the delivery log show a fan only as Fan #a1b2c3: stable for one fan on your panel, different on every other panel, and not reversible without our server secret. No fan id, username, display name or message text is returned.
• Meta receives only what it needs. The event name and time, its value for purchases, and the consented click's details from your landing page (fbc, fbp, IP address and browser, a hashed click id). Never a fan's OnlyFans id, username or name, and only for subscribers matched to an exact click.
• Nothing before consent. The landing page records nothing until the visitor accepts the notice.

Troubleshooting

Related

• Webhooks: approval, signatures, the retry ladder and auto-disable.
• Events: what triggers new_subscriber, new_purchase and the rest.
• Subscribers & fans: how new subscribers are detected.