GA4 Purchase & Revenue Mismatches in WooCommerce

Implementing Hybrid Tracking (Server-Side + Client)

To recover revenue lost to redirects, consent, and ad blockers, move to a hybrid architecture: a server-side GTM container plus carefully wired browser events.

1. Provision a Server Container: Deploy GTM Server-Side on Cloud Run or via a managed provider (e.g., Stape, or similar). Configure a custom subdomain like metrics.yourstore.com.
2. Point Web Tags at the Server Container: In your GA4 config tag, change the endpoint to your server container URL, so browser hits go through your controlled edge.
3. Send Backend Events from WooCommerce: Hook into woocommerce_order_status_processing and woocommerce_order_refunded to send Measurement Protocol hits for purchases and refunds.
4. Unify IDs for Deduplication: Use the WooCommerce order ID as transaction_id and derive a stable event_id that both browser and server share. GA4 and Meta can then dedupe correctly.

This is also where cross-domain and attribution issues between GA4 and Google Ads show up. For a deeper dive specific to attribution and channel-level gaps, point readers to your GA4 cross-domain & attribution issues fix .

Correct DataLayer Structure & Revenue Normalization

GA4 will happily report whatever numbers you send. To match WooCommerce “Net Sales” more closely, make sure your DataLayer and tag mapping are explicit and correct.

window.dataLayer = window.dataLayer || [];
window.dataLayer.push({
  event: "purchase",
  ecommerce: {
    transaction_id: "12345",   // STRING, required
    value: 59.99,              // NUMBER, required
    tax: 4.90,
    shipping: 5.00,
    currency: "USD",
    coupon: "SUMMER_SALE",
    items: [
      {
        item_id: "SKU_12345",
        item_name: "Stan and JOE Shirt",
        price: 25.00,
        quantity: 2
      }
    ]
  }
});
                            

If WooCommerce reports “Net Sales” (excluding tax and/or shipping), you can adjust what you send to GA4 via a Custom JS variable in GTM to remove those components before mapping to value.

Once this is in place, you can safely build and monitor your GA4 vs WooCommerce dashboards in Looker Studio. See your GA4–WooCommerce visualization article for layout and query ideas.

Diagnose with BigQuery & Build an Alignment Proof

Once your implementation work is done, you need to prove — to yourself and to stakeholders — that the GA4–WooCommerce gap is within an acceptable margin. That’s where BigQuery and “proof” dashboards come in.

WITH ga_orders AS (
  SELECT DISTINCT ecommerce.transaction_id
  FROM `your-project.analytics_12345.events_*`
  WHERE event_name = 'purchase'
    AND _TABLE_SUFFIX BETWEEN '20260101' AND '20260131'
)

SELECT
  woo.order_id,
  woo.order_date,
  ga_orders.transaction_id AS ga4_transaction_id
FROM `your-project.your_dataset.woocommerce_export` AS woo
LEFT JOIN ga_orders
  ON CAST(woo.order_id AS STRING) = ga_orders.transaction_id
WHERE ga_orders.transaction_id IS NULL
ORDER BY woo.order_date;
                            

This gives you a concrete list of orders missing in GA4. You can slice those by gateway, country, device, or any other dimension to identify patterns.

From there, your GA4 & Google Ads attribution alignment proof should include before/after screenshots, sample orders traced through both systems, and a documented “acceptable variance” band agreed upon with stakeholders.