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.

UserElements

<p><strong>Paste your Measurement ID. Get trustworthy WooCommerce GA4 ecommerce data.</strong></p>
<p>GIA GA4 is a measurement-quality layer between WooCommerce and Google Analytics 4 (optionally Google Ads). It fires the full recommended ecommerce funnel, enriches every line item, backs up purchases server-side, and respects consent — without Google Tag Manager, without a data team, and without turning WordPress into a profit or attribution platform.</p>
<h4>What GIA GA4 is</h4>
<ul>
<li><strong>Complete GA4 ecommerce schema</strong> — not just purchase, but the real shopping and checkout funnel</li>
<li><strong>Reliable revenue</strong> — browser + Measurement Protocol, with <code>session_id</code>, <code>event_id</code>, and consent-aware server sends</li>
<li><strong>Better item data</strong> — categories, brand, GTIN, discounts, list attribution, classic templates and WooCommerce Blocks</li>
<li><strong>GDPR-ready by default</strong> — Consent Mode V2, CMP bridges, geo rules, and a built-in banner</li>
<li><strong>Store-owner UX</strong> — onboarding wizard, verification tools, and a lightweight dashboard for setup and shop pulse</li>
</ul>
<p>GA4 stays the system of record. GIA GA4 feeds it well; it does not replace it.</p>
<h4>What GIA GA4 is not</h4>
<p>GIA GA4 deliberately avoids feature creep. It is <strong>not</strong>:</p>
<ul>
<li>A profit, COGS, or margin-by-channel tool</li>
<li>A journey analytics or multi-touch attribution platform</li>
<li>A Meta CAPI, TikTok, or ad-spend ingestion hub</li>
<li>A heavy BI dashboard that duplicates GA4</li>
</ul>
<p>The built-in dashboard gives operational context — weekly order insights, view-to-purchase, top customers — not a second analytics product inside wp-admin.</p>
<h4>Who this is for</h4>
<ul>
<li><strong>WooCommerce merchants</strong> who want complete GA4 ecommerce without hiring someone for GTM</li>
<li><strong>Stores with a GA4 ≠ orders gap</strong> who need Measurement Protocol backup and deduplication</li>
<li><strong>EU/UK shops</strong> that need Consent Mode V2 without wrestling CMP + gtag</li>
<li><strong>Growth-minded stores</strong> that optionally want Google Ads purchase conversions on the same stack</li>
</ul>
<p><strong>Not primarily for:</strong> agencies running custom GTM containers, or merchants who want P&L-by-channel inside WordPress.</p>
<h4>Why GIA GA4 vs other WooCommerce GA4 plugins</h4>
<p>Most alternatives stop at purchase (and maybe add-to-cart). GIA GA4 goes deep on <strong>measurement quality</strong>:</p>
<ul>
<li>Full funnel completeness (<code>view_item_list</code> through <code>purchase</code> and <code>refund</code>)</li>
<li>Rich <code>items[]</code> parameters on cart and checkout events</li>
<li>First-class WooCommerce Blocks cart and checkout support</li>
<li>Server-side purchase and refund backup with deduplication</li>
<li>Consent Mode V2 and CMP compatibility out of the box</li>
</ul>
<h4>GA4 ecommerce events</h4>
<p><strong>Discovery & product</strong></p>
<ul>
<li><code>view_item_list</code> — Shop, category, and tag archives (<code>item_list_id</code> / <code>item_list_name</code>)</li>
<li><code>view_item</code> — Product pages and variable-product variant changes</li>
<li><code>select_item</code> — Product clicks from classic shop grids (list context persists through the funnel)</li>
<li><code>view_search_results</code> — On-site product search terms (Extra GA4 events)</li>
<li><code>view_promotion</code> — On-sale products and WooCommerce store notices</li>
</ul>
<p><strong>Cart</strong></p>
<ul>
<li><code>add_to_cart</code> — AJAX, form submit, and WooCommerce Blocks cart (full item payloads)</li>
<li><code>remove_from_cart</code> — Cart page, mini-cart, and Blocks cart</li>
<li><code>view_cart</code> — Cart page and Blocks cart</li>
</ul>
<p><strong>Checkout</strong></p>
<ul>
<li><code>begin_checkout</code> — Classic and Blocks checkout</li>
<li><code>add_shipping_info</code> — Shipping method selected</li>
<li><code>add_payment_info</code> — Payment method selected</li>
<li><code>purchase</code> — Thank-you page with <code>transaction_id</code>, revenue, tax, shipping, coupons, payment method, new vs returning customer, and <code>event_id</code> for deduplication</li>
<li><code>payment_failure</code> — Checkout validation and payment errors (always tracked; classic + Blocks)</li>
<li><code>coupon_applied</code> / <code>coupon_removed</code> — Coupon usage</li>
<li><code>select_promotion</code> — Coupon codes applied at checkout</li>
</ul>
<p><strong>Post-purchase & account</strong></p>
<ul>
<li><code>refund</code> — When a refund is processed in WooCommerce (browser + server)</li>
<li><code>login</code> / <code>sign_up</code> — Optional (enable <strong>Extra GA4 events</strong>)</li>
<li><code>exception</code> — 404 pages (optional)</li>
</ul>
<p><strong>WooCommerce Subscriptions</strong> (when the extension is active)</p>
<ul>
<li><code>subscription_started</code>, <code>subscription_cancelled</code>, <code>subscription_expired</code></li>
<li>Renewal orders sent as <code>purchase</code> via Measurement Protocol</li>
</ul>
<p><strong>Optional extras</strong> (off by default — <strong>Extra GA4 events</strong> setting)</p>
<ul>
<li><code>cart_time_spent</code> — Seconds on cart/checkout before leaving</li>
</ul>
<p>Core funnel events can be toggled individually in <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Events</strong> to reduce volume. Checkout errors, coupons, shipping, and payment events are always tracked.</p>
<h4>Rich GA4 item data</h4>
<p>Every funnel event can include detailed product line items:</p>
<ul>
<li>Hierarchical categories (up to 5 levels)</li>
<li>Brand (auto-detects common brand taxonomies)</li>
<li>GTIN / EAN / UPC when stored in product meta</li>
<li>Variant, image URL, stock status</li>
<li>Sale <code>discount</code> amount on discounted products</li>
<li><code>item_list_id</code> and <code>item_list_name</code> carried from list views through add-to-cart and purchase</li>
<li>Product ID or SKU as <code>item_id</code> (setting)</li>
<li>Product Bundles use minimum bundle price in item data</li>
</ul>
<p>Works on <strong>classic templates</strong> and <strong>WooCommerce Blocks</strong> cart/checkout via the Store API.</p>
<h4>Server-side purchase & refund tracking</h4>
<p>Browser tags are blocked by ad blockers and strict privacy settings. GIA GA4 mirrors <code>purchase</code> and <code>refund</code> from your server using the <strong>GA4 Measurement Protocol</strong>.</p>
<ul>
<li>Saves GA4 <code>client_id</code> and <code>session_id</code> on the order at checkout</li>
<li>Sends <code>event_id</code> on server hits to deduplicate with browser <code>purchase</code> events</li>
<li>Retries failed sends via Action Scheduler</li>
<li>Respects stored analytics consent before server sends</li>
<li>Optional multi-currency normalization for foreign-currency orders (WOOCS / WooPayments rates)</li>
<li>Configurable trigger: order <strong>Completed</strong> or <strong>Processing</strong></li>
</ul>
<p>Add your <strong>GA4 API Secret</strong> in settings and use the built-in <strong>Verify tracking setup</strong> tool.</p>
<h4>Consent Mode V2</h4>
<ul>
<li>gtag loads with consent defaulting to <strong>denied</strong> (configurable)</li>
<li>Built-in consent banner (auto-hides when a CMP is detected)</li>
<li>Geo-aware defaults: EU/EEA/UK <span aria-hidden="true" class="wp-exclude-emoji">→</span> denied, US <span aria-hidden="true" class="wp-exclude-emoji">→</span> granted (optional)</li>
<li>Bridges: CookieYes, Complianz, Cookiebot, and the <a href="https://wordpress.org/plugins/wp-consent-api/" rel="ugc">WP Consent API</a></li>
<li>Order-level consent stored for server-side tracking decisions</li>
</ul>
<h4>Google Ads (optional)</h4>
<ul>
<li>Fire <code>conversion</code> on purchase with your AW- account ID and conversion label</li>
<li>Enhanced Conversions: hashed billing data sent with purchase (same consent rules as GA4)</li>
</ul>
<h4>Other optional features</h4>
<ul>
<li>Google Tag Manager container ID (disable base gtag when GA4/GTM is loaded elsewhere)</li>
<li>Server-side gtag proxy (extends cookie lifetime, reduces blocker impact)</li>
<li>Cross-domain linker settings (domains + incoming parameters)</li>
<li>Transactional email link UTM tagging</li>
<li>First-touch UTM / <code>gclid</code> / <code>fbclid</code> saved to order meta + Traffic Source admin column</li>
<li>Exclude store administrators from tracking</li>
<li>GA4 DebugView mode</li>
<li>Gross vs net revenue on purchase events</li>
<li>Accepts <code>G-</code> and <code>GT-</code> Measurement IDs</li>
<li>HPOS (High-Performance Order Storage) compatible</li>
<li>Onboarding wizard on first activation</li>
<li>Admin warnings when Google Analytics for WooCommerce or Site Kit may duplicate tracking</li>
</ul>
<h4>Built-in dashboard (operational, not BI)</h4>
<p>Admin menu: <strong>GIA GA4 <span aria-hidden="true" class="wp-exclude-emoji">→</span> Analytics</strong></p>
<ul>
<li><strong>Overview</strong> — Setup wizard, tracking verification, and weekly WooCommerce insights (revenue, refunds, customer mix, geo, checkout risk, tracking gap vs GA4 when Site Kit is connected)</li>
<li><strong>Traffic</strong> — GA4 sessions, channels, and landing pages via <a href="https://wordpress.org/plugins/google-site-kit/" rel="ugc">Site Kit</a> when installed (optional)</li>
<li><strong>Products</strong> — Local view-to-purchase report (no Google API required for view counts)</li>
<li><strong>Customers</strong> — Top customers by lifetime spend</li>
<li><strong>Settings</strong> — Full configuration (also at WooCommerce <span aria-hidden="true" class="wp-exclude-emoji">→</span> Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Integrations, redirected to GIA GA4 settings)</li>
</ul>
<h4>Known gaps</h4>
<p>Transparent limits aligned with the measurement-quality focus:</p>
<ul>
<li><code>select_item</code> list attribution on <strong>Block Product Collection</strong> grids is not yet supported (classic shop grids are supported)</li>
<li>No <code>add_to_wishlist</code> or deep promotion CMS integration unless store-specific</li>
</ul>
<p>These are extensions of the same GA4 data-quality goal, not a product pivot.</p>
<h4>Privacy</h4>
<ul>
<li>Registers WordPress personal data export and erasure handlers</li>
<li>Checkout error logs and product view counters auto-expire (configurable retention: 30–365 days)</li>
<li>Enhanced conversion data is hashed before transmission; not stored by this plugin</li>
</ul>
<h3>External Services</h3>
<p>This plugin connects to external services to provide analytics functionality. By using this plugin, you agree to the terms and privacy policies of these services.</p>
<p><strong>1. Google Analytics 4 (required for tracking)</strong></p>
<ul>
<li>Purpose: Records ecommerce events, sessions, and conversions</li>
<li>Data sent: Page views, ecommerce events, hashed customer data (if Enhanced Conversions enabled), client/session identifiers</li>
<li>Domains: <code>www.googletagmanager.com</code>, <code>www.google-analytics.com</code>, <code>region1.google-analytics.com</code></li>
<li>Terms: <a href="https://marketingplatform.google.com/about/analytics/terms/us/" rel="nofollow ugc">Google Analytics Terms</a></li>
<li>Privacy: <a href="https://policies.google.com/privacy" rel="nofollow ugc">Google Privacy Policy</a></li>
</ul>
<p><strong>2. GA4 Measurement Protocol (recommended)</strong></p>
<ul>
<li>Purpose: Server-side <code>purchase</code> and <code>refund</code> event delivery when browser tracking is blocked</li>
<li>Data sent: Order value, line items, transaction ID, client ID, session ID, event ID</li>
<li>Endpoint: <code>https://www.google-analytics.com/mp/collect</code></li>
<li>Terms/Privacy: Same as Google Analytics above</li>
</ul>
<p><strong>3. Google Ads (optional)</strong></p>
<ul>
<li>Purpose: Purchase conversion signals for Smart Bidding</li>
<li>Data sent: Conversion value, transaction ID, hashed customer data (if enabled)</li>
<li>Domains: <code>www.googletagmanager.com</code></li>
<li>Terms: <a href="https://ads.google.com/home/terms/" rel="nofollow ugc">Google Ads Terms</a></li>
<li>Privacy: <a href="https://policies.google.com/privacy" rel="nofollow ugc">Google Privacy Policy</a></li>
</ul>
<p><strong>4. Google Tag Manager (optional)</strong></p>
<ul>
<li>Purpose: Tag deployment when you manage GA4 through GTM</li>
<li>Domain: <code>www.googletagmanager.com</code></li>
<li>Only loaded when a GTM container ID is configured</li>
</ul>
<p><strong>5. Google Site Kit (optional — dashboard only)</strong></p>
<ul>
<li>Purpose: Display GA4 traffic reports inside the GIA GA4 dashboard</li>
<li>Only used when Site Kit is installed and Analytics is connected</li>
<li>Plugin: <a href="https://wordpress.org/plugins/google-site-kit/" rel="ugc">Google Site Kit</a></li>
</ul>


GIA — GA4 Ecommerce Tracking for WooCommerce

Complete GA4 ecommerce tracking for WooCommerce — every funnel event, server-side purchase backup, Consent Mode V2. No Tag Manager. No bloat.

Darwin Cookie Consent vs GIA — GA4 Ecommerce Tracking for WooCommerce