Analytics without Consent Check
Check if a URL contains more frugal analytics candidates or marketing/tracking signals requiring consent.
Ideal for preliminary examination of Matomo/Plausible/Fathom setups and differentiation to marketing tracking.
Results
Technical pre-checking of a URL. For multiple URLs, templates and CSV exports, use the GDPR Tracking Audit.
Findings
Detailed hit
What the Analytics without Consent Check evaluated
The exam is deliberately fast and focused. It recognizes technical signals in headers, HTML, JavaScript and resources. Interactions with banners, login, forms and tag triggers should be additionally checked in the browser.
Recognize analytics integration, check consent flow
Illustrative example · no measurement result of your website
Analytics signature in HTML + no recognizable consent pattern = reason for verification, no evidence of breach.The check links recognizable analytics services with technical consent notices. A found analytics signature can indicate an integration; it does not yet prove a measurement event before a decision.
Then check the results in the browser.
- First, determine the detected Analytics service and its associated configuration.
- Compare requests and memory in a fresh browser before selection, after rejection, and after consent.
- Document the scope of data, triggers and purpose. Let open legal issues be assessed on the basis of this actual process.
What this check leaves open
Whether consent is required, this tool does not decide. Missing consent signatures can result from dynamic configuration; existing signatures do not prove correct implementation.
Take a closer look at Google Consent signals →From individual check to GDPR tracking audit
A tool shows a concrete symptom. The audit checks up to 500 URLs, prioritizes tracking, consent and form risks, and provides export data.
Targeted deepening of GDPR tracking
Check which cookies a URL technically shows, whether tracking cookie candidates appear and which attributes such as Secure, HttpOnly or SameSite are set.
Before consentRecognize tracking and third-party candidates who are already visible in the initial delivered page before a user actively consents.
Third party third partiesFind well-known tracking services, external script hosts, and third-party integrations that are relevant to consent, privacy, and tag governance.
Google Consent ModeCheck if Google tags have technical consent mode signals visible and if denied/granted hints appear in the code.
Storage & FingerprintingRecognize technical storage and access signals such as cookies, LocalStorage, SessionStorage, IndexedDB and fingerprinting candidates.
Consent UXCheck whether known consent management platforms and important banner signals such as rejection, settings and revocation are technically findable.
Questions about Analytics without Consent Check
Does the tool give legal clearance?
No. It's just a technical pre-test. Consent-free analytics depends on narrow configuration, purpose limitation and documentation.
Why Are Marketing Tags Considered?
Marketing, heatmap and CRM tags regularly speak against a simple consent-free analytics classification.
Is the individual check free of charge?
Yes. The standalone tools check a single URL. For larger crawls, complete tables and CSV export, the premium audit is planned.
Does the tool replace legal advice?
No. The tools provide technical pre-testing. Legal bases, contracts, information obligations and concrete consent flows must be subject to technical review.