An online shop sending only the page view to its statistics knows nothing about what happens between a product page and an order: purchase reports stay empty, even though the visitor did go through the whole journey — product viewed, item added to cart, checkout started. This application sends that full journey to Google Analytics 4, with the order's real price rather than the one shown on the page at the moment of the visit.
Who the application is for
For anyone running an online shop who wants to see the real purchase journey in Google Analytics 4 — products viewed, carts, orders — rather than just the page view, to understand where visitors drop off and what actually sells.
What the application does
- Sends the six events recommended for online shops: product viewed, list viewed, added to cart, removed from cart, checkout started, purchase.
- Uses the order's real price — including any discount or tax as applicable — rather than the price shown on the page, which can differ.
- Respects the visitor's consent: nothing is sent before they agree, and events that already happened are sent as soon as they accept.
- Counts each order only once, even if the customer reloads or revisits the confirmation page.
- Runs entirely from the visitor's browser, with no outgoing call from the site's server, which lets it work even on hosting that does not allow that kind of call.
Day to day
- Check that the site's Google Analytics key is properly set: it is what allows events to be sent at all.
- Turn on the debug mode, browse the shop and check in Google Analytics 4 that events do arrive, then switch the mode back off.
- In private browsing, refuse then accept tracking to check that the pending events are indeed sent the moment consent is given.
- If nothing arrives, check in order: the Google Analytics key, the base tracking layer's installation, the visitor's consent, then any ad blocker in your own browser.
What the application does not do
- It does not display any consent banner itself: it reads the one already in place on the site.
- It sends nothing to Meta or Google Ads.
- It does not replace the site's Google Analytics key: it relies on it to work.
Getting started
Make sure the site's Google Analytics key is set, leave the separate measurement ID blank unless you deliberately want another property, then check that events arrive in debug mode before switching it off for good: left on, it would mix your real traffic with your test traffic in the reports.
Going further
To find out whether this application suits your business and how to activate it, compare the plans or write to us.