ClickTrail – UTM, Click ID & Ad Tracking (with Consent) -- WordPress 插件

开发者	hugoc
更新时间	2026年5月12日 05:04
PHP版本:	8.1 及以上
WordPress版本:	6.9
版权:	GPLv2 or later
版权网址:	版权信息

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.6.0 This release extends the Gravity Forms integration with channel classification, merge tags, and per-form controls:

Channel classification: every GF entry now receives a ct_ft_channel 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.
Expanded click ID capture: six additional click IDs (Reddit rdt_cid, Pinterest pin_cid, Snapchat snap_cid, Mailchimp mc_cid / mc_eid, and Display & Video 360 dclid) are now captured and stored.
Merge tags: nine {clicutcl_*} merge tags are available in GF notifications and confirmations, including {clicutcl_channel}, {clicutcl_click_id}, and seven UTM-based tags.
Per-form toggle: attribution tracking can be enabled or disabled per form via a dedicated ClickTrail section in Gravity Forms form settings.
Admin QA mode: attribution data is stored in sessionStorage only when a manage_options user is logged in, preventing admin browsing from appearing in attribution reports.
sessionStorage fallback: attribution capture now falls back to sessionStorage when the browser blocks cookies.
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).

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

安装:

Before you configure anything ClickTrail can be rolled out in layers. A basic attribution setup for forms or WooCommerce does not require server-side delivery on day one.

If you only want attribution inside WooCommerce or forms, you can leave server-side delivery disabled.
If your site already loads Google Tag Manager, do not add the GTM container ID again in ClickTrail.
If you use Gravity Forms or WPForms, add the ct_* hidden fields you want stored or exported before testing.
If your site has consent requirements, decide whether ClickTrail or your existing CMP should be the consent source.

Recommended first setup

Install the plugin through WordPress or upload it to /wp-content/plugins/click-trail-handler/.
Activate the plugin.
Open ClickTrail > Settings.
In Capture:
keep attribution enabled
choose a retention window that matches your sales cycle
enable cross-domain continuity only if visitors move between approved domains or subdomains
In Forms:
enable only the integrations you actually use
for Contact Form 7 and Fluent Forms, ClickTrail can add attribution hidden fields automatically
for Gravity Forms and WPForms, add the matching ct_* hidden fields you want to preserve, such as ct_ft_source, ct_lt_source, or ct_gclid
In Events:
leave browser events enabled only if you want dataLayer pushes and on-site event capture
enable WooCommerce storefront events only if you want view_item, view_item_list, view_cart, add_to_cart, remove_from_cart, and begin_checkout in the browser event layer
enable the richer Woo dataLayer contract only if you want event_id and consent-aware user_data for GTM-first flows
add a GTM container ID only if your site does not already inject GTM somewhere else
switch GTM to sGTM compatibility mode when you want a tagging-server URL, first-party script delivery, or a custom loader path, then run the preview checks before rollout
In Delivery:
leave server-side delivery off if you do not have a collector, sGTM, or advertising endpoint yet
if you do use server-side delivery, configure the adapter, endpoint, and timeout here
if consent is required, choose the correct consent source and mode before going live
Open ClickTrail > Diagnostics and run the relevant checks, especially Endpoint Test, Conflict Scan, and Woo Order Trace Lookup when applicable.

How to verify your setup

Visit your site with a test URL such as ?utm_source=test&utm_medium=cpc&utm_campaign=clicktrail-install-check.
Browse to another page, then place a test WooCommerce order or submit a supported form.
Confirm the expected result:
the WooCommerce order or form entry contains attribution values
Woo purchase events appear in your GTM preview or dataLayer
if Woo storefront events are enabled, view_item, view_item_list, view_cart, add_to_cart, remove_from_cart, and begin_checkout appear in GTM preview or the dataLayer
if sGTM mode is enabled, the Events-tab preview checks reach the configured loader or collector URLs
Diagnostics and Logs show intake or delivery activity if Delivery is enabled

Good default rollout Start with Capture plus the forms or WooCommerce integrations you already use. Add Events next if you want browser analytics signals. Add Delivery only when you are ready to send data to a collector or advertising endpoint.

屏幕截图:

常见问题:

更新日志:

1.7.2

NitroPack compatibility: ClickTrail now detects NitroPack and automatically attempts to exclude its scripts from NitroPack's "Postpone JS" feature via two mechanisms: the nitropack_js_url_exclude filter and the data-nitropack-exclude HTML attribute on script tags. Without this, postponed scripts can cause empty UTM data on leads when users navigate away before interacting with the page.
NitroPack diagnostic warning: The Diagnostics conflict scan now surfaces a warn finding when NitroPack is active, with instructions to verify script exclusions in NitroPack → Optimization → JavaScript → Script exclusions.
pt-BR playbook — webhook middleware pattern: Expanded the Padrão 5 section in the Portuguese Implementation Playbook to document the three-layer webhook architecture (script → webhook middleware → CRM), the complete field reference for Google Ads and Meta Ads attribution, PipeRun-specific notes on custom field IDs, and common errors including the silent field-drop behaviour when CRM fields do not exist before the first webhook call.

1.7.1

