Facebook Conversions API (CAPI) Integration
Last updated: September 17, 2026
The Facebook Conversions API (CAPI) sends conversion data directly from your server to Facebook — bypassing browser limitations like ad blockers and iOS restrictions.
Before you begin
- Facebook Business account with access to the advertiser's Pixel / Dataset
- Advertiser provides: Facebook Pixel ID (Dataset ID) and System User Access Token
Where to find it
Integrations > Facebook
Setup steps
- Click Add Configuration
- Fill in:
| Field | What to enter |
|---|---|
| Business Name | Advertiser's brand name |
| Affiliate | Which affiliate's traffic this config applies to |
| Mapped Offers | TrackOG offers whose conversions to send to Facebook |
| Dataset ID / Pixel ID | From Facebook Events Manager |
| Access Token | System User Access Token from Facebook Business Manager |
- Save
TrackOG now sends conversion events to Facebook for every tracked conversion on the mapped offers.
CAPI vs Facebook Pixel
| Facebook Pixel | CAPI | |
|---|---|---|
| Blocked by ad blockers | ✅ Yes | ❌ No |
| Blocked by iOS (ITP) | ✅ Yes | ❌ No |
| Requires browser | ✅ Yes | ❌ No — server to server |
Facebook recommends using both Pixel + CAPI together for maximum accuracy.
Frequently Asked Questions
Q: The access token is expiring. How do I update it? A: Edit the configuration and paste the new token. Use System User tokens (long-lived) to minimise expiry issues.
Q: Do I need the Pixel too, or just CAPI? A: Use both for best results — Pixel handles browser events, CAPI handles server-side.
Related articles
- Integrations Overview
- Conversion Tracking Methods