A useful WooCommerce and GA4 ecommerce tracking audit follows one controlled order through the complete buying journey, then reconciles the recorded events, transaction ID, currency and value with the WooCommerce order. Start with evidence from a test journey rather than a dashboard screenshot. Google states that ecommerce events are not collected automatically in GA4, so the implementation must send them correctly.
The objective is not to force WooCommerce and GA4 to match at every moment. They are different systems with different processing, consent and attribution rules. The objective is to understand whether the measurement chain is complete enough for the decisions you intend to make.
Define what the audit needs to answer
Before opening a report, write down the decisions the data is expected to support. Typical questions include:
- Which landing pages contribute to orders?
- Where do customers leave the checkout journey?
- Which campaigns produce revenue rather than clicks?
- Are promotions or product changes improving conversion?
- Can finance and marketing reconcile the same completed order?
This prevents a common mistake: collecting more events without knowing whether they improve a decision. A small ecommerce business usually needs a dependable core before adding detailed behavioural tracking.
Map the minimum event chain
Google’s recommended ecommerce events include actions such as view_item, add_to_cart, begin_checkout, add_shipping_info, add_payment_info and purchase. Your implementation may not need every optional event on day one, but the names and parameters you do use should follow the documented specification.
For a practical first audit, map three checkpoints:
- Product interaction: the correct item is viewed or added to the basket.
- Checkout start: the checkout journey begins once, at the intended step.
- Completed purchase: one purchase event carries the correct transaction identifier, currency, value and item data.
Draw the journey on one page. Note which plugin, tag or integration sends each event. If two tools both send the purchase event, duplication is likely. If nobody owns an event, the gap is structural rather than a reporting problem.
Prepare a controlled test order
Use a product, payment method and delivery route that can be identified easily and handled safely. Record the time, device, browser, consent choice, campaign parameters, item, quantity, discount, delivery charge, tax treatment, currency and expected total. Do not place an uncontrolled live order that could create stock, fulfilment or accounting problems.
Run the test in a clean browser session. Keep developer or tag-debug tools available if they are part of the implementation, but also record what appears in the platform itself. The test should be repeatable by another competent person using the same steps.
Validate events before reading trends
Watch the event stream during the test. For each checkpoint ask:
- Did the event fire at the correct action?
- Did it fire once?
- Did the event name use the expected spelling and case?
- Did item identifiers match the WooCommerce product or variation?
- Were currency and value populated consistently?
- Did consent behaviour match the chosen configuration?
A purchase appearing in a report is not enough. A duplicate purchase can inflate revenue. A missing transaction ID can weaken deduplication and reconciliation. A value that includes delivery in one system but excludes it in another can produce a predictable difference that still needs documenting.
Reconcile WooCommerce with GA4
Use WooCommerce as the operational record for orders and GA4 as an analytics system. Choose a defined time window and compare completed, refunded, cancelled and test orders deliberately. Do not compare a WooCommerce lifetime total with a GA4 report using different dates, timezone, filters or attribution settings.
| Check | WooCommerce evidence | GA4 evidence |
|---|---|---|
| Order identity | Order number and status | Transaction ID |
| Time | Order timestamp and store timezone | Event timestamp and property timezone |
| Money | Items, tax, delivery, discount, refund | Currency, value, items and refund events |
| Source | Order attribution fields where enabled | Traffic source and campaign dimensions |
| Consent | Consent or checkout context available to the store | Observed collection behaviour |
WooCommerce’s Order Attribution Tracking records session information for orders when the feature is enabled. Its documentation notes that the feature is session-based and does not build behavioural profiles across sessions. Treat these fields as useful order context, not a substitute for a complete analytics implementation.
Classify discrepancies instead of hiding them
Create a discrepancy log with four columns: symptom, likely cause, evidence and next action. Common categories include:
- Implementation: missing event, duplicate tag or malformed parameter.
- Consent: analytics storage was not available for that user journey.
- Processing: data has not reached the standard report yet.
- Definition: systems use different revenue, refund or timezone rules.
- Attribution: the order exists, but campaign credit differs by model or session.
- Operations: the WooCommerce order later changed status, was cancelled or refunded.
This approach is more useful than applying a blanket “analytics is always lower” assumption. Some differences are expected; others reveal money being assigned to the wrong campaign or events being counted twice.
Check privacy and access at the same time
An audit should document which tools collect data, what consent mechanism is in place and who can access the accounts. Review administrator permissions, unused integrations and personal logins. The technical ability to collect an event does not decide whether it should be collected. UK businesses should align configuration with their privacy information, consent choices and applicable data-protection requirements, taking appropriate advice where needed.
Avoid placing personal data in analytics event parameters. Product, order and transaction identifiers should be designed for measurement without exposing names, email addresses or other direct identifiers.
Turn the findings into a repair sequence
Prioritise fixes by decision risk. A missing or duplicated purchase event comes before a cosmetic dashboard issue. Incorrect currency or value comes before an optional product-list event. A sensible order is:
- repair purchase accuracy and deduplication;
- confirm checkout and basket events;
- align item identifiers and values;
- document consent and attribution behaviour;
- improve reporting only after the chain is stable.
After each change, repeat the controlled test. Keep screenshots or exports, the test order ID, the configuration change and the result. That evidence becomes the baseline for future plugin, theme, checkout or consent updates.
Takeaway
A WooCommerce and GA4 ecommerce tracking audit is not a hunt for identical totals. It is a controlled examination of how one real order becomes data. Map the event owners, test the journey, validate each event, reconcile the transaction and classify every difference. Once the chain is dependable, campaign and conversion decisions become easier to defend.
Need a second pair of eyes? RKS Growth Strategy Solutions can help map the measurement chain, prioritise evidence-led repairs and turn ecommerce data into a practical improvement plan.
Frequently asked questions
Does GA4 collect ecommerce events automatically?
No. Google states that ecommerce events are not collected automatically. Your site or integration must send the recommended events and parameters.
Should WooCommerce and GA4 revenue match exactly?
Not necessarily. Differences can come from consent, processing, timezones, refunds, definitions and attribution. The audit should explain material differences and confirm that the event implementation is accurate.
Which GA4 event confirms a completed ecommerce order?
The recommended event is purchase. It should include a unique transaction identifier and the relevant currency, value and item information.
How can duplicate purchase events be found?
Run one controlled order and inspect the event stream and transaction ID. Check whether more than one plugin, tag or integration sends the same purchase event.
How often should ecommerce tracking be audited?
Test after material changes to checkout, theme, plugins, consent or payment integrations, and run a periodic reconciliation based on the pace and risk of the business.
Internal-link suggestions
- website and system development
- practical growth and systems guidance
- discuss an ecommerce tracking audit
