GA4 Ecommerce Tracking Audit Checklist: From Product View to Purchase

The audit flow

A GA4 ecommerce audit tests the full path from the product page to the purchase event reaching GA4. Each step depends on the one before it, so test in order and fix the earliest failing step first. A break early in the flow breaks everything downstream, so a missing view_item event means the later stages cannot be validated properly until it is fixed.

1. Product page loads

Start at the product page. Confirm the page loads and the product data is available. The product data has to exist on the page before any event can carry it. If the product page does not load or the data is not available, no downstream event can be correct.

2. Product data is available

Inspect the data layer on the product page and confirm the product data is present. The item_id, item_name, price and currency should match the product shown. If the data layer holds the wrong product or no product, the view_item event will carry wrong data. Product data accuracy is covered in the guide on GA4 view item product data wrong.

3. view_item fires

Confirm the view_item event fires when the product page loads. Check GTM preview for the tag firing and GA4 DebugView for the event. Confirm the items array contains the correct product. A view_item that does not fire or fires with no items is the first break in the funnel.

4 and 5. Add to cart and add_to_cart fires

Add a product to the cart and confirm the add_to_cart event fires. Because many stores add to cart with AJAX, confirm the trigger fires on the action, not on a page load. Check that the items array contains the added product with the correct quantity. The add to cart flow is covered in the guide on GA4 add to cart not working.

6 and 7. Checkout begins and begin_checkout fires

Start checkout and confirm the begin_checkout event fires at the right point. Identify where checkout actually begins in your store and confirm the trigger matches that action. Check the items and value in the event. The begin checkout flow is covered in the guide on GA4 begin checkout not firing.

8 and 9. Order completes and purchase data is available

Complete a test order and reach the confirmation page. Confirm the order data is available, including the transaction_id, value, currency and items. The purchase event depends on this data existing first. If the confirmation page has no order data, no purchase event can be correct. The purchase flow is covered in the guide on GA4 purchase event not firing.

10. purchase fires

Confirm the purchase event fires on the confirmation page. Check GTM preview for the tag firing and GA4 DebugView for the event. Confirm the event includes the transaction_id, value, currency and items array. A purchase that fires without transaction_id cannot be deduplicated, which is covered in the guide on GA4 purchase transaction ID missing.

11. transaction_id is populated

Confirm the transaction_id is populated with the real order ID and is unique per order. The transaction_id is what distinguishes one purchase from another and what allows duplicate detection. An empty or repeated transaction_id breaks deduplication and reconciliation.

12. value and currency are correct

Confirm the value and currency in the purchase event match your intended definition. Check whether tax, shipping and discounts are included or excluded as you expect. A wrong value usually comes from a definition mismatch at the data layer. The value flow is covered in the guide on GA4 purchase revenue wrong.

13. items contain correct product data

Confirm the items array in the purchase event contains the correct products with the right item_id, item_name, price and quantity. Each item should match a product in the order. The items structure is covered in the guide on GA4 ecommerce items array missing and the field values in the guide on GA4 ecommerce product data wrong.

14. Event reaches GA4

Confirm each event reaches GA4. Check DebugView for live confirmation, since standard reports have a processing delay. An event that fires in GTM but does not appear in DebugView may have the wrong measurement ID or a consent issue. The general event flow is covered in the guide on GA4 events not showing.

15. Duplicate events are checked

Check for duplicate events at each stage. For purchase, use the transaction_id to confirm one order produces one event. Duplicates inflate counts and distort the funnel. The duplicate purchase flow is covered in the guide on GA4 purchase event firing twice and the Shopify-specific flow in the guide on Shopify GA4 duplicate purchase tracking.

16. Store orders are compared with GA4

Compare the store order count and revenue against GA4 for the same period. The numbers will not always be identical, but large unexplained gaps are worth investigating. Separate missing purchases, duplicate purchases and value definition differences. The reconciliation process is covered in the guide on GA4 revenue not matching store.

17. Live production behavior is validated

Preview mode proves configuration works under controlled conditions. Validate against live production behavior as well, because real customers face consent, ad blockers and paths that preview does not reproduce. Confirm events fire for real orders, not just test orders. The difference between preview and production is covered in the guide on server-side tracking preview not production.

How to run the audit

1. 1.Walk the full journey from product page to purchase with a test order.
2. 2.At each stage, confirm the event fires with the correct data in GTM preview.
3. 3.Confirm each event reaches GA4 in DebugView.
4. 4.Check for duplicate events using transaction_id.
5. 5.Compare store orders against GA4 and validate against live production.