InitiateCheckout<\/td> value, currency<\/td> num_items, content_ids<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\nIn WordPress stores, we’ve migrated to CAPI, Event Match Quality scores typically jump from “OK” to “Good” or “Great” within 48 hours of enabling Advanced Matching alongside server-side events.<\/p>\n\n\n\n
How Server-Side Tracking Works on WordPress<\/h2>\n\n\n\n Understanding what happens under the hood helps you troubleshoot faster and make better plugin choices.<\/p>\n\n\n\n
When a visitor completes an action on your WooCommerce store – say, finishing a purchase – WordPress fires a set of PHP hooks (like WooCommerce_thankyou<\/strong>). A CAPI-ready plugin listens for these hooks and, when triggered, makes an API call from your server to Meta’s Conversions API endpoint with the event data.<\/p>\n\n\n\nThis server-to-server communication is the core of server-side tracking on WordPress. The visitor’s browser is not involved at all in sending the CAPI event. That’s why ad blockers and cookie restrictions don’t affect it.<\/p>\n\n\n\n
Plugin-based Approach (Pixelavo, PixelYourSite, etc.):<\/h3>\n\n\n\n Easiest for most stores. The plugin handles hook listening, data formatting, token authentication, and API calls. You configure it through the WordPress dashboard \u2014 no server infrastructure to manage.<\/p>\n\n\n\n
GTM Server-side Container Approach:<\/h3>\n\n\n\n For high-volume stores or multi-channel setups (Meta + Google + TikTok + Pinterest all needing server-side tracking), a dedicated Google Tag Manager server container \u2014 typically hosted on Google Cloud \u2014 centralises all server-side events in one place. This is more powerful but requires a developer to set up and maintain, plus hosting costs (~$100+\/month).<\/p>\n\n\n\n
Which approach to choose:<\/p>\n\n\n\n
\nRunning Meta Ads only \u2192 plugin-based is simpler and cheaper.<\/li>\n\n\n\n Running ads across 3+ platforms with high volume \u2192 GTM server-side is worth the investment.<\/li>\n\n\n\n Either way, the tracking accuracy improvement is significant.<\/li>\n<\/ul>\n\n\n\nHow to Avoid Double-Counting with Pixel + CAPI<\/h2>\n\n\n\n Running both browser Pixel and server-side CAPI means the same event (e.g., a Purchase) gets sent twice to Meta \u2014 once from the browser, once from the server. Without deduplication, Meta counts it as two purchases.<\/p>\n\n\n\n
How Deduplication Works:<\/h3>\n\n\n\n Both the Pixel event and the CAPI event must include the same event_id<\/strong>. When Meta receives both, it matches them by event_id<\/strong> and counts the conversion only once. The CAPI event effectively acts as a “backup” for the browser event – if the browser event was blocked, the server event still counts.<\/p>\n\n\n\nHow to Enable It in Practice:<\/h3>\n\n\n\n\nIn Pixelavo, deduplication is handled automatically. The plugin generates matching event_id<\/strong> values for Pixel and CAPI events.<\/li>\n\n\n\nIf using another plugin, check its documentation for event_id<\/strong> or “deduplication” settings and confirm it’s active.<\/li>\n\n\n\nIf you’ve manually implemented CAPI via custom code, you need to generate and pass the same event_id<\/strong> in both your JavaScript Pixel fbq(‘track’, …) <\/strong>call and your server-side API request.<\/li>\n<\/ul>\n\n\n\nBest Practices:<\/h3>\n\n\n\n\nUse only one CAPI plugin at a time. Running Pixelavo and the official Meta plugin simultaneously will cause duplicate server events.<\/li>\n\n\n\n Use the same event names in both Pixel and CAPI (e.g., “Purchase” in both, not “purchase” in one and “Purchase” in the other).<\/li>\n\n\n\n Test each event type individually in Events Manager’s Test Events tool before launching campaigns.<\/li>\n<\/ul>\n\n\n\nVideo Presentation: How to Set Up Facebook Pixel on WordPress Using Pixelavo Plugin<\/h2>\n\n\n\n