Google Analytics 4 Realtime Showing 0 Users? A WordPress Tracking Checklist (2026)
Quick answer: If Google Analytics 4 Realtime reports zero users while someone is browsing your website, verify the correct GA4 property, web data stream and Measurement ID. Then run one controlled pageview test and check collection, consent and filters. A zero Realtime result alone is not enough to conclude that no person visited your website.
Updated 5 November 2026 · Practical measurement checklist. WordPress admin and GA4 menu labels can change.
First, understand what Realtime actually measures
GA4’s Realtime reporting is a recent-activity view, not a lifetime visitor counter. The standard Realtime view includes recent users and events, and Google also offers a Realtime pages report with selectable recent windows. Standard acquisition and engagement reports can take longer to process. Comparing today’s Realtime number against a historical dashboard is a common source of confusion.
Step 1: Check your account, property and web data stream
- Open Google Analytics and select the intended account and GA4 property.
- Open Admin → Data streams and choose the website’s web stream.
- Confirm that its website URL corresponds to the domain you are testing.
- Copy the Measurement ID and compare it against the Google tag actually installed on the live site.
Businesses sometimes keep old properties, staging environments and production sites under similar names. A perfectly working tag can report into a different property from the one currently open.
Step 2: Check whether the Google tag is installed once, correctly
WordPress owners may install GA4 using a theme integration, Site Kit, a header-code plugin or Google Tag Manager. Identify the actual method and avoid inserting the same tag a second time merely because Realtime is zero. Duplicate installations can inflate events and create confusing reports.
If you use Tag Manager, make sure the container is published, is loading on the intended pages and has the correct Google tag configuration. For a plugin-based setup, confirm the plugin is active and its connected stream is correct.
Step 3: Perform a controlled visit
Open a public article in a separate browser session after confirming the intended consent choice. Visit more than one page and watch the GA4 Realtime report. If nothing appears, inspect the browser’s tag-debugging tools or the site’s network requests for Analytics events. Use the test to distinguish a missing tag from a report-selection problem.
A browser extension, privacy setting or network filter may prevent your own test from being measured. Where permitted, use a separate clean test browser to isolate that variable. Do not disable a visitor’s consent choices to force tracking.
Step 4: Review consent and privacy rules
A consent-management tool may defer analytics until visitors opt in, depending on the applicable setup and consent configuration. Test the accept and reject paths separately. Respect visitor privacy and the laws that apply to your audience; tracking accuracy does not justify bypassing consent.
Step 5: Inspect internal traffic and developer filters
GA4 supports filters for internal traffic and developer traffic. A test from your own office network or debug session might be classified or excluded. Open Admin → Data filters and inspect whether these rules are active. Google warns that active exclusion filters can permanently exclude incoming matching data, so do not toggle them casually in production.
Step 6: Compare Realtime with standard reports correctly
Realtime checks collection in recent windows, while standard reports reflect processed data and may not update immediately. If your controlled test appears in Realtime but not in a standard report right away, wait for the appropriate reporting window before declaring the implementation broken. Google’s Events report documentation says events can take up to 24 hours to appear there.
Step 7: Verify the real landing pages, not just the homepage
A WordPress homepage might load Analytics while article templates do not, particularly when caching, builder templates, conditional tag rules or consent banners differ. Test at least the homepage, a regular post and a category page. Do not assume a successful home-page tag test proves coverage of every template.
Step 8: Separate traffic acquisition from tracking failures
If the tag records your own controlled visits but your site has no external visitors, the implementation may be functioning correctly. The next question is marketing and discoverability, not GA4 installation. Review Search Console impressions and the article’s indexability, and use tagged campaign links to identify promotion performance.
Our related Google search visibility guide covers publisher discovery; traffic growth and analytics instrumentation are two different projects.
A concise handover report for your developer
- GA4 property name and Measurement ID (not account passwords)
- Production domain and tested public URLs
- Tracking method: Site Kit, GTM, theme or other integration
- Time, browser and consent state of the controlled test
- Realtime result and whether any event was received
- Relevant internal or developer data filter settings
- Screenshots or diagnostic logs with personal data removed
Frequently asked questions
Does zero active users mean the website has no visitors at all?
No. It refers to the measured recent window and selected property. It cannot stand in for a complete historical traffic audit.
Can Tag Assistant visits inflate traffic statistics?
Yes, depending on how your tag and filters are configured. Label testing separately from genuine reader activity.
Should I reinstall GA4 immediately?
No. First verify the property, stream and tag behavior to avoid creating duplicate tracking.
Official references
- Google Analytics: Realtime pages report
- Google Analytics: Events report
- Google Analytics: Data filters
