GA4 not tracking? Diagnose in 5 minutes
Answer a few yes/no questions and the diagnoser narrows your GA4/GTM issue from "something's broken" to a specific fix — covers 30+ diagnostic paths built from real client troubleshooting work.
- Diagnose in 5 minutes
- No signup, no email
- Covers 30+ common GA4 issues
Fix My Tracking
Diagnose and fix GA4/GTM tracking problems step by step
What's Going Wrong?
Select the issue that best describes your tracking problem
The 5 root causes of "GA4 not tracking"
About 80% of GA4 tracking issues fall into one of five buckets. The diagnoser above walks you through them in priority order — but if you want the quick mental model:
- Wrong measurement ID — typo, swapped staging vs prod, or the GA4 data stream got recreated.
- GTM container not deployed — preview works, but the live container hasn't been published.
- Consent Mode v2 blocking before consent — events fire but in cookieless mode without the right signals.
- Ad-blocker / CSP header — collect endpoint is blocked at the network or browser level.
- Processing delay on new property — first 24-48h GA4 is "cold-starting" and reports look empty.
The 5-step debug routine that finds 95% of issues
- GA4 Realtime report. If you see your own visit there → tagging works. If not, the tag isn't firing at all.
- GA4 DebugView. Add
?debug_mode=1to your URL or install the GA Debug extension. Events should appear in 5-10 seconds. - GTM Preview. Confirms which tags are firing on which trigger. If GA4 tag isn't in the "Tags Fired" list, the trigger condition is wrong. See our tag management primer for the full mental model.
- Network tab → "collect". Filter to
collectrequests. Status 200 = sent; "(failed)" or no request = blocked. Server-side recovery: Measurement Protocol. - dataLayer inspection. Console:
dataLayer. Verify expected events are pushed with correct parameters.
Adblocker vs CSP vs Consent — how to tell them apart
| Symptom | Likely cause | How to verify |
|---|---|---|
| Network tab shows no collect request at all | Ad-blocker | Open in Chrome incognito with no extensions — request appears. |
Console error Refused to connect ... Content Security Policy | CSP header | Add *.google-analytics.com to connect-src. |
| collect request fires but parameters look stripped (no client_id) | Consent Mode v2 | Check gtag('consent','default') defaults — they may be denying ad_storage. |
| collect fires only on production, not staging | Domain mismatch | Verify staging URL matches GA4 data-stream domain or is unfiltered. |
5 GA4 troubleshooting mistakes
× Trusting Standard reports during debugging
Standard reports lag 24-48h. Always use Realtime + DebugView during active debugging — and BigQuery or the Reporting API for surgical historical queries.
× Testing only with your own browser
Your browser has 6 extensions, a logged-in admin user, and an ad-blocker. Test in a clean profile — incognito + no extensions — before declaring "GA4 is broken".
× Forgetting to publish the GTM container
Preview mode shows tags firing perfectly. Live site shows nothing. The fix is one click — Submit → Publish — but it costs hours of head-scratching when forgotten.
× Confusing duplicate events with missing events
A purchase event firing twice looks like double revenue, not a missing event. Always verify event count per session in DebugView before assuming "we lose half the data".
× Ignoring the change history
"It worked yesterday" is a clue, not an excuse. GTM has version history. WP has the activity log. Check what changed at the moment things broke.
Tracking troubleshooting FAQ
Why is my GA4 not tracking events?
In ~80% of cases the cause is one of: GA4 measurement ID typo or wrong property, GTM container not deployed/published, consent-mode v2 blocking before consent, ad-blocker on your dev browser, or the GA4 24-48h processing delay on a brand-new property.
How do I check if GA4 is actually firing?
Open GA4 → Admin → DebugView in one tab, your site (with debug_mode parameter or GA Debug extension) in another. Events should appear within 5-10 seconds. If DebugView is empty, the tag isn't firing — check GTM Preview, the Network tab for collect calls, and your dataLayer.
Why are my conversions zero in GA4?
Three things to check: the event must be marked as a Key Event (Admin → Events → Mark as conversion), the event must be firing (verify in DebugView), and consent-mode v2 must be sending the event with the correct ad_user_data / ad_personalization signals.
How long does GA4 take to show data?
Realtime reports update within seconds. Standard reports refresh every 24-48 hours for the first 1-2 weeks of a new property, then approach 4-hour latency. If a brand-new property shows nothing after 48 hours, you have a tagging issue, not a delay.
How do I tell if an ad-blocker is breaking GA4?
In Chrome DevTools → Network tab, filter for "collect" or "google-analytics". If the request is blocked or shows "(failed)", an ad-blocker, browser tracking-protection, or your CSP is the culprit. Test in a clean browser profile to isolate.
My GA4 used to work and suddenly stopped. What happened?
Check the change-history first: GTM container changes, theme/plugin updates that injected a CSP header, consent banner upgrades to v2, or the property switching to enhanced-measurement opt-out. Also verify Google Ads linkage — broken linking can hide conversions even if base events still flow.
Can I diagnose tracking issues without GTM Preview?
Yes. The fallback is the GA Debug Chrome extension (it tags all hits as debug_mode), DevTools Network tab filtered to "collect", and the DebugView in GA4 admin. Together they cover ~95% of debugging without ever opening GTM Preview.