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.

Hugo Carvalho

Attribution usually breaks somewhere between the ad click and the conversion. ClickTrail makes it survive: cached pages, dynamic forms, multi-page journeys, repeat visits, and consent requirements.
ClickTrail keeps the source of the visit, not a profile of the visitor. Capture is first-party and consent-aware: the plugin does not call external services to identify or enrich visitors, and data only leaves your site through integrations you enable yourself (GTM, webhooks, server-side delivery).
ClickTrail stores first-touch and last-touch attribution from the landing page and keeps it available until the conversion point, where it becomes usable inside WordPress:
<ul>
<li>WooCommerce orders</li>
<li>supported forms</li>
<li>browser events</li>
<li>optional server-side delivery</li>
</ul>
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.
<h4>Pick a starting path</h4>
<ul>
<li>WooCommerce store: enable Capture and WooCommerce. Orders carry campaign context from day one; add storefront events later if you want funnel signals.</li>
<li>Lead-gen forms: enable Capture and Forms. Contact Form 7 and Fluent Forms get hidden fields automatically; Gravity Forms and WPForms fill the <code>ct_*</code> fields you add.</li>
<li>GTM / sGTM stack: enable Capture, Events, and Delivery. Browser events push to the <code>dataLayer</code>, and the server-side adapters feed sGTM or platform APIs directly.</li>
</ul>
<h4>What problems it solves</h4>
<ul>
<li>No paid order reports as “direct”: 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>No checkout journey goes dark: WooCommerce storefront journeys can 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>No cached or AJAX-rendered form drops attribution: Hidden fields often break on cached pages or dynamically rendered forms. ClickTrail includes client-side fallback and dynamic-content support.</li>
<li>No cross-domain hop breaks continuity: Approved link decoration and attribution tokens keep continuity between domains or subdomains.</li>
<li>No consent signal is ignored: Consent controls, browser events, webhook intake, and server-side transport live in the same plugin and respect the same consent state.</li>
</ul>
<h4>Core capabilities</h4>
<ul>
<li>Capture: first-touch and last-touch UTMs, major ad click IDs, and referrers with automatic organic/social/referral fallback when UTMs are absent.</li>
<li>WooCommerce: checkout attribution persistence, thank-you purchase event push, enriched commerce payloads, optional storefront commerce events, and optional order-status milestones.</li>
<li>Forms: 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>Events: 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>Delivery: optional server-side transport, retry queue, diagnostics, consent-aware dispatch, and failure telemetry.</li>
</ul>
<h4>Recent additions</h4>
Recent releases extended the Gravity Forms integration with channel classification, merge tags, and per-form controls:
<ul>
<li>Channel classification: every GF entry now receives a <code>ct_ft_channel</code> value — a human-readable label such as Google Ads, ChatGPT, or Mailchimp — derived from click IDs, UTM parameters, or referrer context. A server-side fallback covers sessions where JS attribution was unavailable.</li>
<li>Expanded click ID capture: six additional click IDs (Reddit <code>rdt_cid</code>, Pinterest <code>pin_cid</code>, Snapchat <code>snap_cid</code>, Mailchimp <code>mc_cid</code> / <code>mc_eid</code>, and Display & Video 360 <code>dclid</code>) are now captured and stored.</li>
<li>Merge tags: nine <code>{clicutcl_*}</code> merge tags are available in GF notifications and confirmations, including <code>{clicutcl_channel}</code>, <code>{clicutcl_click_id}</code>, and seven UTM-based tags.</li>
<li>Per-form toggle: attribution tracking can be enabled or disabled per form via a dedicated ClickTrail section in Gravity Forms form settings.</li>
<li>Admin QA mode: attribution data is stored in <code>sessionStorage</code> only when a <code>manage_options</code> user is logged in, preventing admin browsing from appearing in attribution reports.</li>
<li>sessionStorage fallback: attribution capture now falls back to <code>sessionStorage</code> when the browser blocks cookies.</li>
<li>Minification protection: ClickTrail script tags carry exclusion attributes recognised by Autoptimize, Cloudflare Rocket Loader, WP Rocket, and LiteSpeed Cache (corrected attribute set in 1.7.0).</li>
</ul>
<h4>Current admin structure</h4>
The main settings experience is organized by capability:
<ul>
<li>Capture</li>
<li>Forms</li>
<li>Events</li>
<li>Delivery</li>
</ul>
Operational screens stay separate:
<ul>
<li>Logs</li>
<li>Diagnostics</li>
</ul>
<h4>Supported integrations</h4>
<ul>
<li>Forms: Contact Form 7, Elementor Forms (Pro), Fluent Forms, Gravity Forms, Ninja Forms, WPForms</li>
<li>Commerce: WooCommerce</li>
<li>CMP sources: ClickTrail banner, Cookiebot, OneTrust, Complianz, GTM, custom</li>
<li>Webhook providers: Calendly, HubSpot, Typeform</li>
<li>Server-side adapters: 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>Contact Form 7 and Fluent Forms: ClickTrail can add hidden attribution fields automatically.</li>
<li>Gravity Forms and WPForms: ClickTrail can populate matching hidden fields you add to the form.</li>
<li>Recommended for Gravity Forms and WPForms: add the hidden fields you want stored or exported, and ClickTrail will fill them.</li>
<li>Elementor Forms (Pro): ClickTrail uses the available submission hooks and attribution fallback, not automatic hidden-field injection.</li>
<li>Ninja Forms: 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.

ServerTrack – Server-Side Tracking & Tagging for WooCommerce vs ClickTrail – UTM, Click ID & Ad Tracking (with Consent)