Send Pay Links
Guides

Server-Side Analytics

Track conversions accurately with server-side analytics

Server-Side Analytics

Send Pay Links includes built-in server-side analytics that bypass ad blockers and browser restrictions, giving you accurate conversion data.

Why Server-Side?

Traditional client-side tracking has limitations:

  • Ad blockers - Block tracking pixels
  • iOS 14+ - Limits cross-site tracking
  • Browser privacy - Restricts third-party cookies

Server-side tracking sends data directly from our servers to analytics platforms, ensuring accurate attribution.

Supported Platforms

PlatformEvents Tracked
Facebook CAPIPurchase, InitiateCheckout, AddPaymentInfo
Google Analytics 4purchase, begin_checkout, add_payment_info
TikTok Events APICompletePayment, InitiateCheckout
KlaviyoPlaced Order, Started Checkout
AttentiveOrder Completed, Checkout Started
CustomerLabsAll events

Configuration

All analytics providers are configured through the admin portal. Navigate to Settings > Analytics & Marketing to configure your providers.

All credentials are encrypted and stored securely. Sensitive fields like API keys and access tokens are never displayed after saving.

Facebook Conversions API

  1. In your admin portal, go to Settings > Analytics & Marketing > Facebook CAPI
  2. Enter your credentials:
    • Pixel ID - Your Facebook Pixel ID
    • Access Token - Your Conversions API access token
    • Test Event Code - Optional, for testing in Events Manager

To get your credentials:

  1. Go to Facebook Events Manager
  2. Select your Pixel
  3. Go to Settings > Conversions API to generate an access token

Google Analytics 4

  1. In your admin portal, go to Settings > Analytics & Marketing > Google Analytics 4
  2. Enter your credentials:
    • Measurement ID - Your GA4 measurement ID (starts with G-)
    • API Secret - Your Measurement Protocol API secret

To get your API secret:

  1. Go to your GA4 property
  2. Navigate to Admin > Data Streams
  3. Select your web stream
  4. Go to Measurement Protocol API secrets

Klaviyo

  1. In your admin portal, go to Settings > Analytics & Marketing > Klaviyo
  2. Enter your credentials:
    • Private API Key - Your Klaviyo private key (starts with pk_)
    • Public API Key - Your Klaviyo public/site ID

To get your API keys:

  1. Go to your Klaviyo account
  2. Copy your Private and Public API keys

Attentive

  1. In your admin portal, go to Settings > Analytics & Marketing > Attentive
  2. Enter your credentials:
    • API Key - Your Attentive API key
    • Company ID - Your Attentive company identifier

CustomerLabs

  1. In your admin portal, go to Settings > Analytics & Marketing > CustomerLabs
  2. Enter your credentials:
    • Account ID - Your CustomerLabs account ID
    • API Token - Your CustomerLabs API token

Event Mapping

Events from Send Pay Links are automatically mapped to platform-specific events:

Checkout EventFacebookGA4TikTok
checkout.initializedInitiateCheckoutbegin_checkoutInitiateCheckout
payment.succeededPurchasepurchaseCompletePayment
upsell.acceptedPurchasepurchaseCompletePayment

User Data Hashing

For privacy compliance, PII (personally identifiable information) is automatically hashed before sending:

  • Email addresses → SHA256
  • Phone numbers → SHA256 (E.164 format)
  • Names → SHA256 (lowercase, trimmed)

This ensures compliance with platform requirements and privacy regulations.

Testing Your Integration

To verify your analytics are working:

  1. Facebook: Use the Test Event Code field and check Events Manager > Test Events
  2. Google Analytics: Use GA4 DebugView in real-time reporting
  3. Klaviyo: Check your Klaviyo activity feed for incoming events

Server-side events may take up to 24 hours to appear in platform dashboards due to processing delays.

Troubleshooting

Events Not Appearing

If events aren't showing up in your analytics platform:

  1. Verify your credentials are correct in the admin portal
  2. Check that the provider shows as "Configured" with a green indicator
  3. Ensure your platform account is active and properly set up
  4. Wait up to 24 hours for events to process

Duplicate Events

If you're seeing duplicate events, you may have both client-side and server-side tracking enabled. Consider disabling client-side tracking for events that are being sent server-side.

On this page