Google Analytics 4

How to check if GA4 is working

Verify collection from the browser outward: tag, consent, request, Realtime and debug reports. Check one layer at a time before changing the implementation.

2. Inspect browser requests

In plain English: A loaded script is not the same as a successfully sent measurement.

Open DevTools Network, reload, grant consent when appropriate, and filter for googletagmanager, google-analytics or collect requests. Inspect status, Measurement ID and page-location values without exposing private identifiers.

Keep in mind: Test both the initial load and client-side navigation in a single-page application.

3. Check Google tools

In plain English: Use Realtime for recent activity, Tag Assistant for tag behaviour and DebugView for debug-mode events.

Realtime can confirm basic arrival, although processing and report availability are not always immediate. Tag Assistant can identify tags and consent sequencing. DebugView is appropriate when debug mode is enabled and you need event-by-event parameters.

  • Open one test page, then navigate to two more.
  • Confirm one intended page_view per navigation—not zero or two.

4. Diagnose common failures

In plain English: No data usually has a concrete tag, consent, environment or reporting cause.

Check the Measurement ID, hostname guard, consent choice, blockers, Content Security Policy, duplicate tags and SPA navigation. Verify enhanced measurement configuration before adding manual page views that may duplicate automatic history measurement.

Standard reports can take longer than debugging surfaces. Do not repeatedly reinstall the tag while waiting for processing.

  • Missing: no request after consent
  • Duplicate: two collect requests for one page view
  • Misrouted: request carries the wrong Measurement ID

Official Google documentation

Primary references used to verify the terminology and definitions on this page.