Core concepts · 4 min read
What Consent Guard AI scans for
A look at what a scan checks — trackers, banner behavior, disclosures, and consent logging.
The scan in plain terms
A scan loads your site the way a real visitor’s browser would, watches what fires, and reports back. It is how your compliance score and issue list are generated.
What we look at
- Trackers and pixels — which ones load, and whether they fire before consent.
- Banner behavior — whether a clear opt-in/opt-out choice is presented.
- Script blocking — whether non-essential scripts are held until consent.
- Disclosures — whether privacy and cookie information is reachable.
- Consent logging — whether visitor choices are being recorded.
How often to scan
Scan after any change to your marketing stack, and periodically as a health check. New embeds, ad tags, and third-party widgets are the most common way a compliant site quietly slips out of compliance.
Tip
Run a fresh scan right after launching a campaign — that is when new pixels tend to appear.
Keep reading
Still have a question?
Contact support →