# Google Analytics not working? Google or your tag

GA4 showing zero? A two-minute check tells a Google reporting delay from a broken tag, then a table matches what you see to the cause and the fix.

_Shaun Brown · October 23, 2026 · https://tagsentry.ai/blog/google-analytics-not-working_

> **The short answer:** First find out whether your site is still sending data. Visit your own site, then open the Realtime report and your browser's Network tab. If your visit shows up and a request to `google-analytics.com/g/collect` goes out, the tag works and Google is slow to process the standard reports, which it says can take 24 to 48 hours. If nothing goes out, or the request carries the wrong measurement ID, the table below names the cause.

## Google or your tag: the two-minute check

Most "Google Analytics stopped working" moments come down to one fork: the data never left your site, or it left and Google hasn't put it in the reports yet. The fixes are opposite, so check which one you have before you touch any tags.

1. Open your site in a private window with ad blockers off, and click around for a minute.
2. In Google Analytics, open Reports › Realtime. It covers the last 30 minutes. If you appear, the tag is sending.
3. In the browser, open DevTools › Network and filter for `collect`. You want a request to `google-analytics.com/g/collect` (or `analytics.google.com/g/collect`) with a 200 or 204 status.
4. Click that request and read its `tid` parameter. It must match the measurement ID in Admin › Data streams, letter for letter. In our test below, `tid` was the only place a typo'd ID showed.

If all four pass, your tag is fine. Leave it alone and read the next section.

## When it's Google: what's normal

Google's own numbers: the Realtime report typically updates within minutes. Intraday data takes 2 to 6 hours and daily data around 12 hours on a standard property, and reports can keep changing for 24 to 48 hours. Some data arrives up to 7 days late.

So "today shows zero but Realtime has people" is often just processing. It can also last longer than usual. From 15 October 2026, [a thread in r/GoogleAnalytics](https://www.reddit.com/r/GoogleAnalytics/comments/1x8iy4g/_/) filled with people whose Realtime and DebugView worked while standard reports showed zero or a fraction of their traffic, some across several properties and with no site changes.

When that happens:

- Compare a day that ended two or more days ago, not today.
- Check the [Ads Status Dashboard](https://ads.google.com/status/publisher), which Google points to for Analytics outages.
- Don't republish tags to fix a delay. You'll only add a second unknown.

## When it's your tag: what we saw in a test

We loaded Google's real tag (gtag.js) for a made-up GA4 property on a test page, under seven setups that make people say GA4 isn't working. Every request to Google Analytics was recorded, then stopped before it left the browser.

| Setup | gtag.js | Requests to /g/collect | What the hit carried |
|---|---|---|---|
| Working tag | loaded (200) | 1 `page_view` | our ID; `_ga` cookie set |
| One letter wrong in the measurement ID | loaded (200) | 1 `page_view` | the wrong ID; `_ga` cookie set |
| Consent denied, no answer yet | loaded (200) | 1 `page_view` | consent state G100, no cookies |
| Tag held until the visitor agrees, no answer | never requested | none | |
| gtag.js blocked, as an ad blocker does | blocked | none | |
| The same tag added twice | loaded once | 2 `page_view` | our ID, twice |
| Debug mode left on | loaded (200) | 1 `page_view` | `ep.debug_mode=true` |

The typo is the one to remember. The script loaded with a 200, a `page_view` went out and a cookie was set, so every quick check passes. Only the `tid` shows the hit is going to a property that isn't yours.

We ran this on 23 October 2026 in Chromium, with Google's tag as served that day.

## The triage table

| What you see | Likely cause | What to do |
|---|---|---|
| Realtime shows you, standard reports show zero | Google is still processing | Wait 24 to 48 hours; compare finished days |
| A `/g/collect` request goes out, Realtime stays empty | The `tid` doesn't match your data stream | Copy the ID from Admin › Data streams into your tag |
| No `/g/collect` request, and no gtag.js in Network | The tag isn't on this page, or a cached page without it is being served | Check the page source; clear your site and CDN cache |
| gtag.js shows as blocked | An ad blocker or privacy extension | Test with it off. Real visitors with blockers won't show, and that's expected |
| Nothing goes out until you click Accept | Your banner holds the tag until consent | Expected where the law asks first; see below |
| Requests carry `gcs=G100` | Consent denied; GA4 gets cookieless pings | Expected. Users in reports fall in places where people refuse |
| Page views roughly doubled | The tag is installed twice (a plugin plus Tag Manager, often) | Remove one copy |
| Your own visits never appear, debug or not | An Active data filter (internal or developer traffic) drops them | Admin › Data settings › Data filters; set it to Testing to check |
| Numbers fell the day a cookie banner went live | Fewer people agree in places that ask first | See [why analytics dropped after a cookie banner](/blog/why-analytics-dropped-after-cookie-banner) |

## Other causes worth ruling out

**Data filters.** An Active internal-traffic or developer-traffic filter drops matching data for good. Google is clear that excluded data "is never processed and will never be available", so a filter set too wide won't come back once you fix it.

**Consent.** Where the law asks first, people who refuse don't become users in your reports. With Google's Consent Mode in its Advanced setup, the tag still sends cookieless pings, as row three of our test shows. [Consent Mode v2, explained](/blog/google-consent-mode-v2-explained) covers the two setups, and our [checklist](/blog/check-consent-mode-v2-working) shows how to read the consent state on a request.

**One event, not the whole property.** If page views arrive but a purchase or sign-up has gone quiet, the property is fine and one tag broke. That's a different hunt, covered in [why tags stop firing without anyone noticing](/blog/tags-stop-firing-silently).

## Where TagSentry fits

[Event monitoring](/monitoring) tells you whether your site is still sending, from real visits. One line of code above Google Tag Manager watches every destination your tags send to, Google Analytics included, and shows each event by name, the fields it sent with their types, and where it went.

It emails you once when an event that matters stops arriving, and once when it's back. "Stopped" is judged against your own site's traffic, so a normal lull reads "Quiet" and sends nothing. In the EU and UK it counts visitors who allowed analytics. It's free to 250,000 events a month.

## Sources

- [Google for Developers: Verify and troubleshoot your Google Analytics setup](https://developers.google.com/analytics/devguides/collection/ga4/troubleshoot?hl=en)
- [Analytics Help: Data freshness](https://support.google.com/analytics/answer/11198161?hl=en)
- [Analytics Help: Realtime report](https://support.google.com/analytics/answer/9271392?hl=en)
- [Analytics Help: Monitor events in DebugView](https://support.google.com/analytics/answer/7201382?hl=en)
- [Analytics Help: Filter out internal traffic](https://support.google.com/analytics/answer/10104470?hl=en)
- [Analytics Help: Data filters](https://support.google.com/analytics/answer/10108813?hl=en)
- [Analytics Help: Analytics service status](https://support.google.com/analytics/answer/3474011?hl=en)
- [r/GoogleAnalytics: reports delayed by a full day since Oct 15](https://www.reddit.com/r/GoogleAnalytics/comments/1x8iy4g/_/)
