Observed technologies
The scan reports detected technologies, cookies, third-party trackers and representative requests from the pages it could reach.
For EU-facing SaaS teams
Verify Consent Mode, script blocking and consent evidence
Check the complete technical chain: denied defaults, scripts before choice, preference updates and the evidence retained for review.
No account required · No card required
Product proof
Your live scan result appears here — never a simulated dashboard
Before-choice activity
Review the count of technologies that loaded before a visitor choice, plus the available banner and consent-signal checks.
Clear next step
Use the live result to decide whether to fix the configuration, recheck a representative journey or request technical review.
The challenge
A consent signal alone does not block a script
Consent Mode, the consent interface and your tag controls have separate roles. A reviewable setup links denied defaults to observed script behaviour, updates signals after a choice and keeps proportionate evidence of the configuration context.
The workflow
Verify the complete technical chain
Start with the default state
Check which technologies and consent signals are present before the visitor chooses.
Connect choices to behaviour
Verify how script controls and supported consent signals change after a visitor choice.
Keep reviewable evidence
Retain proportionate, pseudonymous evidence of the choice and configuration context.
What you get after the scan
- Observed technologies and requests, including what loaded before a choice.
- Available checks for the consent banner and Consent Mode signals.
- A next step to fix, recheck or request review of the full technical chain.
Questions before you start
Does Google Consent Mode replace a CMP?
No. It communicates consent signals to supported Google tags; it does not collect a visitor choice or replace your consent interface.
Does Consent Mode itself block scripts?
No. Script blocking must be configured separately where it is required.
Can we test tags loaded through GTM?
The scan can report observed browser activity. GTM triggers and consent settings should also be reviewed against the intended setup.
Can we scan both a marketing site and a web app?
Start with public, representative URLs. Authenticated or session-specific paths may need a separate review.
Do consent records contain visitor identities?
Consentory uses a pseudonymous visitor reference and stores the selected purposes and configuration context, not a visitor identity.
Free technical scan
Verify the complete consent chain
Check the default state, visitor-choice outcomes and the evidence your team can review.