WooCommerce stores face the same tracking challenges as every other ecommerce platform — ad blockers, iOS privacy restrictions, and browser-based pixel limitations that cause conversions to go unreported. The Conversions API (CAPI) fixes this by sending purchase data directly from your server to Meta, completely bypassing browser-level restrictions.
This guide covers the fastest way to set up Meta CAPI on a WooCommerce store, the key configuration settings that most guides miss, and how to verify your server-side events are arriving correctly and being deduplicated against your browser pixel.
Why WooCommerce Stores Need the Conversions API
A WooCommerce store running only a browser pixel will miss conversions from:
- iOS users who have opted out of tracking — Apple’s ATT framework blocks browser-level pixel tracking for opted-out users, which can represent 40 to 60% of mobile traffic on some stores
- Ad blocker users — browser extensions like uBlock Origin block the Meta pixel script entirely
- Users with strict browser privacy settings — Firefox’s Enhanced Tracking Protection blocks third-party tracking by default
- Network-level blockers — DNS-based ad blockers on home networks and corporate firewalls block pixel requests
For a WooCommerce store doing 100 orders per week, browser-only tracking might be reporting as few as 60 to 75 of those orders to Meta. CAPI fills the gap — it sends purchase data from PHP on your WooCommerce server, where none of these browser-level restrictions apply.
Plugin Options for WooCommerce CAPI
There are three main approaches to setting up CAPI on WooCommerce:
| Option | Cost | Technical Level | Recommended For |
|---|---|---|---|
| Facebook for WooCommerce (official plugin) | Free | Low | Most stores — quickest setup |
| PixelYourSite Pro | Paid (~$99/year) | Low | Stores needing multi-platform pixel management |
| Custom PHP implementation | Developer time | High | Stores with complex order flows or custom data requirements |
For most WooCommerce stores, the official Facebook for WooCommerce plugin is the right starting point. It handles both the browser pixel and CAPI from a single interface, and it automatically manages event_id deduplication between the two.
Setting Up CAPI with the Facebook for WooCommerce Plugin
Step 1: Install and Connect the Plugin
- In your WordPress admin, go to Plugins → Add New and search for “Facebook for WooCommerce”
- Install and activate the plugin
- Go to WooCommerce → Facebook → Settings
- Click Get Started and follow the Facebook login flow to connect your Business Manager account
- Select the correct Business Manager, pixel, and ad account to connect
Step 2: Enable the Conversions API
- Once connected, go to WooCommerce → Facebook → Settings → Advanced
- Find the Conversions API section
- Generate or paste your CAPI Access Token — this is found in Meta Events Manager under your pixel’s Settings → Conversions API
- Enable Send server events
- Save the settings
Step 3: Configure Which Events to Send Server-Side
The plugin lets you choose which events to send via browser pixel, CAPI, or both. For maximum coverage, enable both browser and server for all key events and rely on deduplication to prevent double-counting.
Recommended configuration:
| Event | Browser Pixel | CAPI |
|---|---|---|
| PageView | Yes | Optional |
| ViewContent | Yes | Yes |
| AddToCart | Yes | Yes |
| InitiateCheckout | Yes | Yes |
| Purchase | Yes | Yes — critical |
Step 4: Verify Customer Data Is Being Sent
The biggest determinant of CAPI effectiveness is how much customer data accompanies each server event. The plugin should be configured to send hashed email and phone with every Purchase event — this data is collected at WooCommerce checkout and is legally available server-side.
In the plugin settings, confirm that Advanced Matching is enabled. This instructs the plugin to send hashed customer data (email, name, phone, address) alongside pixel and CAPI events. Without advanced matching, your Event Match Quality will be low and your CAPI events will not attribute effectively.
Verifying CAPI Events in Meta Events Manager
After configuration, go to Meta Events Manager and check your Purchase event’s Overview. Within a few hours of real orders, you should see:
- A non-zero Server column next to your Purchase event
- A non-zero Deduplicated column (confirming browser and server events are being matched)
- The Purchase event’s Match Quality score should be 7 or higher if advanced matching is configured correctly
If the Server column is zero after 24 hours and real purchases have occurred, check:
- That the CAPI access token in the plugin matches the one in Events Manager exactly (no extra spaces)
- That the plugin’s server events are enabled — not just the browser pixel events
- Your server’s PHP error log for any CAPI API call failures
Common WooCommerce CAPI Issues and Fixes
Purchase events arriving twice (no deduplication)
Check that event_id deduplication is enabled in the plugin settings. The official plugin handles this automatically, but custom implementations must pass matching event_ids on both sides. See the deduplication guide for implementation details.
CAPI events not arriving in Events Manager
The most common cause is a server-side PHP error preventing the API call from completing. Enable WooCommerce logging (WooCommerce → Status → Logs) and look for the Facebook for WooCommerce log entries. Failed CAPI calls will appear there with the error message from Meta’s API.
Low Event Match Quality despite CAPI being active
CAPI being active does not guarantee high match quality. The quality depends on what customer data you send. If advanced matching is disabled, CAPI events arrive with minimal customer data and cannot match against Meta profiles effectively. Enable advanced matching and verify the Parameters tab in Events Manager shows email being sent with 100% of Purchase events.
Purchase value is incorrect in CAPI events
If your WooCommerce store uses multi-currency plugins, verify the CAPI plugin is using the order’s actual currency and amount — not the base currency. Some currency conversion plugins create a mismatch between what WooCommerce records as the order total and what the pixel plugin reports.
Run a tracking audit after setup to confirm purchase counts in Events Manager match your WooCommerce order count and that values are accurate.
Related Articles
- Meta Pixel Deduplication: Why It Matters and How It Works
- Shopify Meta Conversions API Setup Guide
- Tracking Explained: How Every Ad Platform Tracks Your Ads
- Free Tracking Audit Checklist: Is Your Setup Working?
📋 Not sure where to start? Use our Free Tracking Audit Checklist to find out where your setup is losing data.
Book a free tracking audit → We’ll review your setup and tell you exactly what to fix.