This translation has not been editorially reviewed yet. The German version is authoritative. Deutsche Fassung →
Tracker connections before consent: the IP alone is enough
The check captures every connection to third-party servers that happens before any consent. What matters: the request alone already transmits the visitor's IP address, and usually also which page they're currently viewing — no cookie is needed for that.
- This is the point many consent solutions miss: they block cookies from being set, but not the file from loading. The connection happens anyway, and the transmission has taken place.
- A complete inventory of third-party hosts is captured, sorted by type — trackers, tag managers, fonts, maps, videos, social networks, captchas, delivery networks. That makes it clear what's embedded at all.
- A tag manager is a special case here: it doesn't measure anything itself, but loads everything configured in it. What it triggers is only visible at runtime.
FAQ
Is a connection with no cookie already a problem?
Yes. IP address, the page requested, and technical browser details all get transmitted. That's a transmission of personal data, regardless of whether a cookie gets set.
What about delivery networks for libraries?
They're listed separately. A connection to a third party arises there too — the clean solution is to serve such files from your own server.