Which trackers load
before consent?
Enter a URL — we fetch the page server-side (like a first visit without any cookie banner clicked) and check which analytics, ad and embed trackers are wired into the HTML. Result in seconds, no signup.
Trackers without consent — what the check detects
The check loads your page exactly as a visitor sees it on the very first visit — before any cookie banner has been answered — and logs which trackers, analytics scripts and third-party services already load at that moment: Google Analytics, Meta Pixel, TikTok, Hotjar, YouTube embeds and more.
That exact moment is GDPR-critical: services requiring consent may only load after active opt-in. Trackers firing before that are the most common cause of cease-and-desist letters on the web — with fines as a real risk. A cookie banner alone is not enough if the scripts technically run anyway.
If the check finds trackers before consent, the fix is usually: wire up consent management correctly (actually block scripts, not just hide them) or switch to privacy-friendly alternatives. Both are very solvable — the important part is knowing about it.
Frequently asked questions
My banner asks for consent — isn't that enough?
Only if the scripts are technically blocked before opt-in. Many banners are purely visual: they ask, but the trackers have long loaded. That is exactly what the check makes visible.
Which services don't need consent?
Technically necessary services (e.g. session cookies, load balancing) and — by common interpretation — cookieless, anonymized statistics. Anything with profiling or third-country transfer needs consent.
Is the result legal advice?
No — it's a technical inventory. But it shows you precisely which services load before consent, i.e. the items you should have legally assessed.