Meta Conversions API Setup with Server-Side Tracking

Complete playbook for implementing Meta Conversions API using CustomerLabs for iOS 14+ tracking resilience.

C
CustomerLabs
Mar 1, 2024 5 min read

Overview

Set up Meta Conversions API (CAPI) to bypass browser tracking limitations and improve ad performance on Facebook and Instagram.

Prerequisites

  • Facebook Business Manager access
  • Meta Pixel installed on website
  • CustomerLabs account with tracking code deployed
  • Meta Ads Manager access

Step 1: Generate Meta Access Token

  1. Go to Facebook Business Settings
  2. Navigate to System Users
  3. Create a new system user or select existing
  4. Generate access token with ads_management and business_management permissions
  5. Copy and save the access token securely

Step 2: Connect Meta in CustomerLabs

  1. Open CustomerLabs dashboard
  2. Navigate to Destinations → Meta
  3. Select “Conversions API”
  4. Enter your Pixel ID and Access Token
  5. Test connection

Step 3: Configure Event Mapping

Map CustomerLabs events to Meta standard events:

  • Purchase → Meta Purchase
  • Add to Cart → Meta AddToCart
  • View Content → Meta ViewContent
  • Initiate Checkout → Meta InitiateCheckout
  • Lead → Meta Lead

Step 4: Enable Event Deduplication

Configure event deduplication to avoid double-counting:

  1. Enable deduplication in CustomerLabs
  2. Set event_id parameter for both Pixel and CAPI
  3. Set deduplication window (default: 24 hours)

Step 5: Verify Setup in Meta Events Manager

  1. Go to Meta Events Manager
  2. Select your Pixel
  3. Check “Test Events” tab
  4. Trigger test events on your website
  5. Verify both Pixel and Server events appear

Step 6: Monitor Match Quality

  1. Navigate to Events Manager → Data Sources
  2. Select your Pixel
  3. Check “Match Quality” score
  4. Aim for 80%+ match rate

Expected Results

  • 20-40% improvement in conversion tracking
  • Better iOS 14+ tracking resilience
  • Improved ROAS from better attribution
  • Higher audience match rates

Advanced Configuration

Customer Information Parameters

Send additional parameters to improve matching:

  • Email (hashed)
  • Phone (hashed)
  • First name (hashed)
  • Last name (hashed)
  • City, state, country
  • Zip code

Custom Events

Map custom events for specific business needs:

// Example: Subscription event
{
event_name: "Subscribe",
custom_data: {
subscription_type: "premium",
value: 29.99,
currency: "USD"
}
}

Best Practices

  1. Always enable deduplication to prevent double-counting
  2. Send as many customer parameters as possible for better matching
  3. Hash PII data before sending (CustomerLabs does this automatically)
  4. Monitor Event Match Quality score weekly
  5. Test both Pixel and CAPI events regularly

Troubleshooting

Low match quality score

  • Add more customer information parameters
  • Verify data quality (valid emails, phone numbers)
  • Check data hashing is working correctly
  • Ensure consistent data formatting

Events not appearing in Events Manager

  • Verify access token has correct permissions
  • Check Pixel ID is correct
  • Confirm CustomerLabs events are firing
  • Review test events for errors

Duplicate events showing

  • Enable event deduplication
  • Verify event_id is set for both Pixel and CAPI
  • Check deduplication window setting
  • Ensure consistent event naming

Success Metrics

Track these KPIs after implementation:

  • Event Match Quality Score (target: 80%+)
  • Attributed Conversions increase (target: 20%+)
  • ROAS improvement (target: 15-30%)
  • iOS conversion tracking recovery
“Excellent first-party tracking without the gimmicks. We identify more customers than other services and feed that data back into Meta and Google to target users who are actually purchasing.”
Justin G. · Small-Business Owner G2

Join The CustomerLabs Newsletter

Stay ahead with first-party data trends, signal engineering insights, and actionable marketing strategies, curated for modern growth teams.

User
Email