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.

Tag Concierge

Handcraft Byte

<p>Tracking eCommerce events via Google Tag Manager and DataLayer makes adding new growth channels a straighforward task. Regardless of a number of connected platforms the data quality and events coverage stays the same.</p>
<p><span class="embed-youtube" style="text-align:center; display: block;"><iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/tTluZ8l94VA?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe></span></p>
<p>This plugin, once activated, starts pushing standard GA4 eCommerce events into GTM DataLayer. Once the data is there you can leverage Google Tag Manager containers to connect virtually any analytics o marketing platform, even if you’re still undecided on your choice.</p>
<p>To speed up the process, our plugin offers pre-packaged integrations for GA4 and Facebook Pixel. You can be up and running in minutes, bypassing the need for time-consuming GTM configuration. See how it works here:</p>
<p>Check <a href="https://demo2-woocommerce.tagconcierge.com/" rel="nofollow ugc">live demo here</a> (perform typical shop activities – add to cart, purchase – to see how events are triggered). This demo showcase all PRO plugin features – FREE version is limited to 2 events listed below.</p>
<p>More information and documentation can be found <a href="https://docs.tagpilot.io/" rel="nofollow ugc">here</a>.</p>
<h3>Example scenarios</h3>
<ol>
<li>Analyse eCommerce behaviors and study your sales funnel in Google Analytics 4</li>
<li>Get most out of Facebook and Instagram paid campaigns with conversion tracking</li>
<li>Optimise your Google Ads campaigns with Enhanced Conversion (requires PRO version)</li>
<li>Expand to new platforms with TikTok, Pinterest and Microsoft UET presets (requires PRO version)</li>
</ol>
<h3>Supported events</h3>
<p>After the plugin is installed it automatically tracks the following events:</p>
<ul>
<li>Add To Cart</li>
<li>Purchase</li>
</ul>
<p>Which are a great base for <strong>conversion measurements</strong> and analysing <strong>sales funnels</strong> related to cart behavior.</p>
<p><strong>For full eCommerce events coverage, improved handling and professional support, <a href="https://tagpilot.io/google-tag-manager-for-woocommerce/?utm_source=wordpress_org" rel="nofollow ugc">buy PRO version</a>. You can also subscribe to our <a href="https://tagpilot.io/care/?utm_source=wordpress_org" rel="nofollow ugc">Tag Pilot Care</a> support service for ongoing assistance, expert guidance, and priority help whenever you need it.</strong></p>
<h3>PRO Version</h3>
<p>The paid version covers following events:</p>
<ul>
<li>view_item_list</li>
<li>select_item</li>
<li>view_item</li>
<li>add_to_cart</li>
<li>view_cart</li>
<li>remove_from_cart</li>
<li>begin_checkout</li>
<li>add_billing_info</li>
<li>add_payment_info</li>
<li>add_shipping_info</li>
<li>purchase</li>
<li>user_data</li>
</ul>
<p>Comes with presets for:</p>
<ul>
<li>Google Ads (Enhanced Conversions)</li>
<li>Google Ads Dynamic Remarketing</li>
<li>Facebook Pixel (Advanced Matching)</li>
<li>Microsoft UET / Bing Ads</li>
<li>Pinterest</li>
<li>TikTok</li>
<li>Consent Mode</li>
<li>Server-side GTM</li>
</ul>
<p>Additonally, works with 3rd party plugins:</p>
<ul>
<li>WooCommerce Brands</li>
<li>Yith Brands</li>
<li>WooCommerce Quick View</li>
<li>WooCommerce Wishlists</li>
<li>WPC Smart Wishlist</li>
<li>WooCommerce Multilingual</li>
<li>WPML</li>
<li>Polylang</li>
</ul>
<h3>Advantage over alternative solutions</h3>
<h3>Only one plugin needed</h3>
<p>Without a GTM plugin, you would need a separate plugin for each of those integrations. Each plugin can track events differently. They can cause conflicts and slow-down on the front-end</p>
<p>With a dedicated GTM plugin, all data is sent in standardized Google format to Google Tag Manager which forwards events to multiple destination services.</p>
<h3>Reporting consistency</h3>
<p>A common problem when trying to use other GTM and Google Analytics plugins is that data can be sent twice corrupting analytics reporting. Using DataLayer is a standard way to ensure your tracking information stays consistent across all connected tools.</p>
<h3>Google Consent Mode v2</h3>
<p>Using GTM and dataLayer allows to build more complex scenarios, such as only processing the data after obtaining user consent. Other plugin directly pipe events into target system no matter if required permission was given or not.</p>


Tag Pilot FREE – Google Tag Manager Integration for WooCommerce

Complete GTM plugin for WooCommerce (Consent Mode v2 and Server-Side). Ready for GA4 and FB Pixel. Product feed for Google Merchant Center.

ClickTrail – UTM, Click ID & Ad Tracking (with Consent) vs Tag Pilot FREE – Google Tag Manager Integration for WooCommerce