Hugo Carvalho

<p>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.</p>
<p>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).</p>
<p>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:</p>
<ul>
<li>WooCommerce orders</li>
<li>supported forms</li>
<li>browser events</li>
<li>optional server-side delivery</li>
</ul>
<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>
<h4>Pick a starting path</h4>
<ul>
<li><strong>WooCommerce store</strong>: enable Capture and WooCommerce. Orders carry campaign context from day one; add storefront events later if you want funnel signals.</li>
<li><strong>Lead-gen forms</strong>: 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><strong>GTM / sGTM stack</strong>: 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><strong>No paid order reports as “direct”</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>No checkout journey goes dark</strong>: 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><strong>No cached or AJAX-rendered form drops attribution</strong>: Hidden fields often break on cached pages or dynamically rendered forms. ClickTrail includes client-side fallback and dynamic-content support.</li>
<li><strong>No cross-domain hop breaks continuity</strong>: Approved link decoration and attribution tokens keep continuity between domains or subdomains.</li>
<li><strong>No consent signal is ignored</strong>: 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><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>Recent additions</h4>
<p>Recent releases extended the Gravity Forms integration with channel classification, merge tags, and per-form controls:</p>
<ul>
<li><strong>Channel classification</strong>: 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><strong>Expanded click ID capture</strong>: 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><strong>Merge tags</strong>: 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><strong>Per-form toggle</strong>: attribution tracking can be enabled or disabled per form via a dedicated ClickTrail section in Gravity Forms form settings.</li>
<li><strong>Admin QA mode</strong>: 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><strong>sessionStorage fallback</strong>: attribution capture now falls back to <code>sessionStorage</code> when the browser blocks cookies.</li>
<li><strong>Minification protection</strong>: 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>
<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.

trackcombo

lucaswhiather

<p><strong>Track Combo — Conversions API for WooCommerce</strong> turns your store into a unified tracking source. One plugin, one tag, and every relevant event reaches Meta (Facebook/Instagram), Google Ads, TikTok, Pinterest, Kwai and any destination you configure in your Track Combo workspace — both from the browser and from the server via the WooCommerce Webhook.</p>
<p>Instead of juggling multiple pixels, conflicting event IDs, and broken deduplication after the iOS 14 / browser tracking updates, Track Combo captures the event once on the storefront, enriches it with first-party data on the server, and fans it out to all destinations with proper <strong>event_id</strong> deduplication between client and server.</p>
<h3>What the plugin does</h3>
<ul>
<li>Injects the Track Combo web tag in the storefront <code><head></code>.</li>
<li>Exposes <code>window.tcWoo</code> with structured product, cart, order, and customer data so events do not depend on DOM scraping.</li>
<li>Registers a native <code>WC_Webhook</code> that sends <code>order.updated</code> to the Track Combo backend when the order reaches the purchase status you choose.</li>
<li>Deduplicates <code>purchase</code> between the client-side <code>complement_data</code> event and the server-side webhook using the order ID as <code>transaction_id</code>.</li>
<li>Declares compatibility with <strong>High-Performance Order Storage (HPOS)</strong> and works with both classic shortcode and <strong>Checkout Blocks</strong> checkouts.</li>
</ul>
<h3>Events sent</h3>
<ul>
<li><code>page_view</code>, <code>search</code>, <code>view_item_list</code>, <code>view_item</code></li>
<li><code>add_to_cart</code>, <code>initiate_checkout</code>, <code>add_shipping_info</code>, <code>add_payment_info</code></li>
<li><code>complement_data</code> (client-side on thank-you page, merged server-side)</li>
<li><code>purchase</code> (server-side via webhook — reliable even when the browser tab is closed)</li>
</ul>
<h3>Why Conversions API</h3>
<p>Tracking quality on WooCommerce stores dropped sharply after iOS 14.5 and the phase-out of third-party cookies. Conversions API (CAPI) is Meta’s, Google’s and TikTok’s answer: send events directly from your server. Track Combo wraps all of them behind one integration.</p>
<h3>Why Track Combo instead of multiple plugins</h3>
<ul>
<li>One plugin instead of one per ad network.</li>
<li>One dedupe boundary handled by Track Combo — no <code>event_id</code> mismatches.</li>
<li>No tag-manager containers to maintain.</li>
<li>Full visibility of every event in the Track Combo dashboard.</li>
</ul>
<p>You need a Track Combo account to use this plugin. Sign up at <a href="https://trackcombo.com/" rel="nofollow ugc">trackcombo.com</a>.</p>
<h3>External services</h3>
<p>This plugin relies on Track Combo (https://trackcombo.com), the service operated by the plugin author, to deliver first-party event tracking and server-side conversion delivery to advertising platforms (Meta Conversions API, Google Ads, TikTok and others). It connects to the following Track Combo endpoints:</p>
<ul>
<li>
<p><strong>Configuration API</strong> — <code>https://server.trackcombo.com/integrationwoocommerce</code>. Called only when the store owner saves the plugin settings in WordPress admin (validate the API key, persist the purchase status filter, register the store domain). Data sent: the API key (HTTP header), and the purchase status or store domain string when those are updated. No customer data is sent through this endpoint.</p>
</li>
<li>
<p><strong>Web tag</strong> — <code>https://track.track-combo.com/tag/{container_id}.js</code> (or your configured first-party CNAME, e.g. <code>https://tracks.yourstore.com/...</code>). Loaded on every storefront page view to enable client-side event tracking. The tag itself dispatches tracking events from the browser to the Track Combo events endpoint.</p>
</li>
<li>
<p><strong>Order webhook</strong> — a WooCommerce webhook registered by the plugin that POSTs the WooCommerce order payload to a URL on <code>server.trackcombo.com</code> whenever an order reaches the purchase status you configure in the plugin settings (default: “Processing”). This enables reliable server-side <code>purchase</code> events even when the customer closes the browser tab.</p>
</li>
</ul>
<p>Track Combo terms of use: https://trackcombo.com/termos-de-uso/<br />
Track Combo privacy policy: https://trackcombo.com/politica-de-privacidade/</p>


Track Combo — Conversions API for WooCommerce

Send WooCommerce events (view, add-to-cart, purchase) to Meta CAPI, Google Ads, and TikTok through Track Combo — no extra pixels needed.

ClickTrail – UTM, Click ID & Ad Tracking (with Consent) vs Track Combo — Conversions API for WooCommerce