Understand what to check after a GA4 installation and distinguish Google's setup messages from actual measurement.

This guide is for people using GA4 through Google Tag Manager, for example after a commissioned installation, and those following shop statistics. Abicart Go, Plus and Pro can connect to GA4. An external installation service has its agreed scope; account ownership, ads, audiences and custom events are not automatically included.

Open the correct Google Analytics account and select the GA4 property receiving the installation's data. Check the shop domain, web stream G-ID, correct GTM container and published container version. A legacy Universal Analytics account with a UA-ID is not the current GA4 measurement.

Universal Analytics has been discontinued. The first images below show historical warnings and the countdown to the 2023 transition, rather than a current deadline. Use them to recognise the old view; do not create a parallel installation merely because an old image shows a red banner.

Open GA4 Realtime and use Tag Assistant and DebugView for an intended test visitor. Check page views first, followed by product views, cart and the intended purchase journeys. A measurement ID or Data flowing message does not prove every ecommerce event has correct content.

Select the GA4 property in the account selector before interpreting reports. Older original images below distinguish a previous view from GA4. Report menus can differ with Google's current interface, report collection and your permissions.

Setup Assistant is a checklist for several Google functions. An unmarked item does not always mean website measurement is absent. Conversely, do not ignore every warning merely because someone installed a package. Check each item against intended use and what was actually delivered.

Distinguish data collection from Google Ads links, audiences, key events, advertising features and custom reports. Do not enable new advertising or consent functions merely to complete the checklist.

GA4 needs the correct purchase event with a unique order ID, currency, purchase value and items. GTM also needs the correct trigger and data layer mapping. Check which shop purchase event the published container uses; two triggers for the same business event can duplicate purchases. Do not add direct GA4 over GTM as a general troubleshooting measure.

Compare the same period and time zone. Distinguish product value from shipping, VAT, payment fees and payouts. GA4 web measurement is not the shop's accounts and cannot reliably capture every paid order. Consent, blocking, an interrupted return from payment and processing delays can affect figures. A large or reproducible discrepancy still needs investigation rather than dismissal using a general percentage.

For missing purchases, collect specific order IDs, times, payment method, domain and container version. Check the full payment and return-page journey using an intended test setup. Do not repeatedly make real purchases that can debit customers or book transport.

Use acquisition reports for traffic sources, engagement reports for usage and ecommerce reports for collected product and purchase data. Check property, period and filters before comparing. Ordinary reports can take time to update, whereas Realtime covers a limited recent period.

Wishlist clicks, particular forms, internal links and other custom events need separate definition and verification. Check your order if you commissioned an installation and ask its owner to explain delivered events, Google accounts and container versions. Do not share passwords or customers' personal data in an ordinary troubleshooting request.

Basic GA4 connection is available in Go, Plus and Pro. An installation service and ongoing maintenance are separate commitments. Preserve actual consent handling and recheck measurement when the theme, domain, checkout or container version changes.