You open GA4 and see nothing. Zero users, no events, blank reports. Or worse — you see some data, but you know it's incomplete. Pages are missing, events aren't firing, and your real-time report shows 2 users when your site clearly has traffic.

Before you panic, know this: GA4 tracking failures are almost always caused by one of 12 common issues. We've diagnosed hundreds of these at NiceLookingData, and the fix is usually faster than you think.

1. The GA4 Tag Isn't Installed (Or Is On the Wrong Pages)

Symptoms: Zero data across all reports.

This is the most obvious one, but it happens more than you'd think — especially after site redesigns, CMS migrations, or theme changes. Your GA4 measurement ID (G-XXXXXXXXXX) needs to be present on every page. Check by opening your browser's Developer Tools → Network tab, filter for "collect", and look for requests to google-analytics.com.

The fix: Install via Google Tag Manager (recommended) or directly in your site's <head> tag. If using a CMS like WordPress, verify your plugin is active and the measurement ID matches your GA4 property.

2. Wrong Measurement ID

Symptoms: Tag fires but data appears in the wrong property.

You'd be surprised how often teams have the measurement ID from a different GA4 property — a staging property, a test property, or a deprecated one. Every GA4 data stream has a unique G-XXXXXXXXXX ID. Verify yours under Admin → Data Streams → your stream.

3. Consent Mode Blocking Collection

Symptoms: Dramatic data drop, especially from EU traffic.

If your Consent Management Platform (CMP) is incorrectly configured, it may set analytics_storage to denied by default and never update it — even after users consent. This silently blocks GA4 from collecting any data for those users. Check your browser console for the gtag('consent', 'update', ...) call after accepting cookies.

4. Ad Blockers and Browser Privacy Features

Symptoms: 15-30% data gap compared to server logs.

Ad blockers like uBlock Origin, Brave browser's shields, and Firefox's Enhanced Tracking Protection all block requests to google-analytics.com. This is expected behavior and accounts for 15-30% data loss on most sites. The only complete solution is server-side tagging via GTM, which routes analytics through your own domain.

5. GTM Container Not Published

Symptoms: Tags work in GTM preview mode but not on the live site.

A classic mistake: you set up your GA4 tag in GTM, test it in preview mode (where it works perfectly), but forget to click Submit to publish the container version. Until published, no changes go live. Check your GTM container's version history to confirm the latest version is published.

6. Data Stream Is Paused or Deleted

Symptoms: Sudden complete data stop.

If someone paused or deleted the web data stream in GA4, no data will be collected even though your tag is firing. Navigate to Admin → Data Streams and verify your stream is active. Also check that the stream's URL matches your actual website domain.

7. Data Filters Are Active (Not Just Testing)

Symptoms: Partial data loss — some traffic or events are missing.

GA4 data filters can exclude traffic based on the traffic_type parameter. If your filter is set to Active (not just Testing), it permanently removes matching data from reports. Check Admin → Data Settings → Data Filters. An overly broad filter — like blocking a VPN IP range that many users share — can silently eliminate legitimate traffic.

8. Duplicate Tags Causing Data Inflation

Symptoms: Inflated page views, doubled event counts.

The opposite problem: GA4 is tracking, but it's tracking too much. If you have both a GTM tag and a hardcoded gtag.js snippet, every event fires twice. Check for duplicate G-XXXXXXXXXX measurement IDs in your page source. Use the GA Debugger Chrome extension to spot doubled hits.

9. Single Page Application (SPA) Not Sending Page Views

Symptoms: Only the first page view is tracked; navigation within the site shows no additional page views.

React, Angular, Vue, and Next.js apps use client-side routing — the URL changes without a full page reload. GA4's enhanced measurement handles history.pushState() changes automatically, but some SPA frameworks use custom routing that doesn't trigger this. Verify by navigating between pages and checking the real-time report.

10. Event Parameter Limits Exceeded

Symptoms: Events fire but custom parameters are missing.

GA4 has hard limits: 25 event parameters per event, parameter names max 40 characters, parameter values max 100 characters. Exceed any of these and the data is silently dropped. You won't see an error — the event still fires, but the offending parameters vanish.

11. Real-Time Report Delay

Symptoms: You think tracking is broken because you don't see yourself.

GA4's real-time report has a 30-second delay. Standard reports can take 24-48 hours to process. If you just installed your tag, don't judge results from standard reports — use DebugView (Admin → DebugView) with the GA Debug Chrome extension for instant verification.

12. Browser Caching Serving Old Pages

Symptoms: You added the tag but it's not firing on your device.

Your browser may be serving a cached version of the page from before you added the GA4 tag. Hard refresh (Cmd+Shift+R on Mac, Ctrl+Shift+R on Windows) or open an incognito window to test with a clean cache.

Instant Diagnosis

NiceLookingData checks for all 12 of these issues automatically. Run a free audit and we'll tell you exactly what's broken and how to fix it — in 30 seconds.

Systematic Debugging Workflow

When GA4 isn't tracking, work through this order:

Check if the tag is present on the page (view source → search for your G- ID)
Verify the correct measurement ID in GA4 Admin → Data Streams
Open DebugView to see if events arrive in real-time
Check for consent mode blocking in the browser console
Verify GTM container is published (not just saved)
Look for duplicate tags or conflicting scripts
Test in an incognito window with no extensions
Check data filters and stream status in GA4 Admin

90% of GA4 tracking failures are resolved within the first 4 steps. If you're still stuck, the issue is almost always consent-related or caused by a JavaScript error that prevents the tag from executing.

GA4 Not Tracking? The Complete Troubleshooting Checklist