Evidence of what your tags did in each consent state. ConsentMark is an independent analytics governance service for regulated organisations across the EU, the EEA and the UK. We have no stake in the answer.
Scanning
Opening your site in a real browser Recording the tags, cookies and requests it loads Working the banner - untouched, accepted, then rejected Scoring the evidence and issuing the grade An example result The result below is a worked example on a demonstration domain, and it is not a scan of a real site.
Some tracking before consent, but in restricted mode
• Tags fire before consent is granted • Google Consent Mode v2 is functional • Meta Pixel fires after consent rejection The scan recorded 5 tags across the consent states it covers. A real result names each one and links the evidence behind it.
Retention We use your email to send you the report. A scan result is deleted after thirteen months, and your email is deleted with it.
Nightly Record A scan is one page on one date. ConsentMark Monitor checks your pages every night against the tags you have approved, and signs each night's verdict.
Dated Result Every result carries its date and the methodology version it was scored under, and names the finding behind each mark.
What this report covers
An independent observation of what your site shipped to the browser at scan time, with the consent state at fire, captured as a timestamped evidence record.
The limits of a scan
It is not a substitute for your DPIA, your processing register, or your supervisory authority's assessment. Scans grade what your tags did under each consent state against one standard, consent before non-essential storage and transmission, which rests on the GDPR and the ePrivacy Directive in the EU and the EEA and on the UK GDPR and PECR in the United Kingdom. Newer UK exceptions for some purposes are not reflected in the grade, and a grade is not a finding that any law was breached. Findings do not evaluate regimes such as the CCPA or the LGPD. Controllers remain accountable under Article 5(2) GDPR.
