capiflow

CapiFlow sends supported WooCommerce events from your server to Meta’s Conversions API (CAPI) — helping reduce the impact of browser-side tracking limitations like ad blockers, Safari ITP, and Firefox ETP.
<h4>Why Server-Side Tracking Matters</h4>
When the Meta pixel is blocked, event data may not reach Meta — affecting ad optimization. CapiFlow complements the browser pixel by sending events server-side with a matching <code>event_id</code> for deduplication.
<h4>How It Works</h4>
<ol>
<li>Install & Activate — Setup wizard launches automatically</li>
<li>Enter Pixel ID + Access Token — From Meta Events Manager</li>
<li>Click Test Connection — Events start flowing</li>
</ol>
No theme edits. No GTM server container required. No separate server-container subscription needed for the built-in Meta CAPI workflow.
<h4>Core Features</h4>
Server-Side Event Tracking
<ul>
<li>🎯 7 Standard Events — Purchase, InitiateCheckout, AddPaymentInfo, AddToCart, ViewContent, Search, PageView</li>
<li>🔄 Deduplication — Browser pixel and server events share the same <code>event_id</code> to support Meta’s deduplication</li>
<li>🛡️ First-Party Event Endpoint — Browser events can be delivered through your own domain where configured</li>
<li>🔐 SHA-256 PII Hashing — Email, phone, name hashed before leaving your server</li>
</ul>
Event Match Quality Support — <code>fbc</code>, <code>fbp</code>, <code>external_id</code>, client IP, user agent, and hashed customer data (email, phone, name) for logged-in users.
Analytics & Monitoring
<ul>
<li>📈 Dashboard — event breakdown and source attribution</li>
<li>🔍 Debug console — payloads and Meta API responses</li>
<li>🏥 System health — token, queue, connection test</li>
<li>🛒 Cart monitor — abandoned cart summary</li>
</ul>
Data Quality & Control
<ul>
<li>📞 Phone validation at checkout</li>
<li>🔒 COD Purchase gate — hold events until admin confirms</li>
<li>📋 Order metabox and columns — per-order CAPI status</li>
</ul>
Developer Tools
<ul>
<li>🔧 Code injection — GTM, analytics, chat widgets (admin-only)</li>
<li>🪝 Filter hooks — <code>capiflow_proxy_url</code>, <code>capiflow_has_tracking_consent</code></li>
<li>📦 HPOS compatible — WooCommerce High-Performance Order Storage support</li>
<li>⏱️ Action Scheduler queue — async event delivery with retry logic</li>
</ul>
<h4>CapiFlow Pro</h4>
CapiFlow Pro is a separate addon that extends the free plugin with:
<ul>
<li>Phone reputation scoring and fraud detection</li>
<li>Negative Purchase events for cancelled/refunded orders</li>
<li>Multi-pixel and category-based pixel routing</li>
<li>COD auto-confirm with courier integration</li>
<li>Real-time EMQ score display from Meta API</li>
<li>Blacklist management for known fraud patterns</li>
<li>Advanced order quality tools</li>
</ul>
Learn more on the <a href="https://capiflowpro.com" rel="nofollow ugc">CapiFlow website</a>.
<h4>Compatibility</h4>
<ul>
<li>Gateways: bKash, Nagad, SSLCommerz, Stripe, PayPal, COD, and all standard WooCommerce gateways</li>
<li>Themes: Any theme — Classic, Block (FSE), page builders</li>
<li>WooCommerce: HPOS and legacy post-based orders</li>
<li>Consent: CookieYes, Complianz, CookieBot, GDPR Cookie Consent, custom filter hook</li>
</ul>
<h4>Requirements</h4>
<ul>
<li>WordPress 6.0+</li>
<li>WooCommerce 7.0+</li>
<li>PHP 7.4+</li>
<li>OpenSSL PHP extension</li>
<li>Meta Pixel ID and System User Access Token</li>
</ul>
<h4>External Services</h4>
This plugin connects to the following third-party services:
Meta (Facebook) Conversions API
CapiFlow sends WooCommerce event data to the Meta Conversions API via: <code>https://graph.facebook.com/</code>
This connection is made from your server to Meta’s servers when a configured tracking event occurs. No data is sent until a valid Pixel ID and Access Token are configured.
Data transmitted includes:
<ul>
<li>Hashed email, phone, first and last name (SHA-256)</li>
<li>Client IP address and Browser User Agent</li>
<li>Meta Click ID (_fbc) and Browser ID (_fbp) cookies</li>
<li>Order total, currency, and event metadata</li>
</ul>
All personal data is SHA-256 hashed before transmission.
<ul>
<li><a href="https://www.facebook.com/terms.php" rel="nofollow ugc">Meta Terms of Service</a></li>
<li><a href="https://www.facebook.com/privacy/policy/" rel="nofollow ugc">Meta Privacy Policy</a></li>
<li><a href="https://developers.facebook.com/terms/" rel="nofollow ugc">Meta Platform Terms</a></li>
</ul>
Meta Pixel JavaScript SDK
This plugin loads the Meta Pixel SDK from: <code>https://connect.facebook.net/en_US/fbevents.js</code>
Loaded on frontend pages when a Pixel ID is configured. The SDK is hosted by Meta.
<ul>
<li><a href="https://www.facebook.com/terms.php" rel="nofollow ugc">Meta Terms of Service</a></li>
<li><a href="https://www.facebook.com/privacy/policy/" rel="nofollow ugc">Meta Privacy Policy</a></li>
</ul>
<h4>Privacy</h4>
For server-side events, all personal data is SHA-256 hashed before transmission. For browser events, the Meta Pixel SDK handles hashing via Advanced Matching. This plugin does not store raw PII in its own tables. See <a href="https://www.facebook.com/privacy/policy/" rel="nofollow ugc">Meta’s privacy policy</a>.
<h4>Cookies</h4>
<ul>
<li><code>cs_uid</code> — Random visitor identifier for <code>external_id</code> deduplication. 180 days. No PII.</li>
<li><code>_fbc</code> — Meta Click ID. Set by Meta SDK on ad click. CapiFlow reads/extends server-side. 180 days.</li>
<li><code>_fbp</code> — Meta Browser ID. Set by Meta SDK. CapiFlow reads/extends server-side. 180 days.</li>
</ul>
All cookies are first-party and contain no personally identifiable information.
<h4>Data Storage</h4>
<ul>
<li><code>{prefix}_capiflow_events</code> — Queued/sent event payloads. Auto-purged after delivery.</li>
<li><code>{prefix}_capiflow_analytics</code> — Daily aggregated analytics. Auto-purged by retention settings.</li>
<li>Order metadata with <code>_capiflow_</code> prefix. Removed on uninstall if “Keep Data” is disabled.</li>
<li>Logs in <code>wp-content/uploads/capiflow-logs/</code> with <code>.htaccess</code> protection. Auto-cleaned daily.</li>
</ul>
<h4>Consent</h4>
By default, events fire once configured. Enable “Consent Enforcement” in Settings to respect CMP signals for both browser and server events.
Supported CMPs: CookieYes, Complianz, CookieBot, GDPR Cookie Consent. Custom integration via <code>capiflow_has_tracking_consent</code> filter.
When Consent Enforcement is enabled, browser and server-side events are blocked until valid tracking consent is detected.
Store owners are responsible for lawful consent configuration where required by privacy regulations.

