Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Marketing Analytics › Troubleshooting

GA4 Not Showing Any Data

Why Google Analytics shows no data: the tag missing or unpublished, a wrong measurement ID, consent denial, data filters, blockers and processing delays.
Troubleshootingbeginner7 min readUpdated

First, confirm that nothing arrives

"No data" needs pinning down, because an empty report and an empty property are different problems. Start with the property selector: confirm you are in the property and data stream the site is meant to feed, since agencies and old setups often leave several near-identical properties behind. Then open Realtime and visit the site from a browser profile with no blocking extensions. If your visit appears, data is arriving and the remaining question is filtering or processing. If it does not, open DebugView with Tag Manager preview running, which marks your visit as debug traffic.

Next, look at the page itself. In the browser's network panel, filter for collect and reload. A request to the analytics endpoint proves the tag sends, and its payload carries the measurement ID it sends to. No request at all means the problem is on the page. The GA4 events reference explains the automatic events you should expect on a first visit, which gives you a list to look for. Finally, if the drop is sudden rather than total, and coincides with a consent banner release, the sibling page on a data drop after a cookie banner is the better starting point.

Diagnosis table

Diagnosis

SymptomCheckLikely causeFix
No analytics request in the network panel on any pageView the page source for the container or Google tag; the container's live versionGoogle tag missing from the site, or the container holding it never publishedInstall the tag on every template, or publish the container version that contains it
Requests leave the page but the property stays emptyThe measurement ID in the request payload against the stream's IDWrong measurement ID, or a stream in a different propertyPoint the tag at the correct stream's ID, held in one constant
Requests absent until the banner is accepted; nothing at all from refusalsThe consent state on the first events in preview; the banner's modeConsent defaults deny analytics storage and no update follows, or tags wait for consentCorrect the default and update sequence; confirm the chosen consent mode
DebugView shows events, reports exclude them, or one location vanishesData filters and their states; internal traffic rulesA data filter excluding traffic: an over-broad internal rule or an active developer filterNarrow the rule, or deactivate the filter that is excluding real visits
Realtime shows visits, standard reports show nothing yetHow long since the tag started sending; whether a full day has closedStandard reports not processed yetWait for a complete processed day before diagnosing further

Fix, verify and prevent each break in the chain

The tag is not on the page, or not live

A theme change, a new checkout template, a page builder that strips head scripts, or a container that was built and previewed but never published all leave pages without a working Google tag. When the tag lives in Tag Manager (GTM), the snippet can be present while the published version contains no Google tag at all.

Fix: install the container on every template, then build and publish the Google tag on the initialisation trigger, following the GA4 through GTM tutorial.

Verify: a collect request appears on each page type, including checkout and error pages, with preview closed.

Prevent: keep a list of templates and check the request on each one after every site release; the sibling page on a GTM tag that is not firing covers a tag that exists but stays silent.

Data sent to the wrong place

Every web stream has its own measurement identifier, and a tag sends wherever that identifier points. A typo, an ID copied from a staging property, a second property created by someone else, or a stream that was deleted and recreated all produce a working tag and an empty report.

Fix: copy the ID from the stream's details page into a single constant variable and reference it from every tag; the stream and property settings are covered step by step in the GA4 setup checklist.

Verify: the request payload carries the corrected ID and your visit appears in Realtime for the intended property.

Prevent: record each property and stream with its owner and purpose, and delete or clearly label properties that should no longer receive data.

A consent banner can legitimately stop analytics data, and a misconfigured one can stop all of it. With defaults set to denied and no update issued when a visitor accepts, tags never switch to full measurement; with the basic implementation, tags do not load until a choice is made, so a broken banner means no data at all.

Fix: check that defaults run on the consent initialisation trigger, that acceptance issues an update, and that the implementation mode was chosen deliberately, using the consent mode guide.

Verify: in preview, the Consent tab shows the state flipping after acceptance and the request after acceptance shows analytics storage granted.

