Matomo · cookieless web analytics · GDPR-compliant
Reliable numbers without a cookie banner — and without Google behind it.
Matomo gives you web analytics where the data belongs to you: on your server, without data transfer to the USA, entirely without cookies if you want. I set it up cleanly — as someone who measures their own website exactly that way.
Why so many analytics setups are a problem
Either you measure legally,
or you measure anything at all — rarely both.
Google Analytics has been under data-protection pressure since Schrems II, the cookie banner scares off a share of your visitors, and what's left is patchy numbers. It can be done differently — with analytics that does not play data protection against meaningfulness.
Legal risk: Google Analytics transfers data to the USA — grounds for a warning notice, a recurring topic with supervisory authorities. Banner loss: anyone who clicks "reject" doesn't appear in your numbers at all. Flying blind: in the end you make decisions on the basis of data you can't trust.
Matomo, cleanly set up — not just activated.
Anyone can switch on an analytics plugin. The difference lies in the configuration: cookieless, anonymised, legally justifiable, technically stable.
Matomo set up the way data protection requires.
Self-hosted on a server in Germany or in the Matomo Cloud — with IP anonymisation, cookieless measurement and clean goal tracking. Set up, not just installed.
SwitchoverAway from Google Analytics, without a data break.
I switch your measurement over, set up the important evaluations afresh and secure whatever of the old data is worth saving — with a test run before GA goes off.
Without a bannerMeasure cookielessly — in many cases without consent.
Configured correctly, Matomo measures anonymously enough that a cookie banner is often not needed. More visible visitors, less click frustration — and a configuration you can justify.
The proofThis website measures exactly that way — see for yourself.
My own reach measurement runs cookielessly, with a shortened IP and without external tracking. I recommend nothing I don't run myself. It's all in my privacy policy.
Advice from someone who does it themselves.
I am an IT specialist and I run servers — Matomo is not a foreign plugin to me, it's a craft. But above all I measure this website cookielessly myself: anonymised reach measurement without cookies, without Google, without user data leaving the building. What I recommend to you, I have tried on my own business.
Data protection is not a fig leaf with me, but a stance — evidenced in the open verification record and in the privacy policy, not merely claimed.
I am an independent consultant, not a Matomo-certified partner — and I tell you that openly. My recommendation follows your needs, not a commission. If another tool fits better, I say that too.
Frequently asked questions
What people ask before switching analytics.
Why Matomo instead of Google Analytics?
Because you keep data sovereignty: a server in Germany or entirely on your own systems, cookieless measurement possible, no data transfer to the USA. That defuses the legal problems Google Analytics has carried since Schrems II — with the numbers you need.
Do I still need a cookie banner then?
Often not. Configured correctly, Matomo measures cookielessly and anonymised, so in many cases no consent is needed. Whether that holds in your case we clarify concretely — I promise no blanket banner-freedom, but a justifiable setup.
Can you take over my GA data?
I switch the operation over cleanly, so that from the switchover on measurement is correct. Historical GA data can be secured within limits; what is possible and what makes sense, I tell you in advance.
Self-hosted or cloud?
Both. Self-hosted keeps all data in-house — my recommendation when data sovereignty matters. The cloud is quicker to get going. I set up both and tell you what fits.
What makes you credible?
I run cookieless analytics myself — this website measures without cookies, with a shortened IP, without external tracking. As an IT specialist I set Matomo up cleanly, instead of just activating a plugin.
Tell me what you want to measure — and what data protection requires.
Free initial call · cookieless where possible · honest where the limits are
