firepixel

<p>FirePixel for WooCommerce connects your WooCommerce store to the <a href="https://firepixel.io" rel="nofollow ugc">FirePixel</a> platform, enabling server-side conversion tracking for Facebook/Meta Ads, TikTok Ads, and Google Ads.</p>
<p><strong>Key Features:</strong></p>
<ul>
<li>Server-side event delivery via FirePixel API — helps reduce signal loss from ad blockers, browser restrictions, and iOS privacy changes</li>
<li>Automatic tracking of key WooCommerce events: AddToCart, RemoveFromCart, ViewCart, ViewContent, InitiateCheckout, Purchase, OrderStatusChanged, and more</li>
<li>Frontend pixel/tag script injection for supported ad platforms when configured</li>
<li>Event deduplication to help prevent double-counting</li>
<li>Background async event queue — no impact on page load time</li>
<li>Debug logging via the WooCommerce logger</li>
<li>Quick Connect flow for easy API key setup</li>
<li>Multi-platform ad tracking support for Meta/Facebook, TikTok, and Google Ads</li>
</ul>
<p><strong>Tracked Events:</strong></p>
<ul>
<li>AddToCart</li>
<li>RemoveFromCart</li>
<li>ViewCart</li>
<li>ViewContent (product pages)</li>
<li>InitiateCheckout</li>
<li>Purchase</li>
<li>OrderStatusChanged</li>
</ul>
<h3>External services</h3>
<p>This plugin connects to external services to deliver server-side conversion tracking and to inject client-side pixel/tag scripts on your storefront. Below is a full disclosure of each service, what data is sent, and when.</p>
<h4>FirePixel API (api.firepixel.io)</h4>
<p>This is the core service this plugin is built around. When the plugin is enabled and a tracked WooCommerce event occurs, such as AddToCart, ViewContent, InitiateCheckout, Purchase, or OrderStatusChanged, it queues an event payload in the database and sends it asynchronously to the FirePixel API in the background via WooCommerce Action Scheduler. WP-Cron is used only if Action Scheduler is not available.</p>
<p>The payload may include the event name, product or order data such as IDs, names, prices, quantities, order totals, currency, and browser signals such as IP address, user agent, referrer, click IDs, cookies, and other attribution parameters used for accurate server-side conversion tracking.</p>
<p>FirePixel may use this data to forward server-side events to the ad platforms configured in your FirePixel dashboard, including Meta/Facebook Ads, TikTok Ads, and Google Ads.</p>
<p>No data is sent unless the plugin is explicitly enabled in settings and valid API credentials are configured.</p>
<ul>
<li>Service provider: FirePixel</li>
<li>Terms of service: https://firepixel.io/terms/</li>
<li>Privacy policy: https://firepixel.io/privacy/</li>
</ul>
<h4>FirePixel App (app.firepixel.io)</h4>
<p>Used only during the Quick Connect setup flow. When a store owner clicks “Quick Connect”, the plugin exchanges an access token with the FirePixel app to retrieve API credentials automatically. The store URL and access token are sent as part of this one-time handshake.</p>
<p>No conversion event data is sent to the FirePixel App during this setup flow, and no setup handshake data is sent after setup is complete.</p>
<ul>
<li>Service provider: FirePixel</li>
<li>Terms of service: https://firepixel.io/terms/</li>
<li>Privacy policy: https://firepixel.io/privacy/</li>
</ul>
<h4>Meta/Facebook Pixel</h4>
<p>If Meta/Facebook Pixel IDs are configured in your FirePixel account, the plugin may inject the Meta Pixel script into frontend pages of your store. This script is loaded in the visitor’s browser and may send browser-side page view and conversion signals to Meta/Facebook.</p>
<p>This only occurs when Meta/Facebook Pixel settings are present in your FirePixel configuration.</p>
<ul>
<li>Service provider: Meta Platforms, Inc.</li>
<li>Terms of service: https://www.facebook.com/legal/terms</li>
<li>Privacy policy: https://www.facebook.com/privacy/policy/</li>
</ul>
<h4>TikTok Pixel</h4>
<p>If TikTok Pixel IDs are configured in your FirePixel account, the plugin may inject the TikTok Pixel script into frontend pages of your store. This script is loaded in the visitor’s browser and may send browser-side page view and conversion signals to TikTok Ads.</p>
<p>This only occurs when TikTok Pixel settings are present in your FirePixel configuration.</p>
<ul>
<li>Service provider: TikTok</li>
<li>Terms of service: https://www.tiktok.com/legal/page/row/terms-of-service/en</li>
<li>Privacy policy: https://www.tiktok.com/legal/page/row/privacy-policy/en</li>
</ul>
<h4>Google Tag Manager / Google Ads (googletagmanager.com)</h4>
<p>If Google Ads or Google Tag IDs are configured in your FirePixel account, the plugin may inject the Google Tag script into frontend pages of your store. This script is loaded directly from Google’s servers in the visitor’s browser and may send page view and conversion data to Google Ads on your behalf.</p>
<p>This only occurs when Google Ads or Google Tag IDs are present in your FirePixel configuration.</p>
<ul>
<li>Service provider: Google LLC</li>
<li>Terms of service: https://policies.google.com/terms</li>
<li>Privacy policy: https://policies.google.com/privacy</li>
</ul>
<h4>Ad platform forwarding</h4>
<p>FirePixel forwards the server-side events it receives to whichever ad platforms you have configured in your FirePixel dashboard, including Meta/Facebook Ads, TikTok Ads, and Google Ads.</p>
<p>The plugin itself sends tracked event data only to FirePixel. FirePixel’s own terms of service and privacy policy govern any onward transmission to third-party ad platforms.</p>
<ul>
<li>FirePixel Terms of service: https://firepixel.io/terms/</li>
<li>FirePixel Privacy policy: https://firepixel.io/privacy/</li>
</ul>