Prevent: retest the three consent states on every template whenever the banner or its template changes.

A filter discards what arrives

Internal traffic rules label hits; data filters then exclude them, but only once a filter is active. A rule written with an address range that matches far more than the office, or a developer traffic filter left active while all testing runs in debug mode, can make a working property look empty to the people checking it.

Fix: review the internal traffic definitions and each filter's state in the setup screens the GA4 setup checklist walks through, narrow over-broad rules, and test a filter in its testing state before activating it.

Verify: ordinary visits appear in reports while the excluded traffic stays out.

Prevent: write down each rule's purpose and range, and revisit them when offices, networks or agencies change, remembering that an active filter's exclusions are permanent.

Reports not processed yet

Realtime and DebugView read events within moments; standard reports are built from processed data. The help centre documents that processing takes time, so a new property can look empty in reports while Realtime is busy.

Fix: wait for a complete day to process before changing anything; the reports and dimensions guide explains how recent days behave.

Verify: the first closed day appears in the standard reports with plausible volumes.

Prevent: never judge a new installation, or a fix, on the current day, and teach report readers to treat the latest days as provisional.

Prevention: collection monitoring

An empty property is usually discovered by the person who needs the data, days after the break. Monitoring moves the discovery to the day it happens. Set a custom insight or alert in the property for a sharp fall in users or key events, so a broken release produces a notification rather than a gap. Keep a release checklist that includes one visit per template with the network panel open after every site or container deploy. Hold a property register listing every property, stream, measurement ID, owner and purpose, so nobody fixes the wrong one. Re-run the consent three-state test whenever the banner changes. And review filters and internal traffic rules on a schedule, because the network they describe drifts. Treat the headline measure (KPI) going to zero as a tracking incident first and a business event second; the tracking outage response SOP sets out what to do once collection is confirmed broken, and the tracking verification checklist is a ready list for the release check.

Illustrative example — not a real result

A relaunch that sent everything to an old property

A garden-furniture retailer relaunches its site on a new platform and sees 0 users in its main GA4 property for 2 days. The network panel shows collect requests on every page, so the tag is present. The payload's measurement ID belongs to a staging property the agency created during the build, which shows 9,400 users for the same 2 days. The constant variable in the container still holds the staging ID. The analyst replaces it with the production stream's ID, publishes, and confirms her own visit in the production property's Realtime report within a minute. The 2 lost days are annotated, the staging property is renamed to make its purpose obvious, and the release checklist gains a line comparing the request's ID with the property register.

Common mistakes

Diagnosing from a browser with blocking extensions. Checking the wrong property. Judging the current day's standard reports. Activating a filter without testing it. Assuming a container snippet on the page means a Google tag is live inside it.

Frequently asked questions

Realtime shows visits but the standard reports are empty. Is something broken?

Usually not. Realtime reads events as they arrive, while standard reports are built from processed data, and the help centre documents that processing takes time. A brand new property or a newly connected stream can show activity in Realtime well before the first full day appears in reports. Check again once a complete day has passed before changing any settings.

How do I tell whether the tag is sending at all?

Open the browser's developer tools on a page of the site, filter the network panel for requests containing collect, and reload. A request to the analytics endpoint means the tag is sending; its payload names the measurement ID it sends to. No request means the tag is missing, blocked, waiting for consent or failing, which the diagnosis table separates.

Can an ad blocker explain a property with no data?

It can explain your own test showing nothing, which is why tests should run in a browser profile without blocking extensions. It cannot explain an empty property for every visitor. If the property is empty for everyone, the cause is in the installation, the measurement ID, consent or a filter, not in individual visitors' browsers.

Terms used on this page

Where this page is used

Also related

Sources

  1. Google Analytics Help — Google Analytics Help
  2. [GA4] About events — Google Analytics Help
  3. Preview and debug containers — Google Tag Manager Help

Related