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
| Symptom | Check | Likely cause | Fix |
|---|---|---|---|
| No analytics request in the network panel on any page | View the page source for the container or Google tag; the container's live version | Google tag missing from the site, or the container holding it never published | Install the tag on every template, or publish the container version that contains it |
| Requests leave the page but the property stays empty | The measurement ID in the request payload against the stream's ID | Wrong measurement ID, or a stream in a different property | Point the tag at the correct stream's ID, held in one constant |
| Requests absent until the banner is accepted; nothing at all from refusals | The consent state on the first events in preview; the banner's mode | Consent defaults deny analytics storage and no update follows, or tags wait for consent | Correct the default and update sequence; confirm the chosen consent mode |
| DebugView shows events, reports exclude them, or one location vanishes | Data filters and their states; internal traffic rules | A data filter excluding traffic: an over-broad internal rule or an active developer filter | Narrow the rule, or deactivate the filter that is excluding real visits |
| Realtime shows visits, standard reports show nothing yet | How long since the tag started sending; whether a full day has closed | Standard reports not processed yet | Wait 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 (GTMTag management system.), 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.
Consent stops collection
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 (KPIA metric tied directly to an objective.) 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.
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 GA4Google's event-based analytics platform. 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.