FirePixel for WooCommerce

Server-side WooCommerce conversion tracking for Meta, TikTok, and Google Ads via the FirePixel platform.

capiflow

<p><strong>CapiFlow</strong> 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.</p>
<h4>Why Server-Side Tracking Matters</h4>
<p>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.</p>
<h4>How It Works</h4>
<ol>
<li><strong>Install & Activate</strong> — Setup wizard launches automatically</li>
<li><strong>Enter Pixel ID + Access Token</strong> — From Meta Events Manager</li>
<li><strong>Click Test Connection</strong> — Events start flowing</li>
</ol>
<p>No theme edits. No GTM server container required. No separate server-container subscription needed for the built-in Meta CAPI workflow.</p>
<h4>Core Features</h4>
<p><strong>Server-Side Event Tracking</strong></p>
<ul>
<li>🎯 <strong>7 Standard Events</strong> — Purchase, InitiateCheckout, AddPaymentInfo, AddToCart, ViewContent, Search, PageView</li>
<li>🔄 <strong>Deduplication</strong> — Browser pixel and server events share the same <code>event_id</code> to support Meta’s deduplication</li>
<li>🛡️ <strong>First-Party Event Endpoint</strong> — Browser events can be delivered through your own domain where configured</li>
<li>🔐 <strong>SHA-256 PII Hashing</strong> — Email, phone, name hashed before leaving your server</li>
</ul>
<p><strong>Event Match Quality Support</strong> — <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.</p>
<p><strong>Analytics & Monitoring</strong></p>
<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>
<p><strong>Data Quality & Control</strong></p>
<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>
<p><strong>Developer Tools</strong></p>
<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>
<p>CapiFlow Pro is a separate addon that extends the free plugin with:</p>
<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>
<p>Learn more on the <a href="https://capiflowpro.com" rel="nofollow ugc">CapiFlow website</a>.</p>
<h4>Compatibility</h4>
<ul>
<li><strong>Gateways:</strong> bKash, Nagad, SSLCommerz, Stripe, PayPal, COD, and all standard WooCommerce gateways</li>
<li><strong>Themes:</strong> Any theme — Classic, Block (FSE), page builders</li>
<li><strong>WooCommerce:</strong> HPOS and legacy post-based orders</li>
<li><strong>Consent:</strong> 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>
<p>This plugin connects to the following third-party services:</p>
<p><strong>Meta (Facebook) Conversions API</strong></p>
<p>CapiFlow sends WooCommerce event data to the Meta Conversions API via: <code>https://graph.facebook.com/</code></p>
<p>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.</p>
<p>Data transmitted includes:</p>
<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>
<p>All personal data is SHA-256 hashed before transmission.</p>
<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>
<p><strong>Meta Pixel JavaScript SDK</strong></p>
<p>This plugin loads the Meta Pixel SDK from: <code>https://connect.facebook.net/en_US/fbevents.js</code></p>
<p>Loaded on frontend pages when a Pixel ID is configured. The SDK is hosted by Meta.</p>
<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>
<p>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>.</p>
<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>
<p>All cookies are first-party and contain no personally identifiable information.</p>
<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>
<p>By default, events fire once configured. Enable “Consent Enforcement” in Settings to respect CMP signals for both browser and server events.</p>
<p>Supported CMPs: CookieYes, Complianz, CookieBot, GDPR Cookie Consent. Custom integration via <code>capiflow_has_tracking_consent</code> filter.</p>
<p>When Consent Enforcement is enabled, browser and server-side events are blocked until valid tracking consent is detected.</p>
<p>Store owners are responsible for lawful consent configuration where required by privacy regulations.</p>


CapiFlow – Conversions API (CAPI) Tracking for WooCommerce

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

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