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.
Privacy and consent
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:
- A Fanvue app in the Fanvue Developer Portal
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
-
Open the Fanvue Developer Portal and select your app.
-
Go to Pixel Configuration.
-
Select your Tracking Provider (Meta Pixel or GTM).
-
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
-
Toggle Enabled on or off.
-
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:
Acquisition tracking links
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:selfOAuth scope.
Both sources are merged, so a creator appearing in either list is eligible.
Generating links
- Select a creator from the eligible creators dropdown.
- Optionally define a custom slug (2–255 characters, lowercase alphanumeric and hyphens).
- Click Generate to create a tracking link.
- Copy the generated
https://fanvue.com/...URL and use it in your ad campaigns. - Remove links you no longer need with the delete button.
If you do not provide a custom slug, one is generated automatically.
What happens when a user clicks a tracking link
- An impression is recorded in Fanvue.
- If Meta Pixel is configured, the Meta Pixel fires a
PageViewevent. - If GTM is configured, the GTM container script loads and fires its configured tags.
- 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 (
SUCCESSorFAILED) - 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.