Do ad blockers block cookieless analytics?

Short answer: sometimes. Ad and tracker blockers decide by address, not by what a script does. If a blocklist includes an analytics domain, requests to it are blocked whether or not the tool uses cookies.

Who uses blockers

Use varies a lot by audience. Technical audiences (developers, IT, gaming) block much more than a general public browsing on phones. Some browsers block known trackers by default. For a site aimed at developers, a noticeable share of visitors may never reach any analytics tool; for a local shop, very few.

Why cookieless tools are blocked less, not never

Blocklists focus on advertising and cross-site tracking. Tools that do neither are added later, or not at all, but nothing guarantees it, and lists change.

How to avoid it: your own domain

Serve the script and its requests from your own domain, for example example.com/sd/js/script.js, and forward them to Statsdot. To a blocker, that is a request to your own site. Ready configurations for Nginx, Cloudflare Workers, Next.js and Netlify are in Serve the script from your own domain.

This is not a way around anyone's choice. Statsdot sets no cookies, stores nothing on the device and keeps no personal data; visitors who want to exclude themselves from any counting can still do it with their browser's settings.

How to estimate what you miss

Compare a number you know from elsewhere, such as orders or sign-ups, with the visitors who reached your thank-you page. A large gap on a technical audience is often blocking.