ServerTrack.io

ServerTrack is a powerful Server-Side Tracking solution designed to fix signal loss caused by iOS14, Ad Blockers, and ITP (Intelligent Tracking Prevention). By moving your tracking from the browser to the server, you ensure 99% data accuracy and improve your ROAS.
Why use this plugin?
Most tracking solutions require complex setups involving Google Tag Manager (GTM), DataLayer plugins, and expensive monthly subscriptions.
ServerTrack is different. This plugin handles everything:
<ol>
<li>Generates the DataLayer: It automatically detects WooCommerce events (ViewContent, AddToCart, Checkout, Purchase) and creates the necessary data. You do NOT need “GTM4WP” or any other plugin.</li>
<li>Connects to CAPI: It loads the ServerTrack SDK to send events directly to your server and Facebook Conversion API.</li>
<li>Handles Deduplication: Automatically manages Event IDs to ensure Facebook does not double-count events from your Browser Pixel and Server.</li>
</ol>
Key Features:
<ul>
<li>Zero-Code Setup: Just paste your Auth Key and select “Full Plug-and-Play”.</li>
<li>Custom Domain Support: Use your own subdomain (e.g., <code>track.yourstore.com</code>) to set first-party cookies and bypass ad blockers completely.</li>
<li>Automatic WooCommerce Tracking: Tracks Product Views, Cart Additions, Checkouts, and Purchases out of the box.</li>
<li>Advanced Matching: Automatically captures and hashes customer data (Email, Phone, Name, City) from WooCommerce orders to improve Facebook Match Quality scores.</li>
<li>Custom Events: Fire custom tracking events on any URL pattern you define.</li>
<li>URL Exclusions: Disable tracking on specific pages (e.g., privacy policy, terms).</li>
<li>Configurable AddToCart Triggers: Add custom CSS class, ID, name, href, or data-attribute selectors to detect add-to-cart buttons on any theme.</li>
</ul>

ServerTrack – Server-Side Tracking & Tagging for WooCommerce

Plug & Play Server-Side Tracking for WooCommerce. Auto-generates DataLayer events & connects Facebook CAPI instantly. No GTM required.

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.

ServerTrack – Server-Side Tracking & Tagging for WooCommerce vs CapiFlow – Conversions API (CAPI) Tracking for WooCommerce