Do ad blockers block TapCub?

The short answer

Yes, some can. Ad blockers and privacy extensions use lists of hosts and script names to block, and some of those lists include analytics services. When a visitor's blocker drops the TapCub script or its requests, that visit is not counted. TapCub does not try to get around blockers.

Browser settings matter too. When a visitor turns on Do Not Track or Global Privacy Control, the TapCub script stops before sending anything, unless you have set data-respect-dnt="false" on the script tag. Whether that is appropriate for your site is a decision for you and your legal advice.

What a blocked visit looks like

• Your own visit never appears in Realtime while a different browser or a private window works.
• The network panel shows no request to the TapCub hosts at all. When a request is blocked by the browser, there is nothing to see; the collector never received it.

To test your install, use a browser without privacy extensions. See check that data is arriving.

How big is the gap?

It depends on your audience: technical and privacy-minded audiences block more. To estimate it, compare a number you record on your server with the same number in analytics over a few weeks, for example sign-ups or orders. The difference is a rough upper bound on what blockers, closed tabs and declined consent hide.

Keeping key numbers complete

Send the conversions that matter, such as orders or sign-ups, as server-side events. They are recorded whatever the browser does. Pageviews and browsing behaviour still come from the script, so treat those as a large sample of real visits rather than a complete count. Server events are covered in the developer docs.