Facebook Conversions API (CAPI) - Server-Side Events avatar
Facebook Conversions API (CAPI) - Server-Side Events

Pricing

from $0.01 / 1,000 results

Go to Apify Store
Facebook Conversions API (CAPI) - Server-Side Events

Facebook Conversions API (CAPI) - Server-Side Events

Send offline conversions & server-side events to Meta Conversions API. Track purchases, leads & custom events for Facebook and Instagram ads attribution. Send a single conversion event Send multiple events List all pixels in ad account Get pixel details and stats Validate before sending

Pricing

from $0.01 / 1,000 results

Rating

0.0

(0)

Developer

John Rippy

John Rippy

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Share

Facebook Conversions API

Built by John Rippy | johnrippy.link

๐Ÿ† 2025 Zapier Automation Hero of the Year โ€” Project Phoenix: A 95-step AI sales pipeline cutting development time by 50%. Read more โ†’

Meta CAPI Server-Side Events - Track Purchases, Leads & Custom Conversions

Send offline conversions and server-side events to Meta Conversions API. Track purchases, leads, and custom events with automatic PII hashing for Facebook and Instagram ads attribution.

Features

Event Sending

  • send_event - Send a single conversion event
  • send_batch_events - Send multiple events in one request
  • test_event - Send test event (visible in Events Manager)

Pixel Management

  • list_pixels - List all pixels in ad account
  • get_pixel_info - Get pixel details and stats
  • validate_events - Validate event data before sending
  • get_event_stats - Get event processing statistics

Standard Events

Event NameDescription
PurchaseCompleted transaction
LeadLead form submission
CompleteRegistrationAccount signup
AddToCartItem added to cart
InitiateCheckoutCheckout started
SubscribeSubscription signup
ContactContact form/call
ViewContentPage/product view
SearchSite search

Event Data

User Data (for matching)

All PII is automatically SHA256 hashed:

  • email - Customer email
  • phone - Customer phone (E.164)
  • firstName, lastName - Customer name
  • city, state, zipCode - Address
  • country - ISO country code
  • externalId - Your customer ID

Click IDs (for attribution)

  • fbclid - Facebook click ID from URL
  • fbc - Facebook click cookie
  • fbp - Facebook browser ID cookie

Event Properties

  • value - Conversion value
  • currency - ISO 4217 code
  • orderId - Transaction ID (for deduplication)
  • contentIds - Product IDs
  • eventTime - When conversion occurred

Action Sources

SourceUse Case
websiteWeb conversions
appMobile app events
phone_callCall center sales
chatChat/messaging sales
emailEmail conversions
physical_storeIn-store purchases
system_generatedAutomated events

Example Usage

Single Purchase Event

{
"task": "send_event",
"pixelId": "123456789",
"eventName": "Purchase",
"email": "john@example.com",
"value": 99.99,
"currency": "USD",
"orderId": "ORD-12345",
"actionSource": "physical_store"
}

Batch Events

{
"task": "send_batch_events",
"pixelId": "123456789",
"events": [
{
"eventName": "Purchase",
"email": "john@example.com",
"value": 99.99,
"orderId": "ORD-001"
},
{
"eventName": "Lead",
"email": "jane@example.com",
"phone": "+15551234567"
}
]
}

Event Match Quality

Higher match quality = better attribution. Include:

  1. fbclid/fbc - Best match (click-based)
  2. email + phone - Strong match
  3. email + name + location - Good match
  4. email only - Moderate match

Deduplication

Facebook deduplicates by:

  • event_id - Your unique event identifier
  • orderId + eventName - Transaction-based

Always include orderId to prevent duplicate conversions.

Testing

Use testEventCode from Events Manager to:

  1. Verify events reach Facebook
  2. Check match quality
  3. Debug data issues

Test events appear in Events Manager > Test Events.

Pricing

$0.01 per query (all tasks)

Rate Limits

  • 1,000 events per request (batch)
  • 1,000 requests per hour per pixel
  • Events should be within 7 days