vgdevsolutions

<p><strong>VGDev Cookie Banner for Consent Mode v2</strong> is a lightweight, self-hosted GDPR cookie consent solution that integrates natively with Google Consent Mode v2, Google Tag Manager (GTM) and Google Analytics 4 (GA4).</p>
<p>All consent signals start as <code>denied</code> and are updated in real time based on the visitor’s choices — fully compliant with Google’s requirements for EU markets.</p>
<h4>Key Features</h4>
<ul>
<li>✅ <strong>Google Consent Mode v2</strong> — all 7 consent signals managed automatically</li>
<li>✅ <strong>Google Tag Manager (GTM)</strong> — head snippet + body noscript injected automatically</li>
<li>✅ <strong>Google Analytics 4 (GA4)</strong> — standalone gtag.js support (when GTM is not used)</li>
<li>✅ <strong>GDPR Compliant</strong> — consent defaults to denied before any tracking occurs</li>
<li>✅ <strong>Multilingual Privacy Policy</strong> — set a different privacy policy URL per language</li>
<li>✅ <strong>29 built-in languages</strong> — auto-detected via WPML, Polylang or WordPress locale</li>
<li>✅ <strong>Performance Mode</strong> — lazy loads the banner after user interaction (boosts PageSpeed score)</li>
<li>✅ <strong>Force Consent</strong> — block the page until the user makes a choice</li>
<li>✅ <strong>Fully customizable</strong> — colors, layout, position, floating button, and more</li>
<li>✅ <strong>Self-hosted</strong> — no external consent management platform needed</li>
<li>✅ <strong>Lightweight</strong> — no jQuery dependency for the front-end script</li>
</ul>
<h4>Google Consent Mode v2 Signals</h4>
<p>The plugin manages all required consent signals:</p>
<ul>
<li><code>ad_storage</code></li>
<li><code>ad_user_data</code></li>
<li><code>ad_personalization</code></li>
<li><code>analytics_storage</code></li>
<li><code>functionality_storage</code></li>
<li><code>personalization_storage</code></li>
<li><code>security_storage</code></li>
</ul>
<h4>Consent Categories</h4>
<ul>
<li><strong>Necessary</strong> <span aria-hidden="true" class="wp-exclude-emoji">→</span> <code>security_storage</code></li>
<li><strong>Functionality</strong> <span aria-hidden="true" class="wp-exclude-emoji">→</span> <code>functionality_storage</code>, <code>personalization_storage</code>, <code>security_storage</code></li>
<li><strong>Analytics</strong> <span aria-hidden="true" class="wp-exclude-emoji">→</span> <code>analytics_storage</code>, <code>security_storage</code></li>
<li><strong>Marketing</strong> <span aria-hidden="true" class="wp-exclude-emoji">→</span> <code>ad_storage</code>, <code>ad_user_data</code>, <code>ad_personalization</code>, <code>personalization_storage</code></li>
</ul>
<h4>Multilingual Support</h4>
<p>Works out of the box with WPML, Polylang and WordPress locale. You can also set per-language privacy policy URLs so visitors always see the privacy page in their own language.</p>
<h4>Performance Mode</h4>
<p>Enable lazy loading to load the cookie banner only after the first user interaction (scroll, click, mouse move or touch). Since Google PageSpeed Insights does not simulate interactions, the banner will not appear in the performance audit — significantly improving your Core Web Vitals score.</p>
<h4>Built-in Languages</h4>
<p>English, Greek, German, French, Spanish, Italian, Portuguese, Dutch, Polish, Czech, Slovak, Hungarian, Romanian, Bulgarian, Croatian, Serbian, Slovenian, Estonian, Latvian, Lithuanian, Finnish, Swedish, Danish, Norwegian, Russian, Ukrainian, Chinese, Japanese, Arabic.</p>
<h3>External Services</h3>
<p>This plugin connects to external services provided by Google when the site administrator configures a Google Tag Manager (GTM) Container ID or a Google Analytics 4 (GA4) Measurement ID in the plugin settings.</p>
<h4>Google Tag Manager (GTM)</h4>
<p>When a GTM Container ID is entered in the plugin settings, the plugin loads the Google Tag Manager JavaScript snippet from Google’s servers. This happens on every front-end page load.</p>
<ul>
<li><strong>What it does:</strong> Loads the GTM container script so that tags configured inside GTM (analytics, advertising, etc.) can fire according to consent status.</li>
<li><strong>What data is sent:</strong> The GTM Container ID and standard browser information (IP address, user agent, page URL, referrer) are sent to Google’s servers when the script is loaded. Additional data may be collected depending on the tags configured within GTM by the site administrator.</li>
<li><strong>When it is sent:</strong> On every front-end page load, after the consent defaults have been set.</li>
<li><strong>Service provider:</strong> Google LLC</li>
<li><strong>Terms of Service:</strong> <a href="https://www.google.com/analytics/terms/tag-manager/" rel="nofollow ugc">https://www.google.com/analytics/terms/tag-manager/</a></li>
<li><strong>Privacy Policy:</strong> <a href="https://policies.google.com/privacy" rel="nofollow ugc">https://policies.google.com/privacy</a></li>
</ul>
<h4>Google Analytics 4 (GA4) via gtag.js</h4>
<p>When a GA4 Measurement ID is entered and no GTM Container ID is configured, the plugin loads the Google Analytics gtag.js script from Google’s servers.</p>
<ul>
<li><strong>What it does:</strong> Loads the GA4 measurement script to collect website analytics data (page views, events, etc.) according to consent status.</li>
<li><strong>What data is sent:</strong> The GA4 Measurement ID and standard browser information (IP address, user agent, page URL, referrer) are sent to Google’s servers. Analytics data (page views, session data, events) is only collected according to the visitor’s consent choices.</li>
<li><strong>When it is sent:</strong> On every front-end page load, after the consent defaults have been set. Actual analytics data collection depends on user consent.</li>
<li><strong>Service provider:</strong> Google LLC</li>
<li><strong>Terms of Service:</strong> <a href="https://marketingplatform.google.com/about/analytics/terms/us/" rel="nofollow ugc">https://marketingplatform.google.com/about/analytics/terms/us/</a></li>
<li><strong>Privacy Policy:</strong> <a href="https://policies.google.com/privacy" rel="nofollow ugc">https://policies.google.com/privacy</a></li>
</ul>
<p><strong>Note:</strong> No data is sent to any external service by this plugin unless the site administrator explicitly configures a GTM Container ID or GA4 Measurement ID. The cookie consent preferences are stored locally in the visitor’s browser and are not transmitted to any external server.</p>


