문서
문서 둘러보기

Ad blockers and analytics

How ad blockers and privacy browsers affect analytics, how to check whether the tracker is blocked, and what you can do about it.

Markdown으로 보기

Some content blockers and privacy browsers block analytics scripts by domain or file name, including privacy-friendly ones. How many visitors that affects depends on your audience: technical audiences block more.

Blocked visitors aren't counted, so your numbers may be somewhat lower than the real traffic. Treat the dashboard as a slight undercount and compare trends over time rather than exact totals across tools.

What you can do#

  • Expect some undercounting. The tracker loads only from privatusstats.com, and we don't offer ways around blockers. Visitors who block analytics are simply not counted.
  • Nothing else goes with it. The tracker has a domain of its own, so a blocker that stops it doesn't stop your testimonial widgets, forms or status pages (on privatus.page) or your dashboard. See Our domains.
  • Don't try to hide the script (random paths, renamed files or forwarding it through your own server). We don't support that: respecting people who deliberately block analytics is part of the deal. They can also opt out directly.

Checking whether you're blocked#

With a blocker, the Network tab shows pa.js or /api/event as blocked (ERR_BLOCKED_BY_CLIENT in Chrome). Test in a private window without extensions to confirm tracking works.