Not necessarily. If I read the article correctly, it is about sending data to the US:
> The complaints allege that the companies, in violation of the law, transfer personal data to the United States.
So if the 3rd party is inside the EU, you might be fine. Or at least you may run into different GDPR issues.
IFF you have access to your logs.
What I'd be curious to see is the ROI on these tools. They obviously work in some cases, but do they always work? We currently employ three business intelligence developers, and two developers who actually build products. What's the most hilarious about it, however, is that despite employing three BI's I can't tell you if they earn their keep, because their data doesn't show that.
I sometimes check access logs and pipe some grep queries into a line counter, or uniq by IP address to have a rough idea of how many people look at a particular part of, or tool on, my website. Maybe twice a year or so. Helps prioritise which things are worth maintaining/updating based on what's still being read (found by search engine or linked from third parties)
It's more then enough for me.
And a few clients whom I enabled it for, told me they very much liked the simplicity. Less data as a feature!
I found a bad bug in their JS which means that on some pages it just silently fails and doesn't log anything, which means your analytics are even more inaccurate than ever (given the browser restrictions). I was totally broke and I wanted to use their paid service for a few months, so I offered them the fix in exchange for a few months free service (maybe $30 credit?). They told me basically "don't worry, we'll find the bug ourselves one day, we don't need your help."
But I've been in one, where a customer offered "patches", despite our software not being open for contributions. Not only were they inconsistent with our standards, they were hard to read and had some subtle security issues on careful review. I'm still suspecting it was an attempt to plant a backdoor.
In any case, even if legit, it was a lot of work on our side to just review and clean it. Far more than if we just did it ourselves.
This is different for OSS, which should have external contributions as main workflow. Ours wasn't prepared for external contributions.
Maybe the same is with Plausible?
Tracking events is actually useful to see which features are used etc.
It's not all marketing and evil ads.
Having said that, GA4 is awful as a casual user.
I think for most use cases users would want to know if their content is consumed/read. Maybe how long someone spends on it and where they came from. For this sort of stuff you can write a small script to parse your logs. I did something along these lines to parse Caddy logs to get some idea of how many people visit a link. That's really all I needed and the great part is that I run it whenever I want an update, so it's not consuming resources constantly. The logs are cleared and the output is saved before logs are cleared so I know Article 1 had 39 views (or less!) and Article 2 had 5 views and so on...
So I think we're overdoing it and we would benefit from taking a few minutes before going down the rabbit hole of analyzing EVERYTHING.