GA4 Real-Time Report Not Updating: Causes and Fixes

GhazanfarApril 17, 20263 min read

You fire a test event, check GA4 Realtime, and see nothing for 5+ minutes. Or Realtime shows active users but your custom events never appear. GA4 Realtime is one of the most useful debugging tools — when it works. Here are the six most common reasons Realtime stops updating and how to fix each one.

Cause 1: Wrong GA4 Property Loaded

The most common cause: you’re testing on a dev/staging environment connected to a different GA4 property than the one you’re viewing. Check which Measurement ID is loading: open DevTools → Network → filter “collect” → click a request → check the “tid” parameter. It must match your GA4 Admin → Data Streams Measurement ID.

Cause 2: Ad Blockers or Privacy Extensions

Realtime uses the same collection endpoint as regular GA4 data. uBlock Origin, Privacy Badger, and similar extensions block GA4 hits. Test in an incognito window with no extensions. If Realtime works in incognito but not regular mode, an extension is blocking — this affects real users too and is a data quality issue to quantify.

Cause 3: Consent Mode Blocking Hits

If Consent Mode is set to analytics_storage: ‘denied’ as default, GA4 won’t fire hits until consent is granted. Check by temporarily granting consent in the console:

// Temporarily grant consent to test Realtime
gtag('consent', 'update', {
  'analytics_storage': 'granted',
  'ad_storage': 'granted'
});
// Then fire a test event and check Realtime

Cause 4: GTM Container Not Published

If you made changes in GTM but forgot to submit/publish, the live website runs the old container version — your new tags don’t exist in production. Check GTM → top right for “Unpublished Changes.” Note: GTM Preview mode runs a temporary version and Preview events DO appear in GA4 Realtime (they’re real data going to your property).

GA4 Real-Time Report Not Updating: Causes and Fixes

Cause 5: Server-Side GTM Misconfiguration

With GTM Server-Side, client-side hits go to your SS container endpoint, not directly to GA4. If the SS container is misconfigured, GA4 never receives the hit — but the client-side tag fires successfully. Debug in GTM SS Preview: does the GA4 tag in the server container show a successful response?

Cause 6: IP Address Data Filter Active

If your IP is in GA4’s internal traffic filter AND the Data Filter is set to Active, your hits are filtered before appearing in any reports — including Realtime. Temporarily disable the Data Filter (set to Testing state) and refresh Realtime to confirm.

Quick Diagnostic Flow

☐ Verify correct Measurement ID via Network tab (tid parameter)
☐ Test in incognito with no extensions
☐ Check Consent Mode status in Console
☐ Confirm GTM container is published (not just saved)
☐ If SS GTM: check server container Preview for GA4 tag response
☐ Temporarily disable Data Filters if IP filtering is active