Technical controls
Cookie scanner and prior blocking in one workflow
Evaluate cookie scanning and prior blocking through the Consentory private beta. Review observed technologies, classify their purposes and verify how your site responds to visitor choices.
For teams that need to move from cookie inventory to enforceable controls.
01 / The problem
A cookie list does not stop a tracker
Scans surface technologies and requests, but they do not by themselves change execution. Tags can also appear only on a product page, behind a campaign link or after a user action. Prior blocking needs both an inventory and a tested rule for each optional technology.
Signs the setup needs a closer look
- A scan identifies vendors but the network trace stays the same
- A script fires before the banner is ready
- A blocked tag never starts after permission
02 / What Consentory does
Connect discovery, control and verification
Consentory combines representative scans with technology classification and consent-aware blocking. Test both the denied first visit and the granted path so privacy controls do not silently break measurement.
Representative scans
Inspect public pages and browser-observed technologies, including requests that appear before a choice.
Purpose-level blocking
Hold optional scripts or embeds until the relevant visitor choice is available.
Recheck after change
Compare fresh, rejected and accepted states to confirm the rule works in production-like conditions.
03 / Technical implementation
From finding to fixed behavior
Request beta access with your public website URL. Together we confirm the pages, available scan limits and access before scanning; your site owner reviews the findings and approves blocking changes.
- 01
Capture a baseline
Scan landing, product and conversion journeys with a clean browser state.
- 02
Review the inventory
Classify each observed technology and investigate unknown or first-party proxy requests.
- 03
Configure blocking
Install controls before optional scripts execute; include direct embeds and tags outside GTM.
- 04
Retest both outcomes
Confirm no optional request before permission and normal behavior after the relevant grant.
04 / Evidence and verification
The pass conditions are observable
Keep the request trace with the scan result; neither alone tells the full story.
- Fresh visitor
- Optional scripts and requests are absent before the relevant permission.
- Allowed purpose
- The expected technology starts once, without duplicate measurement.
- Changed preference
- Future activity follows withdrawal or a more granular choice.
Keep exploring
Technical guides
Use these guides to check the details before you request access.
Related solutions
Choose the next question
Each page focuses on a different implementation decision.
05 / Request access
See what happens before a visitor chooses
Submit your public website URL in the beta request. We review scope and access before a scan is arranged. Findings inform your site owner’s classification and blocking decisions.
Scanner access is reviewed during private beta. This page does not run an instant scan or generate a report when you enter a URL. Browser observations cover only the pages and states tested.