WooCommerce conversion tracking: events and order checks

Set up WooCommerce conversion tracking around the actual order event and destination, checking duplicates, consent and differences from store records.

WooCommerce conversion tracking is ready when one purchase reaches the intended analytics property with the correct order identifier, value and currency. Connect one supported purchase sender, then trace an isolated test order into the receiving system. An installed extension or a visible checkout success page does not establish that the event arrived.

This procedure uses Google Analytics for WooCommerce and Google Analytics 4 (GA4). Keep WooCommerce as the order record and your payment provider as the payment record. Analytics measures the buying journey and can differ from both.

Identify the installation and destination

Identify which extension sends purchases and which analytics property receives them before adding another tag. Check the active checkout page for Checkout Blocks, classic shortcode checkout or a customised checkout. Record the WooCommerce and analytics-extension versions alongside that checkout type.

Inspect existing analytics plugins, theme snippets and tag-manager containers. Include any server integration that sends the same purchase. Assign one owner to the GA4 purchase event so an older installation does not keep sending alongside its replacement.

The Google Analytics for WooCommerce setup uses WooCommerce > Settings > Integration > Google Analytics. Enter the web stream’s measurement ID beginning with G-. Enable Purchase Transactions and the journey events you need. The documented purchase method requires a gateway that returns the customer to the order-received page after payment.

Use a separate analytics test property and an isolated store with test payments and fulfilment disabled. Copy the measurement ID from that property’s web stream, then confirm the destination in the outgoing event. A correctly formatted ID can still belong to the wrong property.

Google’s purchase event reference defines the fields to inspect:

  • purchase is the event name for a completed purchase.
  • transaction_id uniquely identifies the order. It must remain the same when that order’s confirmation page is reopened.
  • value is the sum of item price multiplied by quantity, excluding shipping and tax.
  • currency is the three-letter currency code and is required when sending value.
  • items contains the purchased products. Shipping and tax have separate event parameters.

Inspect the payload emitted by your installed release. WooCommerce’s extension changelog records changes to purchase value and transaction identification. A copied legacy snippet can use a different basis from the current event contract.

The extension integrates with the WordPress consent API but does not supply a consent banner. Connect your consent interface and test its accepted and rejected states. Confirm consent updates reach the tag before interpreting a missing purchase as an installation fault.

Trace one purchase to the destination

Trace the same fictional order through checkout and analytics, keeping its identifier beside the amounts you expect. Use invented customer details and a test payment method. Send the order only to your isolated store and test property.

A fictional order to reconcile

Assume a customer buys two storage boxes at $50 each after discount, excluding tax. Shipping is $10 and total tax is $11. The payable order total is $121, while the GA4 item value is $100.

FieldExpected exampleWhat to compare
Order identifierTEST-410The actual saved order number or documented identifier mapping
Item detailsTwo storage boxes at $50Product identifier, quantity and discounted price
Purchase value100Item revenue excluding tax and shipping
CurrencyAUDOrder currency, regardless of the property’s reporting currency
Shipping10Separate shipping amount
Tax11Separate total tax amount
Payable total$121WooCommerce order and test payment record

These are assumed amounts for the exercise, not prices or observed test results. The AUD label above is the machine-readable currency code.

  1. Open the isolated store as a logged-out customer. Connect Google Tag Assistant to your test session and enable device-level debugging.
  2. View the test product, add it to the basket and begin checkout. Inspect the selected journey events before completing payment. Earlier events do not prove purchase tracking works.
  3. Accept analytics consent for this case. Complete the test payment and return to the order-received page through the gateway’s normal redirect.
  4. Open the saved WooCommerce order and write down its identifier, items and amount breakdown. Confirm the payment result separately.
  5. Find purchase in Tag Assistant and inspect its destination and event fields. Compare every value with the order before opening an aggregate revenue report.
  6. Open GA4’s DebugView for that device. Select the purchase and confirm the same identifier, currency and value reached the test property.
  7. Reload the order-received page and revisit it once. Check for another send and whether the receiving system counts the same order again. Repeat with a new order to confirm distinct orders retain distinct identifiers.

Google documents transaction-ID deduplication. Reusing one ID across different orders can undercount purchases. An empty ID can also cause purchases to collapse together. Remove duplicate senders even when deduplication prevents an inflated total.

DebugView establishes event collection for this session. Standard reports process separately. Google’s purchase setup guide says purchase data becomes available in reports after about 24 hours. Keep the event check and the later reporting check distinct.

Diagnose missing or duplicate conversions

Diagnose the first point where the order and event stop matching. Start with the outgoing request, then inspect collection and reporting. Avoid adding another tracking plugin to compensate for an unexplained gap.

Symptoms and corrective checks

SymptomCheckCorrective action
No outgoing purchaseGateway return, enabled purchase option and checkout errorsRepair the supported trigger on the isolated store, then place a fresh order.
Journey events arrive but purchase does notThe actual order-received return and purchase configurationFollow the gateway’s normal return flow and inspect the purchase sender.
Event goes to another propertyMeasurement ID in the outgoing requestCorrect the destination in the owning integration.
Multiple outgoing purchasesExtensions, theme code and tag-manager triggersRetain one purchase owner and remove the overlapping sender from the test installation.
Missing event after consent refusalConsent state and tag behaviourKeep refusal respected. Compare with a separate accepted-consent case.
Correct event absent from reportsDebugView receipt, report period and processing timeAllow processing before treating a reporting delay as a failed event.
Revenue differs from order totalItem value, discounts, tax, shipping and currencyCompare like amounts and repair an incorrect field mapping.
Refunded order still shows purchase revenueWhether the installation sends a corresponding refund eventVerify refund support and reconcile the refund separately.

Google’s ecommerce event guide describes a separate refund event tied to the original transaction ID. A WooCommerce refund does not prove your chosen integration sent that event. On the isolated store, test a refund and inspect its receiving record before relying on net revenue.

Repeat the affected purchase case after a repair. Include a second distinct order, an order-page revisit and both consent states. Keep a short record of the checkout type, sender version, destination and amount basis. Name the person who owns that configuration so a theme, checkout or extension update prompts the same checks.

Once purchase collection is verified, use ecommerce insights to choose the reporting question. Reconcile financial settlement from the payment and accounting records, rather than treating the analytics revenue total as a bank receipt.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup