Conversion Tracking

Fanvue supports conversion tracking so you can send signals from Fanvue flows into your ads reporting and optimization tools. You can choose between Meta Pixel (with Conversions API) or Google Tag Manager (GTM) as your tracking provider.

Supported providers

Meta Pixel + Conversions API (CAPI)

Meta Pixel is a browser-side tracking mechanism tied to your Pixel ID. It helps Meta Ads measure actions that happen after users interact with your campaigns, such as subscriptions, purchases, and registrations.

Meta Conversions API (CAPI) is a server-to-server integration that sends conversion events directly to Meta. It can improve tracking reliability in cases where browser tracking is limited by blockers, privacy settings, or client-side interruptions.

When you select Meta Pixel as your provider, Fanvue uses both Pixel and CAPI together.

Google Tag Manager (GTM)

GTM allows you to route conversion events through your own server-side Google Tag Manager container. This gives you full control over how events are processed and forwarded to downstream analytics or ad platforms.

Fanvue conversion tracking:

  • Uses privacy-preserving processing, with conversion data anonymized or minimized where possible.
  • Respects each user’s cookie consent choice (allow or reject).

Prerequisites

Before configuring conversion tracking in Fanvue, make sure you have:

For Meta Pixel:

  • A Meta Business account with access to Events Manager
  • A Meta Pixel ID (10–20 digits)
  • A Meta Conversions API access token for that pixel

For GTM:

  • A GTM Container ID (format: GTM-XXXXXXX)
  • A server-side GTM endpoint URL
  • A GTM server secret

Configure tracking in Fanvue

  1. Open the Fanvue Developer Portal and select your app.

  2. Go to Pixel Configuration.

  3. Select your Tracking Provider (Meta Pixel or GTM).

  4. Fill in the provider-specific fields:

    Meta Pixel:

    • Enter your Pixel ID
    • Enter your CAPI access token

    GTM:

    • Enter your GTM Container ID
    • Enter your Server Endpoint URL
    • Enter your Server Secret
  5. Toggle Enabled on or off.

  6. Click Save.

If a secret is already configured (CAPI access token or GTM server secret), the field is not shown in plain text. Enter a new value only when you want to replace the current one.

Supported events

Fanvue sends the following event names to your configured tracking provider:

EventWhen it is sent
SubscribeA user subscribes to a creator
PurchaseA user completes a purchase
StartTrialA user starts a trial
CompleteRegistrationA user completes registration through a tracking link

The Pixel Configuration page includes acquisition tracking links so you can attribute creator campaigns to your app’s tracking provider.

Eligible creators

Creators available for link generation come from two sources:

  • Agency-connected creators — creators managed by your agency who have accepted their invite.
  • OAuth-consented creators — creators who have granted your app the read:self OAuth scope.

Both sources are merged, so a creator appearing in either list is eligible.

  1. Select a creator from the eligible creators dropdown.
  2. Optionally define a custom slug (2–255 characters, lowercase alphanumeric and hyphens).
  3. Click Generate to create a tracking link.
  4. Copy the generated https://fanvue.com/... URL and use it in your ad campaigns.
  5. Remove links you no longer need with the delete button.

If you do not provide a custom slug, one is generated automatically.

  1. An impression is recorded in Fanvue.
  2. If Meta Pixel is configured, the Meta Pixel fires a PageView event.
  3. If GTM is configured, the GTM container script loads and fires its configured tags.
  4. The user is redirected to the creator’s profile page.

The impression is stored in a cookie and in local storage so that downstream conversion events (subscriptions, purchases, trials) can be attributed back to the link.

Monitor delivery in the Events tab

Use the Events tab to inspect conversion delivery and troubleshoot tracking:

  • Filter by provider (Meta Pixel or GTM)
  • Filter by event type
  • Filter by status (SUCCESS or FAILED)
  • Filter by creator
  • Filter by start date and end date
  • Sort by event time or event name
  • View the value of each conversion event
  • Load more records with pagination
  • Export filtered results as CSV

This view helps validate that events are being sent and identify failures quickly.

Resources