Consent collection
A GDPR cookie consent banner you can actually verify
Give visitors a clear choice, keep optional technology off until the right permission exists, and retain a reviewable record of what they chose.
For EU-facing sites replacing a cosmetic banner or reviewing an existing CMP.
01 / The problem
A banner can look right while trackers still run
A visitor sees buttons, but a GTM tag, embedded video or marketing pixel may already have loaded. A banner is only one part of consent management: the choice has to reach the scripts, stay consistent across pages and remain changeable.
Signs the setup needs a closer look
- Optional requests appear before any choice
- Reject and accept produce the same network traffic
- A saved preference is hard to find or change
02 / What Consentory does
One workflow for the choice, controls and evidence
Consentory connects the visitor interface with purpose-level controls, a preference centre and pseudonymous consent records. Your team still decides the correct purposes, vendors and regional rules.
Granular visitor choice
Present distinct purposes, offer reject and accept paths, and let visitors revisit preferences.
Prior blocking
Hold optional scripts and embeds until the relevant purpose is allowed, including vendors outside Google's tag ecosystem.
Reviewable records
Keep the selected purposes and configuration context so a later technical review has a traceable starting point.
03 / Technical implementation
How the banner becomes an enforceable choice
Start with a real inventory, then connect each purpose to a specific execution rule.
- 01
Scan representative pages
Find cookies, pixels, iframes and requests that appear on the journeys visitors actually use.
- 02
Classify by purpose
Review each technology with the site owner and decide whether it is necessary or optional.
- 03
Publish the banner and controls
Configure choices, install the widget early, and block optional technologies before their first request.
- 04
Test and revisit
Compare fresh, rejected, accepted and withdrawn states after every material tag or site change.
04 / Evidence and verification
Evidence your team can inspect
Use browser traces alongside the configuration. A legal conclusion requires your own policy review.
- Fresh visit
- Optional technology remains inactive before a visitor chooses.
- Reject and granular choice
- Only technologies for allowed purposes activate; reject does not act like accept.
- Preference change
- The saved choice and future requests reflect the new state.
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
Review the banner on your own site
Tell us which site and region you want to assess. We will help define a practical beta scope and the first technical checks.