Browsing site with VPN gets events dropped about analytics HOT 7 CLOSED

Thanks for the report @raulrpearson. I agree that VPN users should be counted and this is being worked on: #3766

We'll create a special country entry for VPN users since the actual location of the visitor is unknown.

from analytics.

this is now done! visitors that use VPNs are now grouped under the "Anonymous VPN Service" entry in the Countries report

from analytics.

See the Bot Filtering section in the README: https://github.com/plausible/analytics?tab=readme-ov-file#can-plausible-analytics-be-self-hosted

Advanced bot filtering for more accurate stats. Our algorithm detects and excludes non-human traffic patterns. We also exclude known bots by the User-Agent header and filter out traffic from data centers and referrer spam domains.

Since VPNs use data centers for their proxying, you get dropped as bot.

from analytics.

Thanks, @Le0Developer, my point is that real users sometimes use VPNs and categorizing those as bots leads to less accurate stats, specially as VPNs become more popular. Maybe better heuristics can be developed.

from analytics.

Hello @metmarkosaric @ukutaht

Just checking, would all the custom scripts be updated to catch VPN users?

We're using the combination https://plausible.io/js/script.manual.local.js which we proxy, but we seem to drop them as well, unless there's something we'd need to do when doing the manual scripting?

Thanks!

from analytics.

@antoinemacia hey! yes, all of our script extensions are covered by this.

If you have a proxy, you should make sure to set the value of X-Forwarded-For header with the actual user's IP address. See the events API page for more information on header requirements and for debugging https://plausible.io/docs/events-api#request-headers

from analytics.

OK great, re header we're just following this so we should be good, it must be something else..

from analytics.