CapiFlow – Conversions API (CAPI) Tracking for WooCommerce

Send WooCommerce events to Meta Conversions API with server-side tracking, deduplication, and confirmed Purchase control.

pixelflow

Stop losing 30-50% of your WooCommerce conversions to iOS restrictions and ad blockers. <a href="https://pixelflow.so" rel="nofollow ugc">PixelFlow</a> is the no-code solution for implementing Meta’s Conversions API on WooCommerce – so your ads finally get the data they need to optimize.
<ul>
<li>No more missing sales or conversions in Facebook ads manager</li>
<li>See every single event and where it came from down to the campaign, adset and ad</li>
<li>No for developers, Google Tags Manager or expensive solution</li>
</ul>
Why PixelFlow?
Most server-side tracking solutions are built for developers or enterprise teams. They require complex setups, expensive consultants, or per-event pricing that spirals out of control.
PixelFlow is different:
<ul>
<li>No developer needed — install plugin, click enable and you’re DONE.</li>
<li>Unlimited event tracking — flat monthly pricing, no per-event fees or surprise charges</li>
<li>Set up in minutes — not days or weeks</li>
</ul>
What You Get
<ul>
<li>Recover lost conversions that browser-based tracking misses</li>
<li>Improve Event Match Quality scores for better ad targeting and lower CPAs</li>
<li>Track WooCommerce events automatically — Add to Cart, Checkout, Purchase</li>
<li>Real-time event monitoring — see exactly what’s being sent to Meta</li>
<li>Works alongside your existing Pixel — CAPI supplements browser tracking, it doesn’t replace it. PixelFlow automatically loads both your pixel & CAPI for you for perfect event. deduplication and more coverage.</li>
</ul>
Why Server-Side Tracking Matters
Since iOS 14, Meta’s browser-based Pixel misses up to half your conversions. Ad blockers make it worse. When Meta doesn’t receive your conversion data, it can’t optimize your campaigns — so you pay more for worse results. 
PixelFlow sends events directly from your server to Meta, bypassing ad blockers and privacy restrictions entirely. Your ads get complete data. Your ROAS improves.
Built for WooCommerce
When WooCommerce is active, PixelFlow automatically tracks:
<ul>
<li>Add to Cart — with product name, price, and quantity</li>
<li>Initiate Checkout — captures cart totals</li>
<li>Purchase — full order data including revenue</li>
</ul>
No manual setup. No custom code. Works instantly.
Additional options:
<ul>
<li>Exclude free products from tracking</li>
<li>Exclude admins and specific user roles</li>
<li>Control which events fire and when</li>
</ul>
Not Using WooCommerce? We’ve Got You Covered. 
Running a WordPress site without an online store? PixelFlow works for you too without the need for a plugin. Learn more at <a href="https://pixelflow.so" rel="nofollow ugc">PixelFlow</a>
<h3>Privacy Policy</h3>
PixelFlow integrates with Meta’s Conversions API to track customer actions on your website (when configured). This may include:
<ul>
<li>Page views</li>
<li>Product interactions</li>
<li>Purchase events</li>
<li>Form submissions</li>
</ul>
All data is processed according to Meta’s privacy policies and your local privacy regulations. Please ensure you have appropriate user consent mechanisms in place if required by law (e.g., GDPR, CCPA).
For more information: 
* <a href="https://pixelflow.so/privacy" rel="nofollow ugc">PixelFlow Privacy Policy</a> 
* <a href="https://www.facebook.com/business/tools" rel="nofollow ugc">Meta Business Tools</a>
<h3>Additional Information</h3>
Links: 
* <a href="https://pixelflow.so" rel="nofollow ugc">PixelFlow Website</a> 
* <a href="https://docs.pixelflow.so" rel="nofollow ugc">Documentation</a> 
* <a href="https://docs.pixelflow.so/pixelflow-classes-document" rel="nofollow ugc">Event Classes Reference</a> 
* <a href="https://pixelflow.so/contact" rel="nofollow ugc">Support</a>
Requirements: 
* WordPress 5.0 or higher 
* PHP 7.4 or higher 
* WooCommerce 4.0+ (optional, for e-commerce features)
Developer Resources: 
* The plugin is developer-friendly with filters and hooks 
* Custom event tracking can be implemented using PixelFlow classes 
* Compatible with custom WooCommerce themes 
* <a href="https://github.com/PixelFlow-org/pixelflow-wordpress" rel="nofollow ugc">GitHub Repository</a> – feel free to contribute or report issues

PixelFlow

Facebook Conversions API for WooCommerce. One-click setup. Auto track WooCommerce events to Meta with 100% accuracy. Bypass iOS restrictions & ad  …

CapiFlow – Conversions API (CAPI) Tracking for WooCommerce vs PixelFlow