If you're building a business around tracking people, then you should expect adblockers will block the domain with the tracker on it. You should treat it like an ephemeral domain and anticipate you'll need to rotate it at some point if you're playing cat-and-mouse with the ad blockers. If you don't want your landing page blocked too, then don't put it on the same domain.

Better yet, shut down the business and work on building something that's a positive contribution to society.

Exactly, I am curious if they were providing the script directly from domain of the main website, and that probably would be an issue.

> What he replied is that he couldn't block the script alone if he was serving it from the same domain, so I proposed to move it to a subdomain, and he was fine with that.

Seems like the way it should work, no?

But think of falcon_ and his hustled HN front-page ad.

Indeed. This should be flagged out of the front page.

Yeah, ad-blockers tend to err on the side of false positiveness; by blocking the domain, they make sure that they block the ads. Given that your business is about, well, analytics, it seems that the best you can do is be creative about circumventing them.

At first I thought you had another kind of business. But, as an analytics provider, it's unsurprising that you're prone to being targeted by ad-blockers. It sucks though. After all, ad-blockers do not care whether you are privacy friendly or not (look at Plausible for starters).

Anyways, keep us posted in how you solve this and good luck!

> ad-blockers do not care whether you are privacy friendly or not

Analytics are inherently not privacy-friendly.

Tracking domain needs to be on a separate domain to your website and interfaces.

If this isn’t possible, then at least load the website assets (images, css , JavaScript etc) on a different domain.

It's the list maintainers that you'd need to contact, not the ublock people who just consume those lists.

When I load your page, I get a red bar at the bottom:

> This site requires JavaScript to run correctly. Please turn on JavaScript or unblock scripts

The statement about javascript is false as demonstrated by the fact that I can read the whole article.

I think this is why most trackers use obscure domain names to load their tracking scripts from and I presume will periodically change them. Would definitely be nice to be able to challenge the blacklisting though.

After a few months working on MetricsWave, I recently discovered that some blacklisting lists are including my site domain, not the tracking script, but my landing page domain.

> What he replied is that he couldn't block the script alone if he was serving it from the same domain, so I proposed to move it to a subdomain, and he was fine with that. I have been lucky.

Doubly so, since hosting the tracking script on the same domain as your website was a decision that was inevitably going to come back to haunt you at some point.