Connect the correct GA4 property to the shop and verify which events actually arrive.
This guide is for Go, Plus and Pro administrators with access to the correct Google Analytics account and permission to change shop measurement. The theme path below applies to Diversity. TPL shops or shops with central Scripts and services can have a different location. First choose direct GA4 installation or Google Tag Manager (GTM).
1. Inventory the existing installation
Check the active theme, domain-specific settings, Scripts and services, GTM container and custom HEAD/BODY code. A G-ID identifies GA4 measurement; a GTM-ID identifies a Tag Manager container. A legacy UA-ID is not a GA4 ID.
Choose one intended route for the same GA4 property. Direct GA4 plus the same purchases sent from GTM can create duplicate events. Do not remove the entire container or other working code when changing one particular tag.
2. Get the correct measurement ID in Google Analytics
Sign in to Google Analytics and choose the correct account and GA4 property. Create them if missing, using the intended time zone and reporting currency.
Open Admin and Data streams and select the shop's web stream. Create a web stream with the correct HTTPS address if needed.
Copy the full measurement ID beginning with
G-. Do not paste the numeric property or stream ID into the measurement ID field.
3. Connect direct GA4 or use GTM
Direct GA4 in Diversity theme settings
If the shop's installation is managed in the theme, open Appearance → Themes → Edit → Add-ons → Google in the correct theme. Enter the measurement ID under Analytics or Google Analytics 4. Check both the all-domain value and domain-specific values. Save and check the active theme; a saved theme copy is not automatically live.
Central configuration in Scripts and services
If your admin version offers Settings → Scripts and services → Google Analytics 4 , use the intended central configuration and its Measurement ID field. Open the existing configuration or add it if missing. Check Active and save only after reviewing the account, measurement ID and consent handling. Do not guess by adding the same installation in the theme too. If unsure which configuration the shop uses, establish that before changing it.
GA4 through Google Tag Manager
For GTM, enter the shop's GTM container in the intended Tag Manager setting and configure GA4 tags in the correct container. The GA4 measurement ID belongs to the Google tag rather than the container ID field. Check triggers, variables, consent and the published container version. A saved GTM workspace is not a published container.
4. Distinguish basic measurement from ecommerce and click events
A page appearing in GA4 does not prove every product, cart and purchase event works. Google's Enhanced measurement is different from Abicart's ecommerce setting. For GTM, the correct shop data layer values must reach the correct GA4 events. Check the actual active theme and delivered configuration.
Wishlist or particular button clicks are not automatically measured merely because a measurement ID exists. They need an intentional event or GTM trigger for the correct element. Check additions and removals, mobile, desktop and that one action is not counted several times. Do not send email addresses, phone numbers or other directly identifying information as ordinary GA4 parameters.
5. Verify and troubleshoot
Use Google's Tag Assistant and GA4 DebugView to follow an intended test visitor. Check page views and required events with the shop's actual consent choices. Do not disable consent protections to obtain more data. Ordinary reports may update later than debugging views; empty reports immediately after installation do not alone prove failure.
Purchases need an actual unique transaction_id, the correct currency, values and items. An empty value or the text undefined is not a correct order ID. Check the full payment and thank-you/return-page journey, including separate payment flows. Follow the provider's test procedure; a real purchase can reserve money and start stock and order processes.
Do not compare GA4 with payment provider payouts as if they were the same metric. Dates, time zones, VAT, shipping, abandoned purchases, consent, blocked scripts and return from payment can differ. Document specific missing or duplicate orders with time, order ID, active theme and container version before changing installation.
If a removed ID returns, first check the correct theme, domain overrides, central configuration and successful saving. No general cache action is proven to solve every such case. Contact support with a reproducible example if the same saved field still returns.
Quick start
Choose direct GA4 or GTM and inventory existing tags.
Get the correct web stream G-ID.
Save through the shop's actual configuration route without duplicates.
Verify page views and intended events, rather than only a green installation indicator.
Subscription and theme
GA4 connection is available in Go, Plus and Pro. The older theme path applies to Diversity; central configuration, TPL, custom code and a commissioned GTM setup must be assessed against their actual installation. An existing connection does not prove complete ecommerce measurement.
