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.

datablow

Datablow Event Tracker connects your WordPress site directly to Meta using the Conversions API (CAPI). It sends events from both the browser and the server side with matching deduplication keys, so your ad campaigns receive complete and accurate conversion data.
Traditional browser-only tracking loses 20–30% of event data due to ad-blockers, iOS privacy protections, and Safari Intelligent Tracking Prevention (ITP). This plugin addresses those challenges by acting as a local proxy on your own domain and writing cookies server-side.
<h4>Core Features</h4>
<ul>
<li>PageView Tracking — Fires PageView events from both the browser pixel and the server side.</li>
<li>Deduplication Engine — Generates matching <code>event_id</code> values for browser and server events so Meta merges them automatically.</li>
<li>Audit Logger — Stores the last 50 Conversions API payloads and HTTP response codes in your admin dashboard.</li>
<li>Test Simulator — Manually trigger test CAPI payloads from WordPress to verify your configuration.</li>
<li>Ad-Blocker Script Proxy — Serves the Meta Pixel JavaScript from your own domain endpoint, preventing ad-blockers from blocking the tracker.</li>
<li>Cookie Keeper — Writes <code>_fbp</code> and <code>_fbc</code> cookies from PHP (server side), extending their lifespan up to 2 years and bypassing Safari ITP limits.</li>
<li>User Registration — Sends <code>CompleteRegistration</code> events when new users register on your site.</li>
<li>URL-to-Event Mapping — Fire any standard Meta event on specific URL paths without writing code.</li>
</ul>
<h3>External Services</h3>
This plugin connects to Meta (Facebook) external services to track web events and transmit conversion data. Specifically:
<ol>
<li>
Meta Pixel JavaScript (connect.facebook.net)
<ul>
<li>The plugin loads the Meta Pixel JavaScript library from <code>https://connect.facebook.net/en_US/fbevents.js</code> in the visitor’s browser to enable browser-side event tracking.</li>
<li>When the Ad-Blocker Script Proxy feature is enabled, this script is fetched server-side and cached locally, then served from your own domain to the visitor’s browser.</li>
<li>What data is sent: No user data is sent to this URL directly; it is a JavaScript file load only.</li>
<li>When: On every front-end page load when a Pixel ID is configured.</li>
</ul>
</li>
<li>
Meta Pixel Noscript Fallback (www.facebook.com/tr)
<ul>
<li>The plugin outputs a 1×1 pixel <code><img></code> tag inside a <code><noscript></code> block requesting <code>https://www.facebook.com/tr</code>.</li>
<li>What data is sent: Pixel ID and a PageView event signal for visitors who have JavaScript disabled.</li>
<li>When: On every front-end page load when a Pixel ID is configured and JavaScript is disabled.</li>
</ul>
</li>
<li>
Meta Graph API / Conversions API (graph.facebook.com)
<ul>
<li>The plugin sends server-side event data to <code>https://graph.facebook.com/v19.0/{pixel_id}/events</code>.</li>
<li>What data is sent: Event name, event time, deduplication event ID, action source, hashed user data (SHA-256 hashed email, phone, name, city, state, zip, country), client IP address, user agent, and Facebook browser/click cookies (<code>_fbp</code>, <code>_fbc</code>). For purchase events, value and currency are also included.</li>
<li>When: On PageView (every front-end page load), custom URL-mapped events, and user registrations — depending on which features are enabled in settings.</li>
<li>Authentication: An Access Token stored in WordPress options is appended to each request.</li>
</ul>
</li>
</ol>
These connections to Meta services are required for the plugin’s core conversion tracking functionality. The processing occurs on Meta’s external servers.
<ul>
<li>Service Provider: Meta Platforms, Inc.</li>
<li>Meta Terms of Service: https://www.facebook.com/legal/terms</li>
<li>Meta Privacy Policy: https://www.facebook.com/about/privacy</li>
<li>Meta Conversions API Terms: https://www.facebook.com/legal/developer_terms</li>
<li>Meta Platform Terms: https://developers.facebook.com/terms/</li>
</ul>
No data is transmitted until you configure a valid Meta Pixel ID and Conversions API Access Token in the plugin settings.

Datablow Event Tracker for Meta Conversions API

First-party Meta Conversions API and browser tracking plugin for WordPress. Bypasses ad-blockers and extends cookie lifetimes.

TrackSharp: Server-Side GA4 Tracking + Attribution Audit for WooCommerce vs Datablow Event Tracker for Meta Conversions API