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.

trackcombo

lucaswhiather

<p><strong>Track Combo — Conversions API for WooCommerce</strong> turns your store into a unified tracking source. One plugin, one tag, and every relevant event reaches Meta (Facebook/Instagram), Google Ads, TikTok, Pinterest, Kwai and any destination you configure in your Track Combo workspace — both from the browser and from the server via the WooCommerce Webhook.</p>
<p>Instead of juggling multiple pixels, conflicting event IDs, and broken deduplication after the iOS 14 / browser tracking updates, Track Combo captures the event once on the storefront, enriches it with first-party data on the server, and fans it out to all destinations with proper <strong>event_id</strong> deduplication between client and server.</p>
<h3>What the plugin does</h3>
<ul>
<li>Injects the Track Combo web tag in the storefront <code><head></code>.</li>
<li>Exposes <code>window.tcWoo</code> with structured product, cart, order, and customer data so events do not depend on DOM scraping.</li>
<li>Registers a native <code>WC_Webhook</code> that sends <code>order.updated</code> to the Track Combo backend when the order reaches the purchase status you choose.</li>
<li>Deduplicates <code>purchase</code> between the client-side <code>complement_data</code> event and the server-side webhook using the order ID as <code>transaction_id</code>.</li>
<li>Declares compatibility with <strong>High-Performance Order Storage (HPOS)</strong> and works with both classic shortcode and <strong>Checkout Blocks</strong> checkouts.</li>
</ul>
<h3>Events sent</h3>
<ul>
<li><code>page_view</code>, <code>search</code>, <code>view_item_list</code>, <code>view_item</code></li>
<li><code>add_to_cart</code>, <code>initiate_checkout</code>, <code>add_shipping_info</code>, <code>add_payment_info</code></li>
<li><code>complement_data</code> (client-side on thank-you page, merged server-side)</li>
<li><code>purchase</code> (server-side via webhook — reliable even when the browser tab is closed)</li>
</ul>
<h3>Why Conversions API</h3>
<p>Tracking quality on WooCommerce stores dropped sharply after iOS 14.5 and the phase-out of third-party cookies. Conversions API (CAPI) is Meta’s, Google’s and TikTok’s answer: send events directly from your server. Track Combo wraps all of them behind one integration.</p>
<h3>Why Track Combo instead of multiple plugins</h3>
<ul>
<li>One plugin instead of one per ad network.</li>
<li>One dedupe boundary handled by Track Combo — no <code>event_id</code> mismatches.</li>
<li>No tag-manager containers to maintain.</li>
<li>Full visibility of every event in the Track Combo dashboard.</li>
</ul>
<p>You need a Track Combo account to use this plugin. Sign up at <a href="https://trackcombo.com/" rel="nofollow ugc">trackcombo.com</a>.</p>
<h3>External services</h3>
<p>This plugin relies on Track Combo (https://trackcombo.com), the service operated by the plugin author, to deliver first-party event tracking and server-side conversion delivery to advertising platforms (Meta Conversions API, Google Ads, TikTok and others). It connects to the following Track Combo endpoints:</p>
<ul>
<li>
<p><strong>Configuration API</strong> — <code>https://server.trackcombo.com/integrationwoocommerce</code>. Called only when the store owner saves the plugin settings in WordPress admin (validate the API key, persist the purchase status filter, register the store domain). Data sent: the API key (HTTP header), and the purchase status or store domain string when those are updated. No customer data is sent through this endpoint.</p>
</li>
<li>
<p><strong>Web tag</strong> — <code>https://track.track-combo.com/tag/{container_id}.js</code> (or your configured first-party CNAME, e.g. <code>https://tracks.yourstore.com/...</code>). Loaded on every storefront page view to enable client-side event tracking. The tag itself dispatches tracking events from the browser to the Track Combo events endpoint.</p>
</li>
<li>
<p><strong>Order webhook</strong> — a WooCommerce webhook registered by the plugin that POSTs the WooCommerce order payload to a URL on <code>server.trackcombo.com</code> whenever an order reaches the purchase status you configure in the plugin settings (default: “Processing”). This enables reliable server-side <code>purchase</code> events even when the customer closes the browser tab.</p>
</li>
</ul>
<p>Track Combo terms of use: https://trackcombo.com/termos-de-uso/<br />
Track Combo privacy policy: https://trackcombo.com/politica-de-privacidade/</p>


Track Combo — Conversions API for WooCommerce

Send WooCommerce events (view, add-to-cart, purchase) to Meta CAPI, Google Ads, and TikTok through Track Combo — no extra pixels needed.

GIA — GA4 Ecommerce Tracking for WooCommerce vs Track Combo — Conversions API for WooCommerce