> I installed Google Analytics alongside Plausible Analytics on three sites in June.
All he measured was people who load Plausible Analytics and not Google Analytics. Anybody running noscript (like me) wouldn't have shown up here at all.
So yeah, I would expect the true Google Analytics blockage figure to be markedly higher than the 13% reported here.
I found that it was only added to _Peter Lowe's_ list yesterday/today, so it wouldn't have affected the statistics for this blogpost
https://pgl.yoyo.org/adservers/serverlist.php?showintro=1&st...
For the record, you can also view exact timestamps on the detail page: https://pgl.yoyo.org/adservers/details.php?hostname=plausibl...
If you run some kind of proxy yourself on an unconventional name (e.g. “ads.mysite.example” may well be blocked) and make sure that any script it needs loads from your own site, again with an unconventional name (e.g. “piwik.js” would be blocked as Matomo), then your tracker won’t be blocked until someone notices.
If you want to head far down this route, smuggle analytics data in with legitimate requests and separate and forward it on your server.
Fortunately, taking it to this extreme takes enough effort that it’s decidedly uncommon.
The site of the article cloaks `custom.plausible.io` as `ms.markosaric.com`.
<noscript><img src=//tracker.example/pixel.gif style=position:absolute></noscript>
Some of Google’s tracking things include (or used to include?) such a snippet. But broadly the technique has fallen into disuse. I don’t see Plausible advertising any way for it to work, and their main snippet POSTs to https://plausible.io/api/event, which an image won’t be able to achieve.