Server-Side Tracking

What Is Server-Side Tracking?

Server-side tracking sends conversion data directly from your server to ad platforms via their Conversion APIs, bypassing the browser entirely. Unlike client-side tracking (which loads Tracking Tags in the browser), server-side tracking uses server-to-server communication that ad blockers cannot see or block.

When a conversion happens, your server sends event data directly to platforms like Facebook Ads or Google Ads via their Conversion APIs without loading a browser pixel. For a detailed comparison of how Meta's three tracking layers work together (Pixel, Conversion API, and Conversion API for CRM), see Meta Pixel vs CAPI vs CAPI for CRM.

📘

Note

Server-side tracking is available on all AnyTrack plans. AnyTrack handles data transformation, hashing, and API management automatically when you connect an ad platform.

Why Server-Side Tracking Matters

Ad blockers, iOS App Tracking Transparency, and cookie limitations break traditional pixel tracking. Server-side tracking solves three critical problems:

1. Accuracy: Servers communicate reliably. Failed requests retry automatically with error logging.
2. Ad blocker immunity: Browser extensions cannot block server-to-server communication.
3. Data quality: Hash personal information, normalize formats, and enrich conversion data before sending.

Industry estimates suggest that without server-side tracking, 20-30% of conversions are lost to ad blockers and browser restrictions. Ad platforms receive incomplete data, degrading campaign optimization.

How Client-Side Tracking Works

Traditional pixel tracking loads in the browser when users reach your thank-you page.

Example: Facebook Pixel on checkout page

When a customer completes a purchase, the thank-you page executes:

fbq('track', 'Purchase', {
  value: 40.00,
  currency: 'USD'
});

Flow:

1. Customer completes purchase
2. Thank-you page loads in browser
3. Facebook Pixel code executes
4. Pixel sends Purchase event to Facebook
5. Facebook Event Manager records the conversion
6. Facebook Ads updates campaign ROAS

Problem: Ad blockers, iOS App Tracking Transparency, and cookie limitations block 20-30% of pixel requests. Facebook never sees the conversion, so campaigns optimize on incomplete data.

How Server-Side Tracking Works

Server-side tracking sends conversion data from your server to ad platforms via Conversion APIs, with no browser pixel required.

Flow:

1. Customer completes purchase
2. Your server records the transaction
3. Server transforms data to match the Conversion API format
4. Server hashes personal data (email, phone, name)
5. Server maps internal field names to platform standard names
6. Server sends a POST request to the Conversion API

Example: Facebook Conversion API payload

{
  "data": [
    {
      "event_name": "Purchase",
      "event_time": 1661941807,
      "action_source": "website",
      "event_id": "123123123123123123",
      "event_source_url": "https://example.com",
      "user_data": {
        "em": ["7b17fb0bd173f625b58636fb796407c22b3d16fc78302d79f0fd30c2fc2fc068"],
        "ph": ["72fe84274df481a1ad439dbd462c76f6304a99a8e009e583924ff04f9c17cc01"],
        "external_id": ["932f3c1b56257ce8539ac269d7aab42550dacf8818d075f0bdf1990562aae3ef"]
      },
      "custom_data": {
        "currency": "USD",
        "value": "142.52"
      }
    }
  ]
}

The user_data fields are hashed (SHA-256). Meta uses these identifiers to match conversions to user profiles and improve Event Match Quality.

Matching Conversions Across Systems

Ad platforms need identifiers to connect server-side conversions to users who clicked your ads.

Send multiple identifiers to maximize match rates. Meta uses these to calculate Event Match Quality. Higher match quality improves targeting and optimization.

Server-Side Tracking: Advantages and Challenges

Advantages

Reliability: Server-to-server communication does not fail silently. Failed requests trigger retries and error notifications.

Ad blocker immunity: Browser extensions cannot see or block server-to-server API calls.

Privacy control: Process and anonymize data before sending to ad platforms. You decide what data to share.

Data enrichment: Combine conversion data with CRM records, customer lifetime value, and product catalogs before sending.

Cross-device tracking: Use customer IDs and hashed email to track users across devices without cookie dependency.

Challenges

Development required: Backend work is needed to transform data to the Conversion API format, hash personal information, and handle authentication.

Identifier dependency: Without email, phone, or Meta cookies, match rates decline.

API maintenance: Monitor for deprecation notices and update integrations when platforms release new versions.

Infrastructure: Server-side tracking requires capacity to handle API requests, retries, and error logging.

Data quality risk: Malformed data or wrong event parameters can degrade campaign performance. Test before deploying to live campaigns.

Why Use AnyTrack for Server-Side Tracking

AnyTrack eliminates backend development. Install the AnyTrack Tracking Tag once and enable server-side tracking via a toggle.

What AnyTrack automates:

• Data transformation: Converts conversions to match each platform's Conversion API format (Meta, Google Ads, TikTok, etc.)
• Identifier collection: Captures browser cookies (fbp, fbc, gclid) and first-party data (email, phone)
• Hashing and normalization: Automatically hashes personal data to maximize Event Match Quality
• API management: Handles authentication, retries, error logging, and version updates
• Multi-platform delivery: Send conversions to all connected platforms simultaneously

Examples:

• Shopify: Automatic purchase tracking via Conversion API
• Affiliate networks: Server-side tracking via postback URL
• Custom checkouts: Webhooks send conversions directly to AnyTrack

AnyTrack connects your website, backend systems, and ad platform APIs, handling all orchestration so you focus on optimization.

Server-Side Tracking Best Practices

Start with Hybrid Tracking

Send conversions from both browser and server. Use the event_id parameter to deduplicate conversions across sources. This maximizes coverage during platform transitions.

Maximize Event Match Quality

Send all matching identifiers: hashed email, hashed phone, fbp, fbc, IP address, and user agent. Higher match quality improves targeting and attribution.

Monitor Data Quality

Set up alerts for failed API requests, low Event Match Quality scores, and conversion discrepancies between your logs and platform reporting.

Keep APIs Current

Subscribe to platform changelog notifications (Meta, Google Ads, etc.). Update integrations when platforms deprecate endpoints or release new features.

Test Before Launch

Validate server-side tracking with test conversions. Compare server-side counts to internal transaction logs to verify accuracy before enabling live campaigns.

Getting Started with Server-Side Tracking

Step 1: Assess Your Tracking Needs

Identify which platforms you advertise on and which conversion events to track. Common events: Purchase, Lead, AddToCart, CompleteRegistration.

Step 2: Choose Your Implementation Method

Option 1: Manual backend integration. Build custom integration with each platform's Conversion API. Full control, highest complexity.

Option 2: AnyTrack. No-code setup with automatic data transformation. Connect your ad platform in the Integration Catalog and server-side tracking starts working.

Option 3: Server-side Google Tag Manager. Intermediate complexity. Requires server container setup.

Step 3: Collect Identifiers

Capture browser cookies (fbp, fbc, gclid) and first-party data (email, phone) throughout the customer journey. Store these so your server includes them in Conversion API requests.

Step 4: Test Implementation

Send test conversions and verify they appear in platform Event Manager tools. Check Event Match Quality scores and fix any identifier issues.

Step 5: Enable Deduplication

Use the event_id parameter to deduplicate browser and server conversions. Same event_id means same conversion.

Step 6: Monitor and Optimize

Track Event Match Quality scores, API error rates, and conversion completeness. Optimize by adding more identifiers and fixing data quality issues.