Hugo Carvalho

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 <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.
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:
<ul>
<li>WooCommerce orders</li>
<li>supported forms</li>
<li>browser events</li>
<li>optional server-side delivery</li>
</ul>
Teams can start with order or form attribution first, then add browser events, consent handling, or server-side transport when needed.
<h4>What problems it solves</h4>
<ul>
<li>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.</li>
<li>Checkout continuity breaking before purchase: 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>Cached or dynamic forms: Hidden fields often break on cached pages or AJAX-rendered forms. ClickTrail includes client-side fallback and dynamic-content support.</li>
<li>Cross-domain breaks: Approved link decoration and attribution tokens help keep continuity between domains or subdomains.</li>
<li>Consent and transport complexity: Consent controls, browser events, webhook intake, and server-side transport live in the same plugin.</li>
</ul>
<h4>Core capabilities</h4>
<ul>
<li>Capture: first-touch and last-touch UTMs, major ad click IDs, and referrers with automatic organic/social/referral fallback when UTMs are absent.</li>
<li>WooCommerce: checkout attribution persistence, thank-you purchase event push, enriched commerce payloads, optional storefront commerce events, and optional order-status milestones.</li>
<li>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.</li>
<li>Events: 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>Delivery: optional server-side transport, retry queue, diagnostics, consent-aware dispatch, and failure telemetry.</li>
</ul>
<h4>What is new in 1.5.2</h4>
This maintenance release focuses on code-quality cleanup and standards compliance without changing runtime behavior:
<ul>
<li>Line-ending cleanup: normalized mixed line endings in key PHP handlers so packaging and standards checks stay consistent across environments.</li>
<li>Standards cleanup: resolved PHPCS findings in the consent, attribution-token, and privacy handlers, including targeted documentation for intentional exceptions.</li>
<li>No runtime change: 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>
The main settings experience is organized by capability:
<ul>
<li>Capture</li>
<li>Forms</li>
<li>Events</li>
<li>Delivery</li>
</ul>
Operational screens stay separate:
<ul>
<li>Logs</li>
<li>Diagnostics</li>
</ul>
<h4>Supported integrations</h4>
<ul>
<li>Forms: Contact Form 7, Elementor Forms (Pro), Fluent Forms, Gravity Forms, Ninja Forms, WPForms</li>
<li>Commerce: WooCommerce</li>
<li>CMP sources: ClickTrail banner, Cookiebot, OneTrust, Complianz, GTM, custom</li>
<li>Webhook providers: Calendly, HubSpot, Typeform</li>
<li>Server-side adapters: 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>Contact Form 7 and Fluent Forms: ClickTrail can add hidden attribution fields automatically.</li>
<li>Gravity Forms and WPForms: ClickTrail can populate matching hidden fields you add to the form.</li>
<li>Recommended for Gravity Forms and WPForms: add the hidden fields you want stored or exported, and ClickTrail will fill them.</li>
<li>Elementor Forms (Pro): ClickTrail uses the available submission hooks and attribution fallback, not automatic hidden-field injection.</li>
<li>Ninja Forms: 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.

DIGITLOAD

SOUFIANE EL OUBAYDI

FitConsent is a powerful yet simple Consent Management Platform (CMP) designed to help you comply with privacy regulations like GDPR and CCPA. This plugin makes it incredibly easy to add the FitConsent banner to your WordPress site.
Most importantly, it provides automatic, out-of-the-box compatibility with the WP Consent API, which is the standard used by Google Site Kit.
By using this plugin, you can enable Google Site Kit’s consent mode feature and be confident that your users’ consent choices are respected, allowing for compliant and effective analytics and ad tracking.
Key Features:
<ul>
<li>Simple Setup: Just enter your FitConsent Website ID and the plugin handles the rest.</li>
<li>Google Site Kit Ready: Works seamlessly with Google Site Kit’s consent mode by integrating with the WP Consent API.</li>
<li>Lightweight: The plugin is lean and doesn’t add any bloat to your website. It simply adds the necessary JavaScript to your site’s front-end.</li>
<li>Standardized Communication: Ensures consent signals are passed correctly between your consent banner and other plugins.</li>
</ul>
This plugin is the official and recommended way to integrate FitConsent with a WordPress website, especially if you are using Google Site Kit.
<h3>External Services</h3>
This plugin connects to our main service, FitConsent (at app.fitconsent.com), to function. This connection is essential for fetching the consent banner script and its configuration.
<ul>
<li>Service Provider: FitConsent (a DIGITLOAD product).</li>
<li>What data is sent: The plugin sends your unique “FitConsent Website ID” to our service to retrieve the correct banner configuration for your site. No personal data from your website’s visitors is sent by this plugin. The banner script itself, once loaded, may collect anonymized interaction data and the visitor’s IP address for geo-targeting purposes, as detailed in our policies.</li>
<li>Links to Policies: You can review our service’s policies here:
<ul>
<li><a href="https://fitconsent.com/terms-of-service/" rel="nofollow ugc">Terms of Service</a></li>
<li><a href="https://fitconsent.com/privacy-policy/" rel="nofollow ugc">Privacy Policy</a></li>
</ul>
</li>
</ul>

FitConsent CMP

Integrates FitConsent with WordPress and the WP Consent API for seamless Google Site Kit compatibility.

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