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

ClickTrail helps WooCommerce stores and lead-generation sites stop losing campaign context between the landing page and the conversion.

This plugin is sponsored by Funnelsheet.com.

For WooCommerce specifically, ClickTrail keeps attribution attached to the order, pushes enriched purchase events on the thank-you page, and can optionally emit GA4-style storefront events for view_item, view_item_list, add_to_cart, remove_from_cart, and begin_checkout, plus post-purchase milestones, through the same ClickTrail pipeline.

It is built for the parts of attribution that usually break in production: cached pages, dynamic forms, multi-page journeys, repeat visits, consent requirements, and optional server-side delivery.

Instead of only reading the landing-page URL and hoping the data survives, ClickTrail keeps first-touch and last-touch context available until the conversion point and makes that context usable inside WordPress.

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:

• WooCommerce orders
• supported forms
• browser events
• optional server-side delivery

That lets teams start with reliable order or form attribution first, then add browser events, consent handling, or server-side transport later when they actually need them.

What problems it solves

• WooCommerce orders losing source data: 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.
• Checkout continuity breaking before purchase: WooCommerce storefront journeys can now emit opt-in view_item, view_item_list, add_to_cart, remove_from_cart, and begin_checkout signals through the same ClickTrail event layer used elsewhere in the plugin.
• Cached or dynamic forms: Hidden fields often break on cached pages or AJAX-rendered forms. ClickTrail includes client-side fallback and dynamic-content support.
• Cross-domain breaks: Approved link decoration and attribution tokens help keep continuity between domains or subdomains.
• Consent and transport complexity: Consent controls, browser events, webhook intake, and server-side transport live in the same plugin.

Core capabilities

• Capture: first-touch and last-touch UTMs, major ad click IDs, and referrers with automatic organic/social/referral fallback when UTMs are absent.
• WooCommerce: checkout attribution persistence, thank-you purchase event push, enriched commerce payloads, optional storefront commerce events, and optional order-status milestones.
• 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.
• Events: browser event collection with dataLayer pushes, canonical REST intake, webhook ingestion, lifecycle updates, one-time WordPress follow-up events such as login, sign_up, and comment_submit, and optional WooCommerce storefront events.
• Delivery: optional server-side transport, retry queue, diagnostics, consent-aware dispatch, and failure telemetry.

What is new in 1.5.0

This release expands WooCommerce coverage, admin operations, and native delivery breadth without changing the underlying architecture:

• WooCommerce HPOS compatibility declaration: ClickTrail now declares compatibility with WooCommerce custom order tables during bootstrap and keeps order-level attribution logic on Woo APIs.
• Richer purchase payloads: purchase events now include additive commerce fields such as subtotal, tax_total, shipping_total, discount_total, discount_codes, status, order_currency, item_quantity, plus richer item detail such as product_id, sku, variant, and categories.
• Broader WooCommerce coverage: sites can opt in to view_item, view_item_list, add_to_cart, remove_from_cart, and begin_checkout through the existing ClickTrail browser event layer, and server-side delivery can follow post-purchase milestones such as order_paid, order_refunded, and order_cancelled.
• Stronger admin operations: Settings now includes a setup checklist, while Diagnostics now adds conflict scanning, backup restore, and Woo order trace lookup for stored payload snapshots.
• Selective adapter expansion: native delivery support now includes Pinterest Conversions API and TikTok Events API alongside the existing adapters.
• Deployment and privacy hardening: this release also packages the recent WordPress.org deployment cleanup, Plugin Check fixes, privacy-query hardening, and debug visibility improvements.

Current admin structure

The main settings experience is organized by capability:

• Capture
• Forms
• Events
• Delivery

Operational screens stay separate:

• Logs
• Diagnostics

Supported integrations

• Forms: Contact Form 7, Elementor Forms (Pro), Fluent Forms, Gravity Forms, Ninja Forms, WPForms
• Commerce: WooCommerce
• CMP sources: ClickTrail banner, Cookiebot, OneTrust, Complianz, GTM, custom
• Webhook providers: Calendly, HubSpot, Typeform
• Server-side adapters: Generic collector, sGTM, Meta CAPI, Google Ads / GA4, LinkedIn CAPI, Pinterest Conversions API, TikTok Events API

Forms behavior by plugin

• Contact Form 7 and Fluent Forms: ClickTrail can add hidden attribution fields automatically.
• Gravity Forms and WPForms: ClickTrail can populate matching hidden fields you add to the form.
• Recommended for Gravity Forms and WPForms: add the hidden fields you want stored or exported, and ClickTrail will fill them.
• Elementor Forms (Pro): ClickTrail uses the available submission hooks and attribution fallback, not automatic hidden-field injection.
• Ninja Forms: ClickTrail stores attribution with the submission and surfaces it in the submission record, not as automatic hidden-field injection.

Supported click IDs

• Google: gclid, wbraid, gbraid
• Meta: fbclid
• TikTok: ttclid
• Microsoft: msclkid
• X / Twitter: twclid
• LinkedIn: li_fat_id
• Snapchat: sccid
• Pinterest: epik

Additional capture fields

• Extended UTMs: utm_id, utm_source_platform, utm_creative_format, utm_marketing_tactic
• Browser/platform identifiers: fbc, fbp, _ttp, li_gc, ga_client_id, ga_session_id