Freemius

TrackSharp

<p><strong>Improve purchase conversion tracking accuracy for WooCommerce with native server-side tracking.</strong></p>
<p>Browser-based tracking is blocked by modern privacy settings (ITP), ad blockers, and consent choices. This leads to missing purchase conversions in GA4 and incomplete ad reporting.</p>
<p><strong>TrackSharp</strong> adds a reliable, first-party server-side tracking layer. It ensures your most important event — <strong>Purchase</strong> — is recorded in GA4 even when browser tags fail.</p>
<p>No GTM server container. No Google Cloud costs. No complex coding.</p>
<blockquote>
<p>“We previously used Google Tag Manager, but browser blocking still caused us to miss up to 40% of our conversions. With TrackSharp, our data is finally 100% accurate without us needing to change a thing.”</p>
<p><strong>Jordi</strong> — Online Marketer at Hbeds.nl</p>
</blockquote>
<h4>What Problem We Solve</h4>
<p>Most store owners don’t know <em>how much</em> data they are losing. Setting up server-side tracking usually requires complex Google Tag Manager (GTM) containers, monthly cloud hosting fees (Stape/Google Cloud), and developer time.</p>
<p><strong>TrackSharp removes that complexity and cost.</strong><br />
It runs directly on your WordPress server as a native plugin. You can complete the setup in 5 minutes and immediately start auditing your data loss and fixing GA4 tracking.</p>
<h4>Features & Capabilities</h4>
<p><strong>1. Instant Attribution Audit (Free)</strong><br />
Unique to TrackSharp: we don’t just track, we <em>diagnose</em>. The dashboard uses your real historical order data to highlight risks:<br />
* <strong>Google Ads Blind Spots:</strong> See how many orders have Google Click IDs (gclid) that browser tracking might have missed.<br />
* <strong>Meta Pixel Health:</strong> Monitor if your browser Pixel is firing correctly or being blocked.</p>
<p><strong>2. Reliable GA4 Server-Side Tracking</strong><br />
Sends purchase events via the Measurement Protocol directly from your server. This bypasses ad blockers and iOS restrictions to close the gap between WooCommerce orders and Analytics reports.</p>
<p><strong>3. Native WooCommerce Integration</strong><br />
Unlike generic GTM solutions, TrackSharp is purpose-built for WooCommerce. It listens to internal order hooks to ensure data accuracy.</p>
<h4>Supported WooCommerce Events</h4>
<p>TrackSharp tracks the complete shopping journey server-side (GA4) to ensure full funnel visibility:</p>
<ul>
<li><strong>Shopper Activity:</strong> <code>view_item</code> (product view), <code>add_to_cart</code>, <code>view_cart</code></li>
<li><strong>Checkout Flow:</strong> <code>begin_checkout</code>, <code>add_payment_info</code></li>
<li><strong>Conversion:</strong> <code>purchase</code> (Order Completed)</li>
</ul>
<p><em>Note: Non-purchase events are sent via the first-party collector endpoint included in the free version.</em></p>
<h4>Best Fit For Which Stores?</h4>
<ul>
<li><strong>Stores running Paid Ads:</strong> If you spend budget on Google Ads or Meta (Facebook/Instagram) and suspect your ROAS is inaccurate due to tracking loss.</li>
<li><strong>Cost-Conscious Owners:</strong> Stores that want reliable Server-Side tracking without paying €20-€100/month for external hosting (like Stape or Google Cloud).</li>
<li><strong>Agencies & Freelancers:</strong> Professionals looking for a “set-and-forget” solution for clients that doesn’t require maintaining complex GTM server containers.</li>
<li><strong>Non-Technical Founders:</strong> Anyone who wants to fix their data accuracy in 5 minutes without writing code or hiring a developer.</li>
</ul>
<h4>Pro Version: Advanced Attribution</h4>
<p>For stores running paid ads on Google or Meta, TrackSharp Pro adds the missing attribution layer:</p>
<ul>
<li><strong>Google Ads Attribution:</strong> Captures attribution parameters server-side so conversions are credited to the right campaign.</li>
<li><strong>Meta Conversions API (CAPI):</strong> Full server-side backup for the Facebook Pixel.</li>
<li><strong>Enhanced Conversions:</strong> Sends hashed user data (email/phone) to improve match rates on both platforms.</li>
<li><strong>Priority Support:</strong> Direct access to the developers via email.</li>
</ul>
<h3>How It Works</h3>
<ol>
<li><strong>Install:</strong> Activate the plugin on your WordPress site.</li>
<li><strong>Connect:</strong> Use the Setup Wizard to link your GA4 Measurement ID.</li>
<li><strong>Audit:</strong> Check the Dashboard to see your “Revenue Audit” and potential data loss.</li>
<li><strong>Relax:</strong> TrackSharp now runs in the background, securing your data.</li>
</ol>
<h3>Third Party Services</h3>
<h4>Google Analytics 4 (Measurement Protocol)</h4>
<p>TrackSharp sends server-side events to Google Analytics 4 when configured.<br />
* Service: https://www.google-analytics.com<br />
* Terms: https://policies.google.com/terms<br />
* Privacy Policy: https://policies.google.com/privacy</p>
<h4>Meta (Facebook) Conversions API (Pro only)</h4>
<p>When using TrackSharp Pro, purchase events can be sent to Meta via the Conversions API.<br />
* Service: https://graph.facebook.com<br />
* Terms: https://www.facebook.com/terms.php<br />
* Privacy Policy: https://www.facebook.com/privacy/policy</p>
<h4>Freemius</h4>
<p>TrackSharp uses Freemius for optional upgrades, licensing, and updates.<br />
* Service: https://freemius.com<br />
* Terms: https://freemius.com/terms/<br />
* Privacy Policy: https://freemius.com/privacy/</p>


TrackSharp: Server-Side GA4 Tracking + Attribution Audit for WooCommerce

Secure server-side GA4 tracking for WooCommerce + a built-in Audit Dashboard to detect Google Ads & Meta attribution risks.

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.

TrackSharp: Server-Side GA4 Tracking + Attribution Audit for WooCommerce vs CapiFlow – Conversions API (CAPI) Tracking for WooCommerce