Persist and attach first- and last-touch UTMs and click IDs to forms and WooCommerce orders, with consent banner and GA4-ready analytics events.
ClickTrail stores attribution data from landing pages and keeps it available for later form submissions, WooCommerce orders, and event flows.
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 view_item, view_item_list, view_cart, add_to_cart, remove_from_cart, and begin_checkout, plus post-purchase milestones, through the same ClickTrail pipeline.
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.
The plugin 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
Teams can start with order or form attribution first, then add browser events, consent handling, or server-side transport when needed.
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, view_cart, 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.2
This maintenance release focuses on code-quality cleanup and standards compliance without changing runtime behavior:
- Line-ending cleanup: normalized mixed line endings in key PHP handlers so packaging and standards checks stay consistent across environments.
- Standards cleanup: resolved PHPCS findings in the consent, attribution-token, and privacy handlers, including targeted documentation for intentional exceptions.
- No runtime change: behavior remains the same as
1.5.1; this is a maintenance release focused on code hygiene.
Current admin structure
The main settings experience is organized by capability:
- Capture
- Forms
- Events
- Delivery
Operational screens stay separate:
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
Screenshots
WooCommerce order source visibility inside the Woo order list.
WooCommerce order attribution detail for reviewing campaign context on a specific order.
Unified ClickTrail settings organized into Capture, Forms, Events, and Delivery.
Diagnostics and delivery health for verifying event intake and transport behavior.
Where does WooCommerce attribution appear?
ClickTrail stores attribution on the WooCommerce order. The plugin also adds Woo attribution views inside the Woo admin experience where supported, and purchase events carry the same campaign context into the dataLayer and optional server-side delivery.
Does ClickTrail support WooCommerce HPOS?
ClickTrail now declares compatibility with WooCommerce custom order tables (HPOS) and keeps WooCommerce runtime storage on Woo order APIs for order attribution and purchase tracking.
What do the WooCommerce storefront events do?
When you enable WooCommerce storefront events in the Events tab, ClickTrail emits view_item, view_item_list, view_cart, add_to_cart, remove_from_cart, and begin_checkout through the same browser event layer used for other ClickTrail events. They are off by default on upgrades.
What does sGTM mode change?
sGTM mode changes how ClickTrail loads the GTM container and how the Events tab validates a GTM-first rollout. You can configure a tagging-server URL, first-party script delivery, or a custom loader path, then run preview checks before switching Delivery to the sGTM adapter when needed.
Does ClickTrail replace GA4 or GTM?
No. ClickTrail complements them. It preserves attribution inside WordPress, pushes event data to the dataLayer, and can optionally deliver events through its server-side pipeline.
Does it work only with WooCommerce?
No. WooCommerce is one supported conversion surface, but ClickTrail also supports lead forms, external webhook providers, and broader attribution capture for WordPress sites.
What happens if my site uses aggressive caching?
ClickTrail includes a client-side fallback and dynamic-content support so attribution can still reach supported form fields when server-rendered fields are not enough.
Do I need to add hidden fields to every form?
No. Contact Form 7 and Fluent Forms can receive attribution hidden fields automatically. Gravity Forms and WPForms work best when you add the matching ct_* hidden fields you want stored or exported. Elementor Forms (Pro) and Ninja Forms use their submission hooks and stored attribution paths rather than automatic hidden-field injection.
Can I use it without server-side delivery?
Yes. Attribution capture, WooCommerce order attribution, purchase event pushes, and form enrichment all work without enabling server-side delivery.
Is consent mode required?
No. Consent mode is optional. When enabled, ClickTrail can gate attribution and event handling according to the configured consent behavior.
Can I keep using my existing consent platform?
Yes. ClickTrail can listen to its own banner, Cookiebot, OneTrust, Complianz, GTM, or a custom source. You do not need to replace an existing CMP just to use the plugin.
ChangeLog
1.5.2
- Normalized mixed line endings in core PHP handlers to keep standards checks deterministic across environments.
- Resolved the remaining PHPCS findings in the consent, attribution-token, and privacy handlers.
- Kept runtime behavior unchanged from
1.5.1.
1.5.1
- Aligned the public plugin version to
1.5.1 across release surfaces.
- Cleaned up public changelog wording to keep it competitor-neutral and product-focused.
- Kept runtime behavior unchanged from
1.5.0.
1.5.0
- Declared WooCommerce HPOS compatibility during bootstrap and kept Woo order tracking on Woo order APIs.
- Enriched WooCommerce purchase payloads with additive order totals, coupon/status data, richer item detail, and customer/order metadata.
- Added opt-in WooCommerce storefront events for
view_item, view_item_list, view_cart, add_to_cart, remove_from_cart, and begin_checkout, including richer product-list context.
- Added a dedicated sGTM compatibility mode with tagging-server URL support, first-party or custom-loader GTM delivery, and preview checks in the Events tab.
- Added Woo order milestone delivery for
order_paid, order_refunded, and order_cancelled, plus Diagnostics trace lookup for stored payload snapshots.
- Added setup checklist, conflict scan, backup restore, and Woo order trace lookup in the admin surfaces.
- Added Pinterest Conversions API and TikTok Events API as first-class native delivery adapters.
- Added registry-backed QA/docs alignment for the expanded destination and diagnostics surface.
- Included the recent WordPress.org deployment cleanup, Plugin Check fixes, privacy-query hardening, and better debug visibility.
1.3.9
- Made WordPress privacy export and erasure safer by escaping
user_id fragments used inside LIKE-based event matching.
- Improved large-site privacy erasure performance by deleting matched event rows in batches.
- Added lightweight caching for frequently read plugin settings.
- Stopped loading the frontend consent bridge script on pages that do not need attribution capture, consent handling, or browser events.
- Added clearer debug output for invalid attribution-token payloads and for database-level failures during privacy erasure.
1.3.8
- Added a smarter referrer fallback for visits that arrive without UTMs or click IDs.
- ClickTrail now classifies common search, social, and external referral traffic into first-touch and last-touch
source / medium values.
1.3.7
- Introduced dedicated session management with a 30-minute inactivity model and separate session storage.
- Added client-side and server-side session helpers so forms, purchases, and event payloads can include consistent session information.
1.3.6
- Added native Elementor Forms support and completed the Ninja Forms submission-storage path.
- Expanded the capture schema to include newer UTM fields and browser/platform identifiers.
- Split browser event collection from browser event transport and moved frontend attribution onto the shared consent bridge.
1.3.5
- Rebuilt the main settings experience around four capability-based tabs: Capture, Forms, Events, and Delivery.
- Removed user-facing “Tracking v2” language from the main admin flow while keeping backward-compatible internal storage where needed.
Older release notes remain available in changelog.txt.
