This guide explains how to set up Facebook Conversions API for enhanced, server-side tracking.
What is Conversions API?
Facebook Conversions API (CAPI) is a server-side tracking method that sends events directly from your server to Facebook, rather than relying solely on browser-based pixel tracking.
Benefits of CAPI
- Better data accuracy: Not affected by ad blockers or browser restrictions
- More reliable tracking: Works even when cookies are blocked
- Improved attribution: Better connection between ads and conversions
- Future-proof: Works with privacy-first browsing changes
- Enhanced matching: Better customer matching for optimization
Prerequisites
Before setting up CAPI, you need:
- A Facebook Business account
- A Facebook Pixel already configured
- CAPI Access Token from Facebook Events Manager
- Facebook account connected in Pixee app
Getting Your CAPI Access Token
Step 1: Go to Events Manager
- Visit Facebook Events Manager
- Select your pixel from the Data Sources menu
Step 2: Generate Access Token
- Click on Settings tab
- Scroll to “Conversions API” section
- Click Generate access token
- Copy the generated token (it is only shown once)
Important: Keep your access token secure. Do not share it publicly.
Enabling CAPI in Pixee
Step 1: Connect Your Facebook Account
- Go to Settings in the Pixee app
- Under “Login with Facebook”, click Login with Facebook
- Authorize the required permissions
- Your account is now connected
Step 2: Enable CAPI on Your Pixel
- Go to the Dashboard
- Find your Facebook pixel in the list
- Click Edit on the pixel
- Toggle on “Enable Conversions API”
- Enter your Access Token
- Click Save
Step 3: Verify CAPI Status
- Check the pixel list on the Dashboard
- The “CAPI Status” column should show “Enabled”
- Your pixel now sends events via both browser and server
Events Sent via CAPI
When CAPI is enabled, these events are sent server-side:
| Event | Description |
|---|---|
| PageView | All page views |
| ViewContent | Product page views |
| AddToCart | Add to cart actions |
| InitiateCheckout | Checkout starts |
| Purchase | Completed orders |
Deduplication
When using both browser pixel and CAPI, events might be sent twice. Pixee handles deduplication automatically:
- Each event is assigned a unique event ID
- Facebook uses this ID to deduplicate events
- You will only see one event per action in Events Manager
Testing CAPI
Using Events Manager Test Events
- Go to Facebook Events Manager
- Select your pixel
- Click Test events
- Enter your store URL
- Browse your store
- Check both “Browser” and “Server” events appear
Verifying in Events Manager
- Go to Events Manager > Overview
- Look at event breakdown
- You should see events from both “Browser” and “Server”
Plan Requirements
| Feature | Free | Basic | Advanced |
|---|---|---|---|
| Browser Pixel | Yes | Yes | Yes |
| Conversions API | – | Yes | Yes |
Troubleshooting
CAPI Events Not Appearing
- Verify the Access Token is correct
- Check your Facebook account is connected
- Ensure CAPI is enabled on the pixel
- Wait 15-30 minutes for events to appear
- Check Events Manager for any error messages
Access Token Expired
Access tokens can expire. If events stop appearing:
- Go to Facebook Events Manager
- Generate a new access token
- Update the token in your pixel settings
“Invalid Access Token” Error
- Verify you copied the full token
- Check for extra spaces before or after the token
- Generate a new token if needed
Duplicate Events in Events Manager
- Verify Pixee is handling deduplication (check event IDs)
- Check you do not have other apps also sending CAPI events
- Contact support if duplicates persist
Best Practices
- Always use CAPI with browser pixel: Use both for maximum data accuracy
- Secure your token: Never share your access token publicly
- Monitor Events Manager: Check weekly for any issues
- Keep Facebook connected: Maintain your Facebook account connection
Facebook Requirements
Facebook recommends using Conversions API for:
- Better ad optimization
- More accurate conversion measurement
- Compliance with privacy regulations
- Future-proofing against browser changes
Next Steps
- Configure Event Tracking to customize tracked events
- Create Product Feeds for dynamic ads
- Set up Catalog Sync to sync products with Facebook