Marcin Pietrzak

<p>The <strong>Simple Consent Mode</strong> plugin helps seamlessly integrate Google Tag Manager’s (GTM) Consent Mode v2 on your website, ensuring compliance with privacy regulations like GDPR. This lightweight plugin automatically configures Consent Mode and manages user consent for analytics and marketing cookies.</p>
<p>With Simple Consent Mode, you can dynamically adjust the behavior of your tags based on whether the user has granted or denied consent, while still gathering anonymous data when consent is not provided. The plugin makes it easy to implement, providing a simple interface for enabling and configuring consents, without needing to manually adjust code.</p>
<h4>Key Features</h4>
<ul>
<li><strong>Automatic Consent Mode Configuration</strong>: Integrates GTM Consent Mode v2 with no need for complex manual setup.</li>
<li><strong>Granular Consent Control</strong>: Allows users to opt in or out of specific types of cookies (e.g., analytics, marketing).</li>
<li><strong>GTM Tag Support</strong>: Works seamlessly with Google Analytics, Google Ads, and other GTM tags that rely on user consent.</li>
<li><strong>GDPR and Privacy Compliant</strong>: Helps ensure compliance with global privacy regulations by allowing proper consent tracking.</li>
<li><strong>Lightweight & Easy Setup</strong>: Minimal configuration required.</li>
</ul>
<p>This plugin simplifies the process of integrating and managing GTM’s Consent Mode v2, giving site owners better control over cookie usage while respecting user privacy preferences.</p>
<h4>GitHub</h4>
<p>The Simple Consent Mode plugin is available also on <a href="https://github.com/iworks/simple-consent-mode" rel="nofollow ugc">GitHub – Simple Consent Mode</a>.</p>


Simple Consent Mode

Simple Consent Mode helps integrate GTM Consent Mode v2 on your website.

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.

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