Darwin Digital

<p><strong>Darwin Cookie Consent</strong> shows visitors a clear cookie banner, lets them choose what to accept, and sends those choices to your analytics and marketing tools through Google Consent Mode v2. No tracking runs until consent is given.</p>
<p>The plugin includes admin controls for legal links, appearance, integrations, localized frontend messaging, and privacy-safe reporting.</p>
<h4>Key Features</h4>
<ul>
<li>GDPR cookie consent banner and settings modal</li>
<li>Google Consent Mode v2 support</li>
<li>Editable localized content for English, French, German, and Spanish</li>
<li>Automatic content selection by WordPress site locale</li>
<li>WordPress editor support for the banner message and modal intro</li>
<li>Configurable legal page links for privacy, terms, and cookie policy</li>
<li>Integration controls for Google Tag Manager, GA4, Matomo, Facebook Pixel, LinkedIn Insight Tag, and Pardot</li>
<li>Separate Ad Personalization consent handling</li>
<li>Required Strictly Necessary Cookies row always enabled in the popup</li>
<li>Aggregate admin metrics for recent banner views and accepts</li>
<li>Resettable metrics counters with no personal data stored in the metrics table</li>
</ul>
<h4>Consent Categories</h4>
<ul>
<li><strong>Strictly Necessary Cookies</strong>: always required and always enabled</li>
<li><strong>Analytics</strong>: used for analytics tools such as Google Analytics and Matomo</li>
<li><strong>Marketing</strong>: used for marketing-related tracking integrations</li>
<li><strong>Ad Personalization</strong>: handled separately from general marketing consent</li>
</ul>
<h4>Privacy and Data Handling</h4>
<ul>
<li>Localized content is stored in WordPress options</li>
<li>Consent metrics store aggregate daily counts only — no personal identifiers are stored in the metrics table</li>
<li>The consent log table stores a SHA-256 hash of the visitor IP address and the browser user agent alongside the encoded consent payload; no plain-text IP addresses are stored</li>
<li>Consent Mode signals are updated based on saved user choices</li>
<li>No data is transmitted to the plugin author or any third-party service by this plugin itself</li>
</ul>
<h3>External Services</h3>
<p>This plugin can load scripts from third-party services when those integrations are configured in the plugin settings. No external requests are made unless the corresponding integration is enabled by the site administrator.</p>
<h4>Google Tag Manager</h4>
<p>When a GTM container ID is provided, this plugin loads the Google Tag Manager script from <code>googletagmanager.com</code>. Google Consent Mode defaults are applied before GTM loads so that no tracking occurs without user consent.</p>
<ul>
<li>Data sent: page URL and GTM container ID as part of the script request.</li>
<li>When: on every frontend page load, only if a GTM container ID is configured.</li>
<li>Service provider: Google LLC — <a href="https://marketingplatform.google.com/about/analytics/terms/us/" rel="nofollow ugc">Terms of Service</a> | <a href="https://policies.google.com/privacy" rel="nofollow ugc">Privacy Policy</a></li>
</ul>
<h4>Google Analytics (GA4)</h4>
<p>When a GA4 measurement ID is provided and GTM is not in use, this plugin loads the gtag.js script from <code>googletagmanager.com</code>. The script only fires after measurement consent is granted.</p>
<ul>
<li>Data sent: page URL and measurement ID as part of the script request.</li>
<li>When: on every frontend page load after measurement consent is granted, only if a GA4 ID is configured.</li>
<li>Service provider: Google LLC — <a href="https://marketingplatform.google.com/about/analytics/terms/us/" rel="nofollow ugc">Terms of Service</a> | <a href="https://policies.google.com/privacy" rel="nofollow ugc">Privacy Policy</a></li>
</ul>
<h4>Google Fonts</h4>
<p>When the default plugin font is selected, this plugin loads the Roboto typeface from Google Fonts. The stylesheet is fetched from <code>fonts.googleapis.com</code> and the font files are served from <code>fonts.gstatic.com</code>. A preconnect resource hint is also added for both domains.</p>
<ul>
<li>Data sent: browser and referrer information as part of the font request (standard browser HTTP headers).</li>
<li>When: on every frontend page load when the default font option is active.</li>
<li>Service provider: Google LLC — <a href="https://fonts.google.com/about" rel="nofollow ugc">Terms of Service</a> | <a href="https://policies.google.com/privacy" rel="nofollow ugc">Privacy Policy</a></li>
</ul>
<h4>Facebook Pixel</h4>
<p>When a Facebook Pixel ID is provided, this plugin loads the Facebook Pixel script from <code>connect.facebook.net</code>. The script only fires after marketing consent is granted.</p>
<ul>
<li>Data sent: page URL and pixel ID as part of the script request.</li>
<li>When: on every frontend page load after marketing consent is granted, only if a Pixel ID is configured.</li>
<li>Service provider: Meta Platforms, Inc. — <a href="https://www.facebook.com/legal/terms" rel="nofollow ugc">Terms of Service</a> | <a href="https://www.facebook.com/privacy/policy/" rel="nofollow ugc">Privacy Policy</a></li>
</ul>
<h4>LinkedIn Insight Tag</h4>
<p>When a LinkedIn Partner ID is provided, this plugin loads the LinkedIn Insight Tag from <code>snap.licdn.com</code>. The script only fires after marketing consent is granted.</p>
<ul>
<li>Data sent: page URL and partner ID as part of the script request.</li>
<li>When: on every frontend page load after marketing consent is granted, only if a Partner ID is configured.</li>
<li>Service provider: LinkedIn Corporation — <a href="https://www.linkedin.com/legal/user-agreement" rel="nofollow ugc">Terms of Service</a> | <a href="https://www.linkedin.com/legal/privacy-policy" rel="nofollow ugc">Privacy Policy</a></li>
</ul>
<h4>Salesforce Pardot</h4>
<p>When Pardot account and campaign IDs are provided, this plugin loads the Pardot tracking script from <code>pi.pardot.com</code>. The script only fires after marketing consent is granted.</p>
<ul>
<li>Data sent: page URL and account/campaign IDs as part of the script request.</li>
<li>When: on every frontend page load after marketing consent is granted, only if Pardot IDs are configured.</li>
<li>Service provider: Salesforce, Inc. — <a href="https://www.salesforce.com/company/legal/" rel="nofollow ugc">Terms of Service</a> | <a href="https://www.salesforce.com/company/legal/privacy/" rel="nofollow ugc">Privacy Policy</a></li>
</ul>
<h4>Matomo</h4>
<p>When a Matomo URL and site ID are provided, this plugin loads the Matomo tracking script from the configured Matomo instance. The script only fires after measurement consent is granted.</p>
<ul>
<li>Data sent: page URL and site ID to the configured Matomo instance.</li>
<li>When: on every frontend page load after measurement consent is granted, only if Matomo is configured.</li>
<li>Service provider: InnoCraft Ltd — <a href="https://matomo.org/website-terms/" rel="nofollow ugc">Terms of Service</a> | <a href="https://matomo.org/privacy-policy/" rel="nofollow ugc">Privacy Policy</a></li>
</ul>
<h3>Privacy Policy</h3>
<p>This plugin stores data locally in your WordPress database only. No data is transmitted to the plugin author or any third-party service by this plugin itself.</p>
<h4>Data stored locally</h4>
<ul>
<li><strong>Consent log table</strong> (<code>{prefix}darwin_gdpr_consent_log</code>): When a visitor saves their consent choices, the plugin records a SHA-256 hash of the visitor’s IP address, the browser user-agent string, and the encoded consent payload. No plain-text IP addresses are stored. Entries are automatically deleted after the configured retention period (default: 180 days).</li>
<li><strong>Aggregate metrics table</strong> (<code>{prefix}darwin_gdpr_metrics</code>): Stores daily totals of banner views and consent accepts as integer counts. No visitor identifiers of any kind are stored in this table.</li>
<li><strong>Plugin options</strong>: Localized content strings and appearance settings are stored in the WordPress options table. These contain no visitor data.</li>
</ul>
<h4>Third-party service data</h4>
<p>When optional integrations are configured by the site administrator, scripts from third-party services are loaded in the visitor’s browser. Those services may collect data as described in their respective privacy policies, which are linked in the External Services section above. No data is sent to those services until the visitor grants the relevant consent category.</p>
<p>Site administrators should ensure their own privacy policy reflects the data practices described above, particularly the storage of hashed IP addresses and user-agent strings in the consent log.</p>


Darwin Cookie Consent

Cookie banner for Google Consent Mode v2, GDPR & FADP. Includes four built-in languages, privacy-safe metrics, and appearance controls.

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.

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