Freemius

TrackSharp

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

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.

axitrace

AxiTrace for WooCommerce connects your store to the AxiTrace server-side tracking platform at <a href="https://axitrace.com/" rel="nofollow ugc">axitrace.com</a>. Every purchase, add-to-cart, and begin-checkout event is captured on the server and forwarded to your ad platforms — reaching customers that browser-based pixels miss entirely.
Why server-side tracking?
Browser pixels can be blocked by ad blockers, restricted by iOS Intelligent Tracking Prevention, and refused via cookie consent banners. Server-side events travel directly from your WooCommerce server to Facebook CAPI, TikTok Events API, Google Ads, and Google Analytics 4, so conversions are still recorded when the browser pixel cannot fire.
Deduplication so you never double-count
AxiTrace generates a deterministic UUID v5 event ID for every WooCommerce order. The same event ID is attached to both the browser-side purchase pixel fire and the server-side purchase event. Facebook CAPI, TikTok Events API, and Google Ads use that shared event ID to deduplicate automatically — each conversion is counted exactly once, regardless of how many times the confirmation page loads or how many pixels fire.
Server-side AddToCart events
AxiTrace sends AddToCart events server-side, triggered by the WooCommerce <code>woocommerce_add_to_cart</code> hook. This records add-to-cart activity from the server, so the event is captured even when the browser-side pixel is blocked or restricted.
Asynchronous by design — checkout never blocks
All server-side event transmissions are dispatched via WooCommerce Action Scheduler. The HTTP request to AxiTrace’s ingestion API happens in a background job, decoupled from the order placement flow. Checkout latency is unaffected even if the AxiTrace API is momentarily slow or unavailable.
Platform coverage
One plugin. One workspace key. AxiTrace routes your events to whichever ad platforms you connect in your dashboard:
<ul>
<li>Facebook / Meta — Conversions API (CAPI)</li>
<li>TikTok — Events API (server-side)</li>
<li>Google Ads — Offline Conversion Upload (GCLID-based attribution)</li>
<li>Google Analytics 4 — Measurement Protocol</li>
</ul>
HPOS and Cart/Checkout Blocks compatible
AxiTrace for WooCommerce declares compatibility with WooCommerce High-Performance Order Storage (HPOS) and the modern Cart/Checkout Blocks, so it works correctly on stores that have migrated away from legacy shortcode-based checkout.
WP Consent API support
The plugin detects the <a href="https://wordpress.org/plugins/wp-consent-api/" rel="ugc">WP Consent API</a> and checks the visitor’s consent level before firing events. When no consent framework is present, the plugin fires freely (opt-out model). When a framework is present, the plugin respects the consent status for the <code>statistics</code> and <code>marketing</code> categories. This gives your store a ready compliance path without requiring you to build custom integration.
GDPR personal-data tools built in
AxiTrace registers a WordPress personal-data exporter and eraser (<code>wp_privacy_personal_data_exporters</code> / <code>wp_privacy_personal_data_erasers</code>), enabling your store to fulfill GDPR deletion requests directly from the WordPress Tools > Erase Personal Data screen.
Privacy first
Customer email addresses and phone numbers are transmitted in plain text to AxiTrace’s ingestion API at <code>stat.axitrace.com</code> and are SHA-256 hashed inside AxiTrace before being forwarded to any ad platform. No raw PII leaves the AxiTrace platform. See our Privacy Policy at <a href="https://axitrace.com/privacy/" rel="nofollow ugc">axitrace.com/privacy/</a> and the <code>== External Services ==</code> section below for the complete disclosure.
Free plugin. Paid plans for volume.
The plugin itself is free and open source (GPL v2 or later). An AxiTrace account at <a href="https://axitrace.com/" rel="nofollow ugc">axitrace.com</a> is required. Free workspaces are available. Paid plans unlock higher event volumes, longer data retention, and priority support — see <a href="https://axitrace.com/" rel="nofollow ugc">axitrace.com</a> for current pricing.
Requires an AxiTrace account at <a href="https://axitrace.com/" rel="nofollow ugc">https://axitrace.com/</a>.
<h3>External Services</h3>
This plugin connects to stat.axitrace.com — the AxiTrace event-ingestion API.
<ul>
<li>Service: AxiTrace conversion tracking SaaS.</li>
<li>Endpoint: <code>https://stat.axitrace.com/woocommerce/pixel</code> (POST).</li>
<li>When data is sent: on page views (cart, product, checkout, thank-you), add-to-cart events, begin-checkout events, and order placement / payment completion.</li>
<li>Data transmitted: order ID, plain-text billing email (hashed downstream by AxiTrace), billing phone, billing city/country/zip, order total + currency, line items (SKU, name, quantity, price), user agent, IP address, AxiTrace session/user identifiers, click-attribution cookies (fbc, fbp, gclid, ttclid, msclkid, twclid, epik, li_fat_id, sccid, rdt_cid), UTM parameters, page URL/referrer/title.</li>
<li>Why: to forward the conversion to Facebook CAPI, TikTok Events API, Google Ads, GA4, and other ad platforms configured in your AxiTrace workspace.</li>
<li>Terms of Service: https://axitrace.com/terms/</li>
<li>Privacy Policy: https://axitrace.com/privacy/</li>
</ul>
Optional first-party tracking domain
You may optionally configure a custom first-party subdomain under WooCommerce → Settings → Integrations → AxiTrace → “First-party tracking domain”. When set to e.g. <code>metrics.your-store.com</code> (which you set up in your AxiTrace workspace and verify via CNAME to <code>stat.axitrace.com</code>), the SDK and ingestion endpoint load from your own domain instead of stat.axitrace.com. The data transmitted, the endpoint path (<code>/woocommerce/pixel</code>), and the recipient (AxiTrace) remain identical — only the hostname changes. This is purely a delivery optimization that helps bypass client-side blocking; no third-party service is added.
When this field is empty, the plugin uses the default <code>stat.axitrace.com</code> endpoint described above.
Auto-detect lookup endpoint
When the merchant clicks the “Detect from AxiTrace” button on the settings page, the plugin makes a single server-to-server GET request to <code>https://axitrace.com/api/public/workspace/tracking-domain?key={public_key}</code> (AxiTrace admin host — separate from the ingestion host <code>stat.axitrace.com</code>) to look up the default verified domain registered for that workspace. The request contains only the merchant’s own workspace public key (already exposed in every browser event); no customer or visitor data is sent.

AxiTrace for WooCommerce

Server-side conversion tracking for WooCommerce — Facebook CAPI, TikTok Events API, Google Ads, and GA4 from one plugin.

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