Ecommerce Tracking QA: A Pre-Launch Testing Checklist

Why Tracking QA Is Often Skipped

Ecommerce tracking is usually the last item in a site launch or redesign checklist — and often the one that gets sacrificed when the deadline approaches. The consequence: you launch with broken tracking and only discover it weeks later when reporting shows suspicious data, by which time you have lost valuable conversion data.

A systematic QA process before launch takes 2-4 hours and prevents weeks of data loss and remediation work.

Tools Required for QA

• Google Tag Assistant (Chrome extension) — for verifying tag installation
• GA4 DebugView — for verifying event parameters in real time
• GTM Preview Mode — for tracing which GTM triggers are firing
• A staging or pre-production environment matching production (or a willingness to test on production with internal traffic excluded)

Tag Installation Checklist

• ☐ GA4 tag fires on every page (check homepage, category page, product page, cart, checkout, order confirmation)
• ☐ No duplicate GA4 Measurement IDs firing on any page
• ☐ Internal IP filter configured (your office IP is excluded from data)
• ☐ GTM container is the same across all pages (not an old snippet on some pages)

Product Events Checklist

• ☐ view_item_list fires on category page with all visible products in items array
• ☐ select_item fires when clicking a product from the list
• ☐ view_item fires on product detail page with correct item_id, item_name, price
• ☐ item_id format is consistent between list events and detail page events (same ID, not database ID vs SKU)

Cart Events Checklist

• ☐ add_to_cart fires after the item is successfully added (not just on button click)
• ☐ add_to_cart includes correct item_id, item_name, price, quantity
• ☐ value parameter equals price × quantity
• ☐ currency parameter is the correct ISO code
• ☐ remove_from_cart fires when removing from cart
• ☐ add_to_cart does NOT fire on cart page quantity changes (only adds)

Checkout Funnel Checklist

• ☐ begin_checkout fires when user enters checkout
• ☐ add_shipping_info fires with shipping_tier parameter when shipping is selected
• ☐ add_payment_info fires with payment_type parameter when payment method is selected
• ☐ All checkout events include the correct items array (all cart items)

Purchase Event Checklist (Critical)

• ☐ purchase fires on order confirmation page
• ☐ purchase does NOT fire when revisiting the order confirmation page (deduplication working)
• ☐ transaction_id is present and is the actual order ID (not null, not undefined)
• ☐ value is correct (matches order total)
• ☐ currency is correct ISO code
• ☐ items array includes all purchased products with correct item_ids and quantities
• ☐ purchase fires exactly once per test order — place two test orders and confirm two purchase events in DebugView

Post-QA Verification

After QA on staging, repeat the critical tests on production after launch:

1. Place a real test order (or a low-value test product purchase)
2. Verify in GA4 DebugView that the purchase event fires with correct transaction_id and value
3. Refund the test order and verify the refund event fires (if implemented)
4. Check GA4 Realtime to confirm the test purchase appears in Realtime reports

Summary

Ecommerce tracking QA should be scheduled as a formal step in every site launch and major deployment. The checklist above covers tag installation, all product funnel events, and the critical purchase event. The most commonly failed item: purchase event fires on revisits to the confirmation page — always test deduplication explicitly.

See our Conversion Tracking Fix service for tracking audits and QA support.

Need tracking QA before your launch? Contact Adslytics.