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.

Hugo Carvalho

<p>ClickTrail stores attribution data from landing pages and keeps it available for later form submissions, WooCommerce orders, and event flows.</p>
<p>In WooCommerce, ClickTrail stores attribution on the order, pushes enriched purchase events on the thank-you page, and can optionally emit GA4-style storefront events for <code>view_item</code>, <code>view_item_list</code>, <code>view_cart</code>, <code>add_to_cart</code>, <code>remove_from_cart</code>, and <code>begin_checkout</code>, plus post-purchase milestones, through the same ClickTrail pipeline.</p>
<p>It is designed for cases where attribution often breaks in practice: cached pages, dynamic forms, multi-page journeys, repeat visits, consent requirements, and optional server-side delivery.</p>
<p>The plugin keeps first-touch and last-touch context available until the conversion point and makes that context usable inside WordPress.</p>
<p>It captures first-touch and last-touch source data, keeps it available during the user journey, and makes that data usable where conversions actually happen:</p>
<ul>
<li>WooCommerce orders</li>
<li>supported forms</li>
<li>browser events</li>
<li>optional server-side delivery</li>
</ul>
<p>Teams can start with order or form attribution first, then add browser events, consent handling, or server-side transport when needed.</p>
<h4>What problems it solves</h4>
<ul>
<li><strong>WooCommerce orders losing source data</strong>: Paid traffic often ends up looking like direct traffic by the time an order is placed. ClickTrail stores attribution on the order and keeps purchase reporting tied to campaign context.</li>
<li><strong>Checkout continuity breaking before purchase</strong>: WooCommerce storefront journeys can now emit opt-in <code>view_item</code>, <code>view_item_list</code>, <code>view_cart</code>, <code>add_to_cart</code>, <code>remove_from_cart</code>, and <code>begin_checkout</code> signals through the same ClickTrail event layer used elsewhere in the plugin.</li>
<li><strong>Cached or dynamic forms</strong>: Hidden fields often break on cached pages or AJAX-rendered forms. ClickTrail includes client-side fallback and dynamic-content support.</li>
<li><strong>Cross-domain breaks</strong>: Approved link decoration and attribution tokens help keep continuity between domains or subdomains.</li>
<li><strong>Consent and transport complexity</strong>: Consent controls, browser events, webhook intake, and server-side transport live in the same plugin.</li>
</ul>
<h4>Core capabilities</h4>
<ul>
<li><strong>Capture</strong>: first-touch and last-touch UTMs, major ad click IDs, and referrers with automatic organic/social/referral fallback when UTMs are absent.</li>
<li><strong>WooCommerce</strong>: checkout attribution persistence, thank-you purchase event push, enriched commerce payloads, optional storefront commerce events, and optional order-status milestones.</li>
<li><strong>Forms</strong>: automatic hidden-field enrichment for Contact Form 7 and Fluent Forms, compatible hidden-field population for Gravity Forms and WPForms, client-side fallback, dynamic form support, and WhatsApp attribution continuity.</li>
<li><strong>Events</strong>: browser event collection with <code>dataLayer</code> pushes, canonical REST intake, webhook ingestion, lifecycle updates, one-time WordPress follow-up events such as <code>login</code>, <code>sign_up</code>, and <code>comment_submit</code>, and optional WooCommerce storefront events.</li>
<li><strong>Delivery</strong>: optional server-side transport, retry queue, diagnostics, consent-aware dispatch, and failure telemetry.</li>
</ul>
<h4>What is new in 1.5.2</h4>
<p>This maintenance release focuses on code-quality cleanup and standards compliance without changing runtime behavior:</p>
<ul>
<li><strong>Line-ending cleanup</strong>: normalized mixed line endings in key PHP handlers so packaging and standards checks stay consistent across environments.</li>
<li><strong>Standards cleanup</strong>: resolved PHPCS findings in the consent, attribution-token, and privacy handlers, including targeted documentation for intentional exceptions.</li>
<li><strong>No runtime change</strong>: behavior remains the same as <code>1.5.1</code>; this is a maintenance release focused on code hygiene.</li>
</ul>
<h4>Current admin structure</h4>
<p>The main settings experience is organized by capability:</p>
<ul>
<li>Capture</li>
<li>Forms</li>
<li>Events</li>
<li>Delivery</li>
</ul>
<p>Operational screens stay separate:</p>
<ul>
<li>Logs</li>
<li>Diagnostics</li>
</ul>
<h4>Supported integrations</h4>
<ul>
<li><strong>Forms</strong>: Contact Form 7, Elementor Forms (Pro), Fluent Forms, Gravity Forms, Ninja Forms, WPForms</li>
<li><strong>Commerce</strong>: WooCommerce</li>
<li><strong>CMP sources</strong>: ClickTrail banner, Cookiebot, OneTrust, Complianz, GTM, custom</li>
<li><strong>Webhook providers</strong>: Calendly, HubSpot, Typeform</li>
<li><strong>Server-side adapters</strong>: Generic collector, sGTM, Meta CAPI, Google Ads / GA4, LinkedIn CAPI, Pinterest Conversions API, TikTok Events API</li>
</ul>
<h4>Forms behavior by plugin</h4>
<ul>
<li><strong>Contact Form 7 and Fluent Forms</strong>: ClickTrail can add hidden attribution fields automatically.</li>
<li><strong>Gravity Forms and WPForms</strong>: ClickTrail can populate matching hidden fields you add to the form.</li>
<li><strong>Recommended for Gravity Forms and WPForms</strong>: add the hidden fields you want stored or exported, and ClickTrail will fill them.</li>
<li><strong>Elementor Forms (Pro)</strong>: ClickTrail uses the available submission hooks and attribution fallback, not automatic hidden-field injection.</li>
<li><strong>Ninja Forms</strong>: ClickTrail stores attribution with the submission and surfaces it in the submission record, not as automatic hidden-field injection.</li>
</ul>
<h4>Supported click IDs</h4>
<ul>
<li>Google: <code>gclid</code>, <code>wbraid</code>, <code>gbraid</code></li>
<li>Meta: <code>fbclid</code></li>
<li>TikTok: <code>ttclid</code></li>
<li>Microsoft: <code>msclkid</code></li>
<li>X / Twitter: <code>twclid</code></li>
<li>LinkedIn: <code>li_fat_id</code></li>
<li>Snapchat: <code>sccid</code></li>
<li>Pinterest: <code>epik</code></li>
</ul>
<h4>Additional capture fields</h4>
<ul>
<li>Extended UTMs: <code>utm_id</code>, <code>utm_source_platform</code>, <code>utm_creative_format</code>, <code>utm_marketing_tactic</code></li>
<li>Browser/platform identifiers: <code>fbc</code>, <code>fbp</code>, <code>_ttp</code>, <code>li_gc</code>, <code>ga_client_id</code>, <code>ga_session_id</code></li>
</ul>


ClickTrail – UTM, Click ID & Ad Tracking (with Consent)

Consent-aware attribution for WooCommerce, WordPress forms, and event flows. Capture UTMs and click IDs across conversion paths.

TrackSharp: Server-Side GA4 Tracking + Attribution Audit for WooCommerce vs ClickTrail – UTM, Click ID & Ad Tracking (with Consent)