Fanvue TikTok Pixel and Events API tracking

Fanvue TikTok Events API tracking through Fanvue API sends the events that matter for a Fanvue business - subscriptions, renewals, PPV purchases and tips - straight to TikTok's servers, so your campaigns optimise on real revenue instead of clicks alone.

• Server-side CompletePayment, Subscribe and SubmitForm events sent directly to the Events API on your behalf
• Automatic deduplication against the browser pixel using a shared event_id
• ttclid passthrough and hashed email or phone for accurate attribution and matching
• Custom events for tips, PPV and renewals so TikTok can tell revenue types apart

The pipeline is the same one used across every ad platform Fanvue API supports, specialised for TikTok's identifiers and event names.

1. 01

   Ad click

   ttclid captured

   TikTok appends ttclid to the destination URL when a fan clicks your ad.

2. 02

   Tracking link

   _ttp / ttclid saved

   Your Fanvue tracking link stores ttclid alongside TikTok's _ttp cookie.

3. 03

   Fanvue conversion

   subscribe, tip, PPV

   The fan subscribes, tips or buys a PPV message on Fanvue.

4. 04

   Fanvue API

   hash, dedupe, sign

   Fanvue API hashes the fan's email, attaches event_id and calls the Events API.

5. 05

   TikTok Ads Manager

   CompletePayment, Subscribe

   The event appears in Events Manager and feeds TikTok's optimisation within minutes.

Gather these five things before you open the Fanvue API dashboard:

• A TikTok Ads account with access to Events Manager
• A pixel code from TikTok Events Manager
• An Events API access token generated for that pixel
• A Fanvue tracking link for the creator you are advertising
• A Fanvue API key from your dashboard's API Keys page

TikTok appends ttclid to your ad's destination URL. Fanvue API's tracking-link script reads it on landing and stores it in a first-party cookie for 90 days, alongside TikTok's own _ttp cookie, so the identifier survives even if the fan does not convert on the first visit.

// capture-ttclid.js - run once on the tracking-link landing page
(function () {
  var params = new URLSearchParams(window.location.search);
  var ttclid = params.get("ttclid");
  if (!ttclid) return;

  var expires = new Date(Date.now() + 90 * 24 * 60 * 60 * 1000).toUTCString();
  document.cookie = "fanvue_ttclid=" + ttclid + "; expires=" + expires + "; path=/; SameSite=Lax";
})();

Required and recommended parameters per event, for the TikTok column of Fanvue API's event mapping.

The Fanvue API endpoint below wraps the TikTok Events API call POST https://business-api.tiktok.com/open_api/v1.3/event/track/ so you send one request to Fanvue API and it handles hashing, retries and the Events API call for you.

curl -X POST https://api.apifanvue.com/v1/ads/tiktok/events \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "pixel_code": "C4XXXXXXXXXXXXX",
    "event": "CompletePayment",
    "event_id": "fanvue_sub_abc123",
    "event_source": "web",
    "event_source_id": "C4XXXXXXXXXXXXX",
    "context": {
      "user": { "email": "<sha256(email)>" },
      "ad": { "callback": "<ttclid>" }
    },
    "properties": { "currency": "USD", "value": 9.99, "content_id": "fanvue:creator_xyz" }
  }'

If you also run the browser TikTok Pixel on your Fanvue landing page, TikTok will see two events for the same conversion: one from the pixel, one from the Events API. Fanvue API prevents double counting by generating one event_id per conversion (for example fanvue_sub_abc123) and attaching the same event_id to both calls. TikTok then treats them as a single event for reporting and optimisation, keeping the browser event only for the extra signal it adds.

Fanvue API never sends raw personal data to TikTok. Email addresses and phone numbers are trimmed, lowercased and hashed with SHA-256 before they leave Fanvue API's infrastructure. Only the hashed value plus ttclid is included in the context and user objects.

Consent is respected end to end. If a fan has not granted ad-personalisation consent under IAB TCF v2.2 or Google Consent Mode v2, Fanvue API withholds the event or strips identifying fields depending on the flag, so you stay compliant without extra integration work.

Open the Test Events tool in TikTok Events Manager, copy the test_event_code shown there, and paste it into the Fanvue API dashboard's TikTok connection settings. Trigger a test subscription or fire a manual test event from the dashboard. A good result shows the event listed in Test Events within a few seconds, with CompletePayment or Subscribe, value, currency and a hashed email field all populated, and no warnings about missing parameters.