Why isn't Google Analytics tracking my website traffic?

Seven common causes in 2026: (1) Google tag (gtag.js) not firing — check view-source on a page and search for G-XXXXXXXXXX measurement ID. (2) Tag fires but blocked by Consent Mode v2 — EU/EEA traffic and now CA + WA require explicit consent before tag captures personal data. (3) Tag installed but wrong stream — common after switching from UA to GA4 + multi-property accounts. (4) Realtime works but reports lag 24-48 hours — normal for first 48h after install, NOT a bug. (5) Enhanced measurement turned off — scroll/outbound clicks/video not auto-tracked. (6) Server-side tag broken — if using sGTM, container config issue. (7) Cross-domain misconfigured — separate web property pulling parallel data.

How do I check if my Google Analytics tag is actually firing?

Three honest methods: (1) GA4 Realtime report — open dashboard.google.com/analytics → Realtime view → load your page in another tab. Should see 1 active user within 30 seconds. (2) Browser Tag Assistant (Chrome extension) — shows every tag firing with payload + errors. (3) View source → search for 'G-' or 'gtag(' or 'window.dataLayer' — confirms tag is present in HTML even if it's blocked from firing. Most operators don't realize #3 catches the 'tag installed but blocked' case that #1 and #2 miss when consent mode is rejecting.

Why is Google Analytics realtime showing data but reports show nothing?

Three possibilities: (1) Reports lag 24-48 hours for new properties — first 48 hours after install is NORMALLY blank in reports while realtime works. (2) Date range wrong — GA4 reports default to 'last 7 days' but if you just installed, you have <7 days of data. (3) Data thresholds — GA4 applies privacy-related data thresholds; very low-volume reports show '(other)' or empty. Wait 48 hours OR adjust date range OR ignore (other) buckets. If still empty after 48h, the install probably has a stream-ID mismatch.

What's the GA4 Consent Mode v2 problem and how do I fix it?

As of March 2024, Google requires Consent Mode v2 signals for EEA/UK/Swiss traffic to receive ad targeting + measurement data. As of 2025+, CA + WA + CT + CO state privacy laws extended similar requirements. If your CMP (Cookiebot, OneTrust, Termly, etc.) is sending consent signals but tag is still tracking before consent grant, you violate the regulation AND lose attribution. Fix: configure CMP to set 'ad_storage' + 'analytics_storage' to 'denied' by default, only flipping to 'granted' on explicit user consent. Most operators have ad_storage default 'granted' which is now non-compliant.

Why is my GA4 attribution showing 'direct' for all traffic?

Five common causes: (1) UTM parameters missing on inbound campaign links — every paid/email/social link needs ?utm_source=...&utm_medium=...&utm_campaign=. (2) Cross-domain tracking misconfigured — user clicks from yourdomain.com to yourapp.com but the second domain's GA4 is a separate property. (3) HTTPS to HTTP referral lost — referer header drops when going from secure to insecure. (4) Privacy browsers (Safari ITP, Firefox ETP) blocking GA4 client IDs — increasing share of 'direct' traffic in 2026 is structural, not your config. (5) Bookmarks + direct typing — actually direct (rare for high traffic). Check #1 and #2 first.

How do I troubleshoot server-side GA4 (sGTM) not collecting data?

