Fanvue Snapchat Pixel and Conversions API tracking

Fanvue Snapchat CAPI is a server-side integration built into Fanvue API. It exists so that agencies and creators running Snapchat ads to their Fanvue page can see accurate conversion data even after iOS tracking prevention and ad blockers cut off the browser-only Snap Pixel.

• Server-side Snap Conversions API calls for every subscription, renewal, PPV purchase and tip
• Automatic ScCid capture and 90-day first-party cookie storage on your Fanvue tracking link
• SHA-256 hashed email matching, so raw personal data never reaches Snapchat unhashed
• event_id deduplication shared between the Snap Pixel and the server-side event

A fan clicks your Snapchat ad and lands on a Fanvue tracking link with a ScCid parameter appended by Snapchat. Fanvue API's landing script stores that click ID in a first-party cookie, then attaches it to the fan record the moment they sign up, subscribe or spend. When that event happens, Fanvue API builds a signed request and posts it to Snapchat's Conversions API endpoint on your behalf, using the same event_id that the client-side Snap Pixel used, so Snapchat's deduplication counts it once.

1. Fan clicks a Snapchat ad linking to a Fanvue tracking link carrying ScCid.
2. The landing page stores ScCid in a first-party _scid_fv cookie for 90 days.
3. The fan subscribes, renews, buys a PPV message or tips on Fanvue.
4. Fanvue API hashes the fan's email and builds the Conversions API payload.
5. Fanvue API posts the event to Snapchat with the shared event_id for dedup.

Have these five things ready before you open the Fanvue API dashboard:

• An active Snapchat Ads account with billing enabled
• A Snap Pixel ID from Snapchat Ads Manager, Events Manager
• A Conversions API access token generated for that pixel
• A Fanvue tracking link for the creator you are running ads for
• A Fanvue API key with the ads-tracking scope enabled

Snapchat appends a ScCid parameter to your destination URL. Fanvue API's tracking-link script reads it and stores it in a first-party cookie for 90 days so it survives the gap between the ad click and a later subscription or purchase.

// capture-sccid.ts - run on your Fanvue tracking-link landing page
function captureSnapClickId() {
  const params = new URLSearchParams(window.location.search);
  const scCid = params.get("ScCid");
  if (!scCid) return;

  const ninetyDays = 90 * 24 * 60 * 60 * 1000;
  const expires = new Date(Date.now() + ninetyDays).toUTCString();
  document.cookie = `_scid_fv=${scCid}; expires=${expires}; path=/; SameSite=Lax; Secure`;
}

captureSnapClickId();

Fanvue events map to Snapchat's four core event types as follows.

The same conversion can be sent with a raw cURL call, the Fanvue API TypeScript client or a plain Python request. All three produce the same Snapchat Conversions API event.

curl -X POST "https://tr.snapchat.com/v3/PIXEL_ID/events?access_token=SNAP_CAPI_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "data": [
      {
        "event_name": "SUBSCRIBE",
        "event_time": 1699999999,
        "action_source": "WEB",
        "event_source_url": "https://link.apifanvue.com/c/creator_xyz",
        "event_id": "fanvue_sub_abc123",
        "user_data": {
          "em": ["<sha256(lowercase(trim(email)))>"],
          "client_ip_address": "203.0.113.4",
          "client_user_agent": "Mozilla/5.0 ...",
          "sc_click_id": "<ScCid>"
        },
        "custom_data": {
          "currency": "USD",
          "value": 9.99,
          "content_ids": ["fanvue:creator_xyz"]
        }
      }
    ]
  }'

If you also run the client-side Snap Pixel on your Fanvue page or bio link, both the browser event and the server event carry the same event_id. Snapchat uses this shared ID to recognize the two as one conversion, so ROAS and conversion counts are not inflated. Generate the event_id once per conversion, for example fanvue_sub_abc123, and pass it to both the pixel call and the server-side event in the same request cycle.

Fanvue API only sends hashed personal data to Snapchat. Email addresses are trimmed of whitespace, lowercased, and hashed with SHA-256 before they ever leave Fanvue API's servers. Raw email addresses are never transmitted.

Fields sent with each event: the hashed email (em), the client IP address and user agent for context, and the sc_click_id when a ScCid was captured. Consent is respected end to end: if a fan has not accepted marketing consent under IAB TCF v2.2 or your Consent Mode v2 configuration, Fanvue API withholds the event rather than sending it with degraded identifiers.

Open Events Manager in Snapchat Ads Manager and switch to the pixel's test mode, or request a test_event_code. Send a test event from the Fanvue API dashboard, either through the "Send test event" button on the Snapchat connection page or by including the test code on a real conversion. A good result shows the event listed within Events Manager with status "Received", the correct event name, and the hashed email marked as matched.