Taking on new projects

GA4 Not Tracking? 9 Common Causes and How to Fix Them

Google Analytics 4 is only useful if you trust the numbers. When clients tell me “GA4 isn’t working”, it usually means one of three things: no data at all, missing conversions, or numbers that are obviously wrong. Here are the causes I find most often, in roughly the order I check them.

First, rule out the waiting game

Standard GA4 reports can take 24 to 48 hours to fully process. Before you assume something is broken, open the Realtime report and DebugView, then visit your site. If you see yourself there, tracking is working and you just need to wait for the standard reports.

1. The tag was removed during a redesign or theme change

This is the most common cause by far. The tracking code lived in the old theme’s header, the theme was replaced, and the code went with it. Check the page source for your measurement ID (it starts with G-) or your Google Tag Manager container ID (GTM-).

2. The Tag Manager container was never published

Changes in Google Tag Manager do nothing until you click Submit and publish a new version. Preview mode works, the live site does not. Check the Versions tab to see what is actually live.

3. Wrong measurement ID

Copying an ID from the wrong property, or from an old Universal Analytics setup, sends data somewhere you are not looking. Match the ID in your site against Admin, Data streams in GA4.

4. Duplicate tags

If traffic doubled overnight, look for the same GA4 tag installed twice: once by a plugin and once in Tag Manager, for example. Tag Assistant will show you every tag firing on a page.

5. Key events are not marked

In GA4, conversions are now called key events. An event can be firing perfectly and still not count as a conversion because nobody marked it as a key event in Admin, Events.

6. The form event never fires

Many forms submit with JavaScript and never load a thank-you page, so a “page view of /thank-you/” trigger never happens. Track the form’s own success event instead, or push a custom event to the data layer when the form succeeds.

If you use a cookie banner with Consent Mode, analytics may only record visitors who accept. That is correct behaviour for visitors who decline, but a misconfigured banner can block everyone. Test with consent accepted and check that tags fire.

8. Filters and referral settings

An internal traffic filter set to Active with a wrong IP range can exclude real visitors. Payment gateways and booking tools that send users away and back can also steal credit for conversions unless you list them as unwanted referrals.

9. Malware stripped or replaced the code

This surprises people, but I have seen it on real cleanups: malicious code injected into a site can break or replace analytics scripts. If tracking died at the same time as other strange behaviour, check the site for malware before anything else.

My quick diagnostic order

  1. Realtime report and DebugView: is any data arriving?
  2. Page source: is the right ID on the page, and only once?
  3. Tag Manager: is the latest version published?
  4. Events: do your key actions fire, and are they marked as key events?
  5. Consent, filters and referrals: is anything excluding real visits?
  6. Security: any signs of injected code?

If you would rather hand this over, I set up and repair GA4 and Tag Manager tracking, including forms, calls and WhatsApp clicks.

Hire me