GA4 not tracking? Start with these checks.
If Google Analytics 4 (GA4) isn't recording visits or events, start by checking whether your tag loads and sends data to the correct property. The steps below will help you narrow down the cause.
Symptom
You open GA4 and see nothing, or far less than you expect. The Realtime report is empty while you browse your own store. Standard reports show zero users for yesterday. Or some pages and events appear, but not all of them.
Work through the checks below in order. They go from the cheapest test to the more involved ones, and each one rules out a whole group of causes.
Possible causes
- Cause A: no tag on the page. The GA4 snippet or the Google Tag Manager (GTM) container was removed by a theme change, never published, or only added to some templates.
- Cause B: wrong measurement ID. The tag sends data, but to another GA4 property, an old test property or a data stream you don't look at.
- Cause C: consent blocks the tag. Your cookie banner stops GA4 until a visitor accepts, and some visitors never do.
- Cause D: report delay. Standard reports can take a day or more to process. Google's help page on data freshness describes the processing times.
- Cause E: a data filter. An internal-traffic or developer-traffic filter set to Active removes the data before it reaches your reports. Filtered data can't be recovered.
- Cause F: the browser. An ad blocker or privacy setting on your own machine blocks the request, so the tag looks broken to you while working for others.
How to check
- Test in Realtime. Open a private window, visit the store, accept cookies, view two or three pages. Watch Reports, Realtime in GA4. If you appear within a minute or two, collection works and your problem is more likely cause D or E.
- Find the ID on the page. Use Google Tag Assistant, or view the page source and search for
G-andGTM-. Write down every ID you find. - Compare it with GA4. In GA4, go to Admin, Data streams, open your web stream and copy the measurement ID. It must match the ID on the page exactly.
- Watch the network request. Open DevTools, Network tab, filter on
collect, reload. A working tag sends requests to agoogle-analytics.com/g/collectaddress. Check thetidvalue (your measurement ID) and theenvalue (the event name, such aspage_view). - Test before and after consent. Repeat step 4 before you click the banner, then after you accept. If nothing is sent at all until you accept, your setup is blocking GA4 rather than sending cookieless signals. If you use Google consent mode, the
gcsparameter in the request shows the consent state Google received. - Check data filters and GTM. In GA4, Admin, Data filters: note any filter in the Active state. In GTM, open Versions and confirm the live version contains your GA4 tag, then use Preview to see whether it fires.
An illustrative request, shortened, for a working page view might look like this:
https://region1.google-analytics.com/g/collect?v=2&tid=G-AB12CD34EF&gcs=G111&en=page_view&dl=https%3A%2F%2Fexample-store.co.uk%2F
The ID and store address here are invented for the example.
What the result means
- Request sent, ID matches, you appear in Realtime: collection works. Look at report delay, filters, or the date range and comparison you are using.
- Request sent, wrong ID: cause B. Your data is going somewhere, just not to the property you read.
- No request before consent, requests after: cause C. That may be deliberate. It does mean GA4 will undercount visitors who ignore the banner.
- No request and no ID on the page: cause A.
A common false positive. If you test with an ad blocker or a strict browser, you may see no request at all and conclude GA4 is broken. Test in a clean private window, and then in a second browser, before you change anything.
A limitation of public checks. In our public-page check of 975 Shopify stores on 14 November 2026, 196 showed no GA4 or GTM. That is a screening observation, not proof those stores have no analytics: some implementations, such as server-side setups, aren't visible to this type of check, and a public-page check can't confirm whether purchase tracking works.
How to fix it
- Missing tag: add it once, in one place. On Shopify, that usually means the Google and YouTube app or a custom pixel, not a theme file. On WooCommerce, one plugin or one GTM container.
- Wrong ID: replace it with the ID from your data stream. If two properties are in use, decide which one is the record before removing anything.
- Consent: configure your banner and Google consent mode deliberately. Decide whether GA4 should send cookieless signals before consent, and document the choice.
- Filters: move a suspect filter to Testing state and compare. Don't delete it until you know why it was added.
- If the tag fires but events are missing or wrong, the problem is deeper than "not tracking". That needs an event-level review of what each tag sends.
What not to do
- Don't add a second copy of the tag "to be safe". That creates the duplicate problems described in why the same GA4 tag loads twice.
- Don't create a new GA4 property to start over. You lose continuity, and the old tag may keep sending.
- Don't judge from yesterday's standard report alone. Use Realtime and DebugView for live checks.
When to request help
If the tag is present, the ID matches and the data still doesn't add up, a GA4 and GTM audit inspects the deployed tags, consent behaviour, events and ecommerce parameters, and gives you written findings with the evidence.
Related guides:
- Why is the same GA4 tag loading twice?
- Multiple GA4 IDs on one store: what does it mean?
- Shopify purchases not showing in GA4?
Not sure what's wrong?
Send us your store address. Mikael will review the visible tracking signals and explain what can be checked from your public pages.
Sources and updated date
- Google Analytics Help: Data freshness
- Google Analytics Help: Monitor events in DebugView
- Google Analytics Help: Data filters
- Google Analytics Help: Measurement ID
- Google Tag Manager Help: Preview and debug containers
- Google for Developers: Set up consent mode on websites
Last checked against official documentation: 18 November 2026.