Why Does GA4 Show No Data? Common Causes and Fixes

Update time: May 27, 2026

Many novices may encounter the situation where GA4 has no data when they first come into contact with GA4, and they don’t know how to deal with it. Below are several common reasons and corresponding troubleshooting methods that I have summarized.

Reasons Related to GA4

Data Delay

One of the most common beginner misunderstandings is checking reports immediately after installing GA4.

GA4 data is not always processed in real time inside standard reports.

Officially, Google mentions a processing delay of:

However, in practice, most standard reports usually begin showing data within several hours or by the next day.

After implementing GA4: first verify data in Realtime reports， then check standard reports the following day

GA4 Tracking Code Was Removed

Sometimes developers accidentally remove the GA4 tracking code during: website redesigns、theme updates、performance optimizations、migration projects……

Once the tracking code disappears, GA4 naturally stops receiving data.

Open the browser Developer Tools → Network tab.

If Using Direct gtag.js Installation，Filter requests using “gtag”， If you do not see a request for “gtag.js” then the GA4 tracking code is not installed correctly.

If Using GTM Filter requests using “v=2”, GA4 collection requests usually contain “collect?v=2”, If no such requests appear, possible causes include: GA4 tag not configured in GTM、 GTM container not published、 trigger misconfiguration…

GA4 Tracking Code Installation Errors

Sometimes the code exists, but the implementation itself is incorrect.

Tracking Code Not Installed on All Pages:If GA4 is manually deployed: code may be inserted into the wrong location ,only some pages may contain the code, templates may be missing the snippet, As a result, some pages generate data while others do not.
SPA/PWA Tracking MistakesIt ：For SPA or PWA websites, developers often misunderstand how the data layer works. If events are not pushed correctly into the data layer, GA4 will not receive event data.

Filter using “v=2”, If GA4 collection requests are missing, the implementation likely has errors.

Payload Too Large

GA4 limits how much data can be sent in a single request.

Maximum payload sizes:

Universal Analytics: approximately 8 KB
GA4: approximately 16 KB

If the payload exceeds the limit, the request may fail completely.

Reduce parameter lengths 、unnecessary custom dimensions 、oversized payload objects

Filter Configuration Issues

GA4 filters can accidentally block all incoming traffic.

For example, the internal traffic filter may have incorrectly set the IP range, causing normal user data to be excluded.

Check the filter settings in GA4 to make sure you are filtering only intended traffic.

Viewing the Wrong Property

This sounds simple, but it happens surprisingly often.

If you are deploying the Property of “Website A”, but you are looking at “Website B”, don’t be surprised, some people are so careless.

Make sure you are viewing the data in the correct GA4.

Reasons Related to GTM

GTM Container Was Not Published

A very common issue in Google Tag Manager.

Many people configure tags，test in Preview Mode，but forget to publish the container

Until the container is published, live users will not receive the updated configuration.

Publish a new GTM container version.

GTM Container Code Was Removed

If the GTM container snippet is removed from the website, none of the GTM tags can execute, so naturally there is no data.

Use “GTM-” to filter in the network of the browser developer tools. If no GTM requests appear, the container is likely missing.

GTM Configuration Errors

Even when GTM is installed, incorrect configuration can still prevent data collection.

Wrong Measurement ID: you want to deploy G-A, but the actual deployment is G-B, then there will be no data in G-A.
Trigger Problems: No trigger is set, or trigger error will cause no trigger, then there will be no data.

Website-Related Causes

Lazy Loading Issues

Some websites aggressively optimize performance using lazy loading techniques.

In certain cases, JavaScript files may never load properly, including GA4 scripts.

Do not enable Lazy Loading

JavaScript Hidden or Delayed

Some CMS systems or security plugins: delay JavaScript execution，hide scripts in the header，rewrite script tags

This may prevent GA4 or GTM from loading correctly.

Browser and Blocking Issues

Browser Extensions Blocking Tracking

Privacy-focused browser extensions may block GA4 requests entirely.

Temporarily disable browser extensions during testing.

Plug-in can also cause other problems, refer to: Impact of Browser add-ons on Google Analytics 4

Consent Management Platform（CMP）

If a CMP is deployed and users reject tracking consent, GA4 cannot legally collect data.

This is expected behavior.

Content Security Policy（CSP）

If GA4 suddenly stops working without any GTM or GA4 changes, CSP may be blocking Google scripts.

Google officially documents CSP requirements for GTM. For details, please see: https://developers.google.com/tag-manager/web/csp

Add the following code to the header of all pages:

<meta http-equiv="Content-Security-Policy" content="default-src 'self'; script-src 'self' www.googletagmanager.com www.google-analytics.com; connect-src 'self' www.google-analytics.com; img-src 'self' data: www.googletagmanager.com www.google-analytics.com; style-src 'self'; frame-src 'self' www.googletagmanager.com">

Router, Firewall or VPN Blocking

Some corporate environments, VPNs, or firewalls may block Google Analytics domains.

Check whether requests to Google Analytics endpoints are being blocked.

Google-Side Causes

Google Analytics Server Issues or Bugs

This possibility is rare — but it does happen.

You can check the status of Google Analytics services through Google’s official status dashboard.

GA4 Cookie Structure Changes

If Google changes the GA4 cookie structure, tracking logic may suddenly break.

A well-known example occurred in May 2025, when GA4 cookie formatting changes caused some Measurement Protocol implementations to stop working correctly.

GA4’s cookies became:

Final Thoughts

When GA4 shows no data, the problem is usually caused by one of these areas:

tracking code missing
GTM not published
implementation errors
browser or consent blocking
incorrect property configuration
network or CSP restrictions

The fastest troubleshooting method is usually:

open Developer Tools
check Network requests
confirm whether collect?v=2 requests are being sent successfully

If requests are missing, the issue is typically on the implementation side rather than inside GA4 itself.