VGDev Cookie Banner for Consent Mode v2

GDPR cookie consent banner with Google Consent Mode v2, GTM & GA4 integration. Lightweight, self-hosted, multilingual, fully customizable.

Hugo Carvalho

<p>Attribution usually breaks somewhere between the ad click and the conversion. ClickTrail makes it survive: cached pages, dynamic forms, multi-page journeys, repeat visits, and consent requirements.</p>
<p>ClickTrail keeps the source of the visit, not a profile of the visitor. Capture is first-party and consent-aware: the plugin does not call external services to identify or enrich visitors, and data only leaves your site through integrations you enable yourself (GTM, webhooks, server-side delivery).</p>
<p>ClickTrail stores first-touch and last-touch attribution from the landing page and keeps it available until the conversion point, where it becomes usable inside WordPress:</p>
<ul>
<li>WooCommerce orders</li>
<li>supported forms</li>
<li>browser events</li>
<li>optional server-side delivery</li>
</ul>
<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>
<h4>Pick a starting path</h4>
<ul>
<li><strong>WooCommerce store</strong>: enable Capture and WooCommerce. Orders carry campaign context from day one; add storefront events later if you want funnel signals.</li>
<li><strong>Lead-gen forms</strong>: enable Capture and Forms. Contact Form 7 and Fluent Forms get hidden fields automatically; Gravity Forms and WPForms fill the <code>ct_*</code> fields you add.</li>
<li><strong>GTM / sGTM stack</strong>: enable Capture, Events, and Delivery. Browser events push to the <code>dataLayer</code>, and the server-side adapters feed sGTM or platform APIs directly.</li>
</ul>
<h4>What problems it solves</h4>
<ul>
<li><strong>No paid order reports as “direct”</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>No checkout journey goes dark</strong>: WooCommerce storefront journeys can 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>No cached or AJAX-rendered form drops attribution</strong>: Hidden fields often break on cached pages or dynamically rendered forms. ClickTrail includes client-side fallback and dynamic-content support.</li>
<li><strong>No cross-domain hop breaks continuity</strong>: Approved link decoration and attribution tokens keep continuity between domains or subdomains.</li>
<li><strong>No consent signal is ignored</strong>: Consent controls, browser events, webhook intake, and server-side transport live in the same plugin and respect the same consent state.</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>Recent additions</h4>
<p>Recent releases extended the Gravity Forms integration with channel classification, merge tags, and per-form controls:</p>
<ul>
<li><strong>Channel classification</strong>: every GF entry now receives a <code>ct_ft_channel</code> 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.</li>
<li><strong>Expanded click ID capture</strong>: six additional click IDs (Reddit <code>rdt_cid</code>, Pinterest <code>pin_cid</code>, Snapchat <code>snap_cid</code>, Mailchimp <code>mc_cid</code> / <code>mc_eid</code>, and Display & Video 360 <code>dclid</code>) are now captured and stored.</li>
<li><strong>Merge tags</strong>: nine <code>{clicutcl_*}</code> merge tags are available in GF notifications and confirmations, including <code>{clicutcl_channel}</code>, <code>{clicutcl_click_id}</code>, and seven UTM-based tags.</li>
<li><strong>Per-form toggle</strong>: attribution tracking can be enabled or disabled per form via a dedicated ClickTrail section in Gravity Forms form settings.</li>
<li><strong>Admin QA mode</strong>: attribution data is stored in <code>sessionStorage</code> only when a <code>manage_options</code> user is logged in, preventing admin browsing from appearing in attribution reports.</li>
<li><strong>sessionStorage fallback</strong>: attribution capture now falls back to <code>sessionStorage</code> when the browser blocks cookies.</li>
<li><strong>Minification protection</strong>: ClickTrail script tags carry exclusion attributes recognised by Autoptimize, Cloudflare Rocket Loader, WP Rocket, and LiteSpeed Cache (corrected attribute set in 1.7.0).</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.

VGDev Cookie Banner for Consent Mode v2 vs ClickTrail – UTM, Click ID & Ad Tracking (with Consent)