Fanvue Google Ads conversion tracking

Fanvue Google Ads conversion tracking is a server-side integration in Fanvue API. It closes the gap between a Google Ads click and revenue that happens later on Fanvue.com, days or weeks after the click, by uploading conversions directly to Google's servers instead of relying on browser-only tags.

• gclid, gbraid and wbraid capture on every Fanvue tracking link, stored for 90 days
• Offline conversion import via the Google Ads API for subscriptions, renewals, PPV and tips
• Enhanced conversions for web using SHA-256 hashed email for better match rates
• Optional GA4 Measurement Protocol events and Consent Mode v2 support

A fan clicks a Google Ads search, display or video ad that lands on a Fanvue tracking link. Google appends a click identifier, gclid for standard clicks, gbraid for app-to-web clicks on iOS, or wbraid for privacy-sandbox web clicks. Fanvue API's landing script stores whichever identifier is present in a first-party cookie. When the fan later converts on Fanvue, Fanvue API builds a conversion record and uploads it to Google Ads using the Google Ads API's ConversionUploadService.UploadClickConversions call.

1. Fan clicks a Google Ads ad linking to a Fanvue tracking link.
2. The landing page stores gclid, gbraid or wbraid in a first-party 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 conversion upload.
5. Fanvue API uploads the conversion to the matching conversion action in Google Ads.

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

• A Google Ads account with conversion tracking enabled
• A conversion action created for each Fanvue event you want to track (subscribe, purchase)
• API access with a developer token and OAuth credentials for that Google Ads account
• A Fanvue tracking link for the creator you are running ads for
• A Fanvue API key with the ads-tracking scope enabled

Google Ads can append gclid, gbraid or wbraid depending on the click's device and consent context. Fanvue API's tracking-link script reads whichever one is present and stores it in a first-party cookie for 90 days, matching the maximum age Google Ads accepts for offline conversion uploads.

// capture-gclid.ts - run on your Fanvue tracking-link landing page
function captureGoogleClickIds() {
  const params = new URLSearchParams(window.location.search);
  const ids = { gclid: params.get("gclid"), gbraid: params.get("gbraid"), wbraid: params.get("wbraid") };
  const ninetyDays = 90 * 24 * 60 * 60 * 1000;
  const expires = new Date(Date.now() + ninetyDays).toUTCString();

  for (const [key, value] of Object.entries(ids)) {
    if (!value) continue;
    document.cookie = `_${key}_fv=${value}; expires=${expires}; path=/; SameSite=Lax; Secure`;
  }
}

captureGoogleClickIds();

Fanvue events map to Google Ads conversion actions and GA4 events as follows.

The same offline conversion upload can be sent with a raw cURL call to the Google Ads API, the Fanvue API TypeScript client, or a plain Python request. All three produce the same conversion record. A fourth snippet shows the optional GA4 Measurement Protocol call.

curl -X POST "https://googleads.googleapis.com/v17/customers/CUSTOMER_ID:uploadClickConversions" \
  -H "Authorization: Bearer OAUTH_ACCESS_TOKEN" \
  -H "developer-token: DEVELOPER_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "conversions": [
      {
        "gclid": "<gclid>",
        "conversionAction": "customers/CUSTOMER_ID/conversionActions/CONVERSION_ACTION_ID",
        "conversionDateTime": "2025-03-01 14:32:11+00:00",
        "conversionValue": 9.99,
        "currencyCode": "USD",
        "orderId": "fanvue_sub_abc123",
        "userIdentifiers": [
          { "hashedEmail": "<sha256(lowercase(trim(email)))>" }
        ]
      }
    ],
    "partialFailure": true
  }'

Google Ads deduplicates conversions by order_id rather than a shared event_id. Fanvue API sets order_id to a stable identifier for each conversion, for example fanvue_sub_abc123, so retried uploads or a combination of enhanced conversions and offline conversion import never double count the same subscription or purchase.

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

Consent Mode v2 signals, ad_user_data and ad_personalization, are read from your consent banner and passed with every conversion. If a fan has not granted ad_user_data consent, Fanvue API withholds the enhanced conversion fields and relies on modeled conversions instead, matching how Google Ads expects consent-aware traffic to behave.

Open the Diagnostics tab on the conversion action in Google Ads to see upload health, recent conversions and any partial failures. Send a test event from the Fanvue API dashboard and confirm it appears in Diagnostics within a few hours, since offline conversion imports are not always instant. A good result shows the conversion listed with status "Recorded" and the correct value and currency.