Docs menuWhy wasn't my visit counted?

Why wasn't my visit counted?

Run "Check this visit" in Settings to see which rule, setting or plugin kept your own visit out of Vireo's numbers, with a link to the setting to change.

On this page

When you browse your own site and the visit doesn’t show up, “Check this visit” tells you why. It tests the browser you’re using right now and lists each reason, with a link to the setting that causes it.

Run the check

Go to Vireo Analytics, Settings, Troubleshooting, and find “Why wasn’t my visit counted?”. Type a page in “Page to check”, as a path such as /pricing/ or a full address. Leave it empty to check the home page. Click “Check this visit”.

The result is either “All clear. This visit would be counted.” or “This visit would not be counted:” followed by a list. Only administrators can run it, and nothing about you is stored.

What it checks

The check runs your browser through the same rules the tracker and collector use.

  • Role: you’re logged in with an excluded role, listed under Settings, General. Excluded users and capabilities are checked here too. See Exclusion fields.
  • IP address: your address is on the excluded IP list.
  • Do Not Track and Global Privacy Control: your browser sends either signal, and Vireo honours both.
  • Consent: your site waits for consent before counting, and the visit counts once the visitor accepts statistics cookies.
  • Bot filter: your browser looks like a bot, so its visits are counted as bot traffic. The result links to the bot filter test.
  • Path: the page matches an excluded path.
  • Country: your country is on the excluded countries list.
  • Code on the site: a developer has turned the tracker off with the vireo_load_tracking_script filter.

The page and the collector

Vireo also loads the page you named, as a logged-out visitor would see it, and looks for the tracker. This catches problems that no setting causes.

  • The page can’t be loaded from the server. A firewall or a login wall in front of the site can cause that.
  • The page returns a 404, and pages that aren’t found aren’t counted as visits.
  • The tracker isn’t in the page. Clear your caching plugin’s cache first. If it’s still missing, the theme may be missing wp_footer(), which pages need to print the tracker. A theme template can call do_action( 'vireo_print_tracking_script' ) instead.
  • The tracker is there, but an optimisation plugin holds it back until the visitor interacts, so people who read and leave aren’t counted. Exclude the Vireo tracker from delayed JavaScript in that plugin.
  • The collector doesn’t answer a test request. If the direct endpoint fails, Vireo switches to the slower admin-ajax route until the next recheck. If admin-ajax fails, a firewall or security plugin may be blocking admin-ajax.php.

Reading the result

Each reason names the setting to change. When several apply, fix the first and run the check again.

Because you’re logged in, the check often finds your role first. That’s the intended behaviour for administrators, who aren’t counted by default. To see how a reader’s visit is treated, open the page in a private window, or use Excluding traffic to review the rules that apply to everyone.

Updated 7 November 2026. Something wrong or missing? Tell us.