Server-side GA4 via Google Tag Manager Server (sGTM) is harder to debug because the failure mode is silent. Check: (1) Container URL configured correctly in Web GTM (custom server tag should point to https://your-sgtm-domain.com). (2) GA4 client created in sGTM with measurement ID + API secret. (3) sGTM server logs — Cloud Run or App Engine logs show every request + response. (4) Network tab in browser DevTools — Web requests should hit your-sgtm-domain.com, not www.google-analytics.com directly. (5) Authentication — App Engine requires service account permissions; Cloud Run requires unauthenticated invoke OR proper auth. Most sGTM 'not working' is actually #4 — Web GTM never switched from default Google endpoint to custom server.

What's a normal Google Analytics 4 sampling rate and when does it become a problem?

GA4 standard properties sample queries at high cardinality — queries returning >10M events get sampled. Sampling rate visible at top of any report (shows percentage of events analyzed). Becomes a problem when: (1) reports show wildly different numbers between sessions, (2) sampling rate < 80%, (3) high-cardinality dimensions like landing-page-path + device + source create combinations exceeding GA4's limits. Fix: upgrade to GA4 360 ($150K+/yr) for unsampled reports, OR export to BigQuery (free for properties under daily quota) and query the raw data.

When should I rebuild Google Analytics versus fix the existing setup?

Rebuild from scratch if: (1) you migrated from Universal Analytics to GA4 and have configuration drift accumulated over 2+ years, (2) cross-domain tracking has 5+ properties all linked weirdly, (3) Enhanced Ecommerce config from UA never properly translated to GA4 events, (4) consent mode was bolted on after GA4 was already live for 12+ months. Fix in place if: (1) install is < 6 months old, (2) single property, (3) one specific event/dimension not tracking. Most operators benefit from a fresh GA4 install with proper consent mode + event taxonomy from day 1 — easier than untangling legacy config.

TL;DR: Google Analytics troubleshooting:the 7 things that actually break. — most cases trace to a config mismatch, a hidden assumption, or a step skipped during setup. The fix path below covers the high-percentage causes first. If you're still stuck after 10 minutes, text PJ — most issues answered in one reply. 858-461-8054.

SideGuy Operator Triage · Google Analytics · 2026-05-27

Google Analytics troubleshooting:
the 7 things that actually break.

Q: What's the GA4 Consent Mode v2 problem and how do I fix it?

As of March 2024, Google requires Consent Mode v2 signals for EEA/UK/Swiss traffic to receive ad targeting + measurement data. As of 2025+, CA + WA + CT + CO state privacy laws extended similar requirements. If your CMP (Cookiebot, OneTrust, Termly, etc.) is sending consent signals but tag is still tracking before consent grant, you violate the regulation AND lose attribution. Fix: configure CMP to set 'ad_storage' + 'analytics_storage' to 'denied' by default, only flipping to 'granted' on explicit user consent. Most operators have ad_storage default 'granted' which is now non-compliant.

Q: Why is my GA4 attribution showing 'direct' for all traffic?

Five common causes: (1) UTM parameters missing on inbound campaign links — every paid/email/social link needs ?utm_source=...&utm_medium=...&utm_campaign=. (2) Cross-domain tracking misconfigured — user clicks from yourdomain.com to yourapp.com but the second domain's GA4 is a separate property. (3) HTTPS to HTTP referral lost — referer header drops when going from secure to insecure. (4) Privacy browsers (Safari ITP, Firefox ETP) blocking GA4 client IDs — increasing share of 'direct' traffic in 2026 is structural, not your config. (5) Bookmarks + direct typing — actually direct (rare for high traffic). Check #1 and #2 first.

Q: How do I troubleshoot server-side GA4 (sGTM) not collecting data?

Server-side GA4 via Google Tag Manager Server (sGTM) is harder to debug because the failure mode is silent. Check: (1) Container URL configured correctly in Web GTM (custom server tag should point to https://your-sgtm-domain.com). (2) GA4 client created in sGTM with measurement ID + API secret. (3) sGTM server logs — Cloud Run or App Engine logs show every request + response. (4) Network tab in browser DevTools — Web requests should hit your-sgtm-domain.com, not www.google-analytics.com directly. (5) Authentication — App Engine requires service account permissions; Cloud Run requires unauthenticated invoke OR proper auth. Most sGTM 'not working' is actually #4 — Web GTM never switched from default Google endpoint to custom server.

Q: What's a normal Google Analytics 4 sampling rate and when does it become a problem?

GA4 standard properties sample queries at high cardinality — queries returning >10M events get sampled. Sampling rate visible at top of any report (shows percentage of events analyzed). Becomes a problem when: (1) reports show wildly different numbers between sessions, (2) sampling rate < 80%, (3) high-cardinality dimensions like landing-page-path + device + source create combinations exceeding GA4's limits. Fix: upgrade to GA4 360 ($150K+/yr) for unsampled reports, OR export to BigQuery (free for properties under daily quota) and query the raw data.

Q: When should I rebuild Google Analytics versus fix the existing setup?

Rebuild from scratch if: (1) you migrated from Universal Analytics to GA4 and have configuration drift accumulated over 2+ years, (2) cross-domain tracking has 5+ properties all linked weirdly, (3) Enhanced Ecommerce config from UA never properly translated to GA4 events, (4) consent mode was bolted on after GA4 was already live for 12+ months. Fix in place if: (1) install is < 6 months old, (2) single property, (3) one specific event/dimension not tracking. Most operators benefit from a fresh GA4 install with proper consent mode + event taxonomy from day 1 — easier than untangling legacy config.

Most "Google Analytics not working" posts walk you through 47 things before naming the real cause. This is the operator-honest 7-step diagnostic — the seven failure modes that account for 95% of GA4 issues in 2026. Built for operators who need data working before standup, not certified marketers.

PJ Zonis · Founder, SideGuy Solutions · Encinitas, CA
Text PJ: 858-461-8054 · No Calendly, no auto-funnel.

The 7-step diagnostic ladder

Run the 7 checks in order — most issues resolve at step 1-3. The deeper steps cover the edge cases that look unfixable until you know the failure mode.

STEP 1

Confirm the tag is actually on the page

View-source on any page · search for G-XXXXXXXXXX or gtag(. No match = tag never installed (CMS plugin disabled · code removed · wrong template). 80% of "GA not tracking" is just the tag not being on the page anymore.

STEP 2

Check Realtime, not reports

analytics.google.com → Realtime view → open your page in another tab. Should see active user within 30s. If Realtime shows 0 users, tag is blocked or wrong measurement ID. If Realtime works but reports are empty, you're hitting the 24-48h lag for new properties (NORMAL — wait 48h).

STEP 3

Consent Mode v2 blocking

As of 2026, GA4 requires Consent Mode v2 for EEA/UK/CA/WA/CT/CO traffic. If your CMP defaults analytics_storage to "granted" pre-consent, GA4 ignores those events. Fix: CMP defaults to "denied", flips to "granted" only on explicit user consent. Most operators have the legacy default that's now non-compliant.

STEP 4

Stream-ID / measurement-ID mismatch

Common after UA→GA4 migration · multi-property accounts · or copying a code snippet from the wrong place. Tag has measurement ID G-ABC123, but reports are configured for G-XYZ789. View-source measurement ID must match GA4 → Admin → Data Streams → Measurement ID exactly.

STEP 5

Cross-domain config broken

User clicks from yourdomain.com to app.yourdomain.com · second domain treats them as new direct visitor. Fix: GA4 → Admin → Data Streams → Configure Tag Settings → List cross-domains. All domains sharing visitor identity must be listed. Misconfig = "direct" traffic spike + broken attribution.

STEP 6

Server-side GA4 (sGTM) container broken

If you migrated to server-side tagging via Google Tag Manager Server, the Web GTM container may still be sending to google-analytics.com instead of your custom server URL. Network tab in DevTools should show requests hitting your-sgtm-domain.com, NOT www.google-analytics.com. If hitting Google directly, sGTM bypassed.

STEP 7

Sampling at high cardinality

GA4 samples queries above 10M events. Reports show sampling % at top. If <80%, your dimension combinations are too granular. Fix: reduce report granularity OR export to BigQuery (free under daily quota) and query raw data. GA4 360 ($150K+/yr) gives unsampled reports — usually not worth it under 50M events/month.

What's NOT broken (don't waste time on these)

(other) bucket in reports. GA4 applies privacy thresholds — low-volume dimensions show as "(other)". Normal, not a bug.

Realtime shows 1 active user that's not you. Google's crawl + monitoring traffic appears as realtime users. Normal.

Direct traffic at 30-40%. Safari ITP + Firefox ETP block GA4 client IDs increasingly in 2026 · "direct" share growing is structural, not your config.

Reports lag 24-48 hours for new install. Realtime works immediately · reports take time to populate. Wait 48h before assuming broken.

The deeper read · operator framing

Most "GA not working" isn't actually about GA. It's about a half-migrated setup · a CMP that's not compliant · or a multi-domain config that worked in UA but didn't translate to GA4. If your GA4 has been live > 18 months and the data feels off, the right move is a fresh GA4 install with consent mode + event taxonomy + cross-domain done correctly from day 1.

Untangling legacy GA4 config typically takes 3-5 hours · doing it fresh on a clean property takes 2 hours. The math favors fresh on most older accounts.

📲 GA4 broken before standup?

Text PJ direct · operator-to-operator. I've untangled GA4 messes for 30+ operators. No Calendly · no consultation fee · just text and we'll work through which of the 7 categories you're in and what to do.

Text PJ · 858-461-8054

Google Analytics troubleshooting:the 7 things that actually break.