Skip to content

Facebook Pixel Server-Side Sync

Menu Location: Settings > Integrations > Facebook Pixel Server-Side

Access Level: Administrator

Last Updated: 2026-03-01

Overview

The Facebook Pixel Server-Side Sync page manages server-side event tracking for Facebook advertising and analytics. Send conversion events directly from your server to Facebook's Conversions API for more reliable tracking.

Primary Functions:

  • Configure Facebook Conversions API integration
  • Send server-side conversion events to Facebook
  • View event sync logs and status
  • Troubleshoot tracking issues
  • Monitor conversion data quality

Page Layout

Header Section

  • Page title and overview
  • Enable/Disable toggle
  • Configuration status indicator
  • Quick links to Facebook Business Manager

Configuration Panel

  • Facebook Pixel ID field
  • Access Token input
  • Test connection button
  • Save settings button

Event Sync Log

  • Timestamp of each event
  • Event type (PageView, Purchase, AddToCart, etc.)
  • Event status (Success, Failed, Pending)
  • Facebook event ID
  • Error messages (if failed)
  • Customer data sent
  • Conversion value

Summary Statistics

  • Total events sent (today, this week, this month)
  • Success rate percentage
  • Failed events count
  • Last successful sync timestamp

Primary Features

Server-Side Event Tracking

Send conversion events directly from server to Facebook, bypassing browser-based tracking limitations like ad blockers and browser privacy features.

Conversions API Integration

Connect to Facebook's Conversions API to ensure accurate attribution and measurement of advertising campaigns.

Event Monitoring

View real-time logs of all events sent to Facebook including success/failure status and detailed error messages.

Data Quality Insights

Monitor event match quality and conversion data completeness to optimize Facebook advertising performance.

Common Use Cases

Use Case 1: Enable Server-Side Tracking

Goal: Set up Facebook server-side conversion tracking

Steps:

  1. Navigate to Facebook Pixel Server-Side page
  2. Obtain Pixel ID from Facebook Business Manager
  3. Generate Access Token in Facebook Events Manager
  4. Enter Pixel ID and Access Token
  5. Click "Test Connection"
  6. Verify successful connection
  7. Click "Enable" to activate tracking
  8. Monitor first events in log

Use Case 2: Troubleshoot Tracking Issues

Goal: Investigate why events aren't reaching Facebook

Steps:

  1. Review event sync log
  2. Filter by Failed status
  3. Check error messages
  4. Verify Access Token is valid
  5. Check Pixel ID is correct
  6. Test connection
  7. Retry failed events if issue resolved

Use Case 3: Verify Purchase Tracking

Goal: Confirm purchases are being reported to Facebook

Steps:

  1. Process test order
  2. Navigate to event sync log
  3. Filter by event type: Purchase
  4. Verify purchase event appears
  5. Check conversion value is correct
  6. Verify event status is Success
  7. Cross-check with Facebook Events Manager

Use Case 4: Monitor Conversion Quality

Goal: Ensure high-quality conversion data

Steps:

  1. Review success rate in summary stats
  2. Check event match quality scores
  3. Identify events with missing parameters
  4. Review customer data completeness
  5. Make improvements to data collection

Use Case 5: Update Access Token

Goal: Refresh expired access token

Steps:

  1. Generate new Access Token in Facebook
  2. Navigate to configuration panel
  3. Enter new Access Token
  4. Click "Test Connection"
  5. Verify successful connection
  6. Click "Save Settings"
  7. Monitor that events resume sending

Troubleshooting

Events Not Sending to Facebook

Symptoms:

  • No events appearing in log
  • Zero events in summary stats
  • Facebook Events Manager shows no data

Check:

  1. Verify server-side tracking is enabled
  2. Check Pixel ID is correct
  3. Verify Access Token is valid and not expired
  4. Test connection to Facebook API
  5. Review system error logs
  6. Check internet connectivity from server

High Failure Rate

Symptoms:

  • Many failed events in log
  • Success rate below 90%
  • Error messages in event log

Solutions:

  1. Review specific error messages
  2. Check Access Token hasn't expired
  3. Verify Pixel ID is correct
  4. Check Facebook account status
  5. Review data format being sent
  6. Contact Facebook support if persistent

Missing Purchase Data

Symptoms:

  • Purchase events not appearing
  • Conversion values missing
  • Facebook reporting lower revenue than actual

Investigation:

  1. Verify purchase event triggering
  2. Check order completion workflow
  3. Review event data being sent
  4. Test with sample order
  5. Check for order status filtering
  6. Verify integration is enabled for all order types
  • Business Settings - General business and integration settings
  • Payment Transactions - View order and payment data
  • Web Stats - View website analytics
  • Email Stats - Marketing performance metrics

Best Practices

Configuration

  1. Use long-lived Access Tokens (60 days)
  2. Set calendar reminder to refresh token before expiration
  3. Test connection after any configuration changes
  4. Keep backup of Pixel ID and configuration
  5. Document Access Token renewal process

Data Quality

  1. Send all relevant customer data for better matching
  2. Include email, phone, name when available
  3. Send accurate conversion values
  4. Use standard event names (Purchase, AddToCart, etc.)
  5. Monitor event match quality scores in Facebook

Monitoring

  1. Check event sync log daily
  2. Investigate failed events within 24 hours
  3. Maintain 95%+ success rate
  4. Review monthly event volume trends
  5. Compare server-side vs browser-side event counts

Security

  1. Keep Access Token confidential
  2. Use tokens with minimal required permissions
  3. Rotate tokens periodically
  4. Monitor for unauthorized access
  5. Revoke tokens if security concern

Quick Reference Card

Task Action/Location
Enable tracking Toggle Enable switch in header
Enter Pixel ID Configuration panel > Pixel ID field
Add Access Token Configuration panel > Access Token field
Test connection Click "Test Connection" button
View recent events Scroll to Event Sync Log section
Filter failed events Event log > Status filter: Failed
Retry failed event Click Retry button on event row
Check success rate View Summary Statistics section
Update token Replace Access Token, save, test
View event details Click event row to expand

FAQs

What's the difference between browser-based and server-side tracking?

Browser-based tracking (Pixel) runs in customer's browser and can be blocked by ad blockers or privacy features. Server-side tracking sends events directly from your server to Facebook, ensuring more reliable data collection.

How often should I refresh my Access Token?

Access Tokens typically expire after 60 days. Set up a monthly reminder to generate and update your token before expiration to avoid tracking interruptions.

Why do I need both Pixel and server-side tracking?

Using both provides redundancy and improved attribution. Browser Pixel captures some events server-side can't (like PageView behavior), while server-side ensures critical conversions (purchases) are tracked even if Pixel is blocked.

Can I send historical events?

Facebook's Conversions API accepts events from up to 7 days in the past. Older events will be rejected. Use this for backfilling recent data only.

How do I know if my events are matching customers?

Check Event Match Quality scores in Facebook Events Manager (Events Manager > Data Sources > Your Pixel > Overview). Scores above 6.0 are good, above 8.0 are excellent.

What happens if my Access Token expires?

Events will fail to send and accumulate in the failed queue. Refresh your Access Token immediately to resume tracking. Failed events can be retried once the token is updated.

End of Documentation

For additional help, contact your system administrator or Kiva Logic support.