Setup Wizard: Added a 3-step onboarding wizard that fires automatically on first activation. Step 1 auto-detects active form plugins, WooCommerce, CMPs, and caching layers. Step 2 collects the GA4 Measurement ID. Step 3 confirms attribution is active with a quick-test link. All external admin notices are suppressed while the wizard is open. A permanent "Setup Wizard" link is added to the plugin action row on the Plugins screen.
Activation fix: Setup_Wizard::init() now registers before the preflight class check so the activation redirect fires reliably on all environments.
Two-phase consent capture: UTMs and click IDs are now buffered to sessionStorage immediately on page load before any consent banner fires. On consent grant the pending buffer is promoted to the attribution cookie, preserving first-touch even when the user accepts the banner on a later page.
Call tracking MutationObserver skip: The MutationObserver watching for dynamically inserted links now bails early when every new anchor has a skippable scheme (tel:, mailto:, #). Eliminates wasted debounce cycles from Dynamic Number Insertion tools such as CallRail, CallTrackingMetrics, and WhatConverts.
GF / WPForms attribution field diagnostic: The Diagnostics conflict scan now checks every active Gravity Forms and WPForms form for ct_* hidden fields. Forms without attribution fields surface a warning with a direct edit link. No new AJAX endpoints.
Cross-domain decoration checklist warning: The setup checklist now shows a warn state when link decoration is on but no allowed domains are listed, and an informational note about external payment providers when decoration is correctly configured.
Cross-domain limitations documentation: Added a "Cross-Domain Limitations" section to the Implementation Playbook and a payment provider table to the Integrations reference covering Stripe, PayPal, Mollie, and Square.
Portuguese (pt-BR) Implementation Playbook: Added IMPLEMENTATION-PLAYBOOK.pt-BR.md covering all rollout patterns including webhook/CRM integrations, the window.ClickTrail JS API field reference, and external checkout limitations.
WP.org compliance: Plugin zip folder renamed from cth to click-trail-handler to match the WordPress.org plugin slug requirement.
Elementor Forms popup fix: Attribution data is now injected reliably when an Elementor popup opens and when new form inputs appear in the DOM after initial page load.
CI: Fixed CodeQL workflow — removed PHP from the language matrix and updated action refs to v4.

1.7.0

Hardening release. No user-visible feature changes; addresses ten findings from the 1.6.0 internal code review.
Fixed admin QA mode cache-poisoning risk: adminQaMode is no longer baked into the localized attribution config, where a full-page cache plugin could capture it from an admin-viewed response and serve it to anonymous visitors. It is now a 1-hour clicutcl_admin_qa cookie set on init only for logged-in manage_options users, which cache plugins correctly exclude.
Fixed minification-exclusion attributes: the previous set advertised support for WP Rocket and LiteSpeed but used non-existent attribute names. Replaced with the canonical attributes each tool actually reads: data-no-optimize, data-noptimize, data-cfasync, data-no-defer, data-no-minify.
Replaced str_replace(' src=', ...) injection with regex-based injection after the opening <script token, robust to attribute order and leading/trailing whitespace.
Refactored Gravity_Forms_Adapter from ~660 lines into four focused classes: Gf_Channel_Resolver, Gf_Form_Settings_Tab, Gf_Merge_Tags, Gf_Minification_Protector. The adapter is now a thin coordinator under 350 lines. All public method signatures preserved; resolve_channel_fallback() kept as a backward-compat shim.
Memoized Attribution_Settings instance inside the adapter and shared it with the extracted classes — fewer redundant Option_Cache reads per request.
Added PHPUnit unit-test suite for Gf_Channel_Resolver covering 10 classification rules, including the gemini.google.com precedence over Google Organic and the fbclid+paid-medium gate.
Added documentation in HOOKS-REFERENCE.md clarifying that ct_* entry meta is registered for all forms but values are gated per-form, and that channel labels are stored data values (not UI strings) and should not be wrapped with __().
Added inline comments documenting fail-open semantics when GF form context is unavailable, and the GF 2.5+ single-arg signature of gform_pre_form_settings_save.

1.6.0

Added full channel classification to Gravity Forms entries: ct_ft_channel stores a human-readable label (Google Ads, ChatGPT, Mailchimp, etc.) derived from click IDs, UTM parameters, or referrer context; server-side fallback computes the label when JS is unavailable.
Added six new click IDs to the capture schema: rdt_cid (Reddit), pin_cid (Pinterest), snap_cid (Snapchat), mc_cid and mc_eid (Mailchimp), and dclid (Display & Video 360).
Added nine {clicutcl_*} merge tags for Gravity Forms notifications and confirmations, including {clicutcl_channel}, {clicutcl_click_id}, and seven UTM-based tags.
Added per-form attribution tracking toggle in Gravity Forms form settings, with a global default option and clicutcl_gf_tracking_enabled filter for developer overrides.
Added admin QA mode: attribution data is written to sessionStorage only when a manage_options user is logged in, preventing admin browsing from polluting attribution records.
Added sessionStorage fallback for attribution capture when browser cookies are blocked.
Added minification-exclusion data attributes to ClickTrail script tags to prevent cache and optimization plugins from deferring or bundling them.
Added entry-edit safety for Gravity Forms: ct_* attribution meta is excluded from the editable fields screen and restored automatically if cleared during a manual entry edit.

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.t

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

标签

下载

详情介绍:

安装:

屏幕截图:

常见问题:

更新日志: