Analytics · Oct 13-14, 2026
Fixing e-commerce measurement in GA4
GA4 was recording page views but none of the events that matter to a store. I found why, fixed it in an order that avoids double counting, and wrote down the rollback for every step.
0product views, add-to-carts, checkouts or purchases recorded in GA4 over four months
2GA4 properties each counting page views
1property after the fix, with the funnel events arriving once each
What the data showed
I exported every event GA4 had recorded from mid June to mid October. Ordinary events were there, but none of the four e-commerce events. The store's real orders had never been recorded, so no conversion rate, average order value or revenue figure from GA4 could be trusted.
| Event | Before (about 4 months) | After (checked Oct 14) |
|---|---|---|
page_view | 3,769 | one per page |
session_start / first_visit | 3,435 / 3,331 | unchanged |
scroll / user_engagement | 724 / 557 | unchanged |
view_item | 0 | once per product view |
add_to_cart | 0 | once per add |
begin_checkout | 0 | once per checkout start |
purchase | 0 | not tested yet: needs a live order |
Why it happened
- The pixel plugin was installed but had no IDs entered, so it sent nothing. It is the part built to send the e-commerce events.
- Two tags counted page views into two different properties: one placed by the Site Kit plugin and one fired from a Tag Manager container.
- The Google Ads tag loaded separately and only sent its own conversion events.
The fix, and why the order mattered
Site Kit was already placing the analytics tag. If the pixel plugin had been given the same ID first, every page view would have been sent twice. So the sequence was:
- Turn off the analytics snippet in Site Kit but keep the module connected, so its dashboard and reports keep working. Rollback: switch the setting back on.
- Enter the measurement ID in the pixel plugin and enable the four e-commerce events. Rollback: clear the ID.
- Pause the duplicate page-view tag in Tag Manager and publish it as a named version. Rollback: publish the previous version.
How I checked it
A logged-out visitor went from a product page to the cart and checkout while I read the hits and the data layer. Product page: one page view and one product view. Add to cart: one event. Checkout: begin-checkout present. No event was sent twice and only one property received hits. One odd finding was written up rather than patched: the payment-info event fires when the checkout page loads, earlier than ideal.
purchase event can only be proven with a real order, so a low-value test order is the last step before the numbers are trusted for revenue.Tools
Google Analytics 4 (reports and DebugView), Google Tag Manager, Site Kit by Google, Pixel Manager for WooCommerce, browser dev tools for the data layer and network hits.
Part of my 2026 revisions to abundifind.com, a WooCommerce store I own and run. All revisions · Portfolio