Checks representative pages
It scans the homepage and different page types, recording cookies, storage, scripts, iframes and network requests.
ShapeConsent · consent and cookie management
ShapeConsent detects services that use data, connects them to a clear visitor choice and keeps a verifiable record of the decision.
The banner is only the beginning. Scanning, the service register, external-content blocking and consent records work as one system within the Shape platform.
One process instead of disconnected tools
The system connects what is actually found on the store with what visitors see and can choose.
It scans the homepage and different page types, recording cookies, storage, scripts, iframes and network requests.
ShapeConsent can automatically add services that unambiguously match a previously reviewed catalogue. Unknown and ambiguous findings are flagged for administrator review. Optional services still require the appropriate visitor consent.
Registered services load according to the selected category or service, and withdrawing consent immediately changes the allowed state.
Storefront controls
Visitors get clear controls, while the store uses the same published register to decide which services may run.
Accept, reject and detailed choices are available with no optional category enabled in advance. Settings can be reopened from the footer.
The Google integration mode is selected for each store. Service-specific rules and the visitor's choice still determine what may be sent.
Known content appears only after the required consent. An unknown embed remains replaced by a safe placeholder until review.
A verifiable decision trail
ShapeConsent stores pseudonymised history under a random ID for the browser and domain. The ID is not linked to a customer account or analytics identifier.
Automated monitoring
Alongside periodic scanning, ShapeConsent records blocked unknown content during real visits. An administrator can review these findings and link them to the register.
Automation is enabled after the initial analysis. Its schedule requires an active Shape cron runner on the project.
Example of a record awaiting review
From setup to maintenance
Initial technical preparation, active consent controls and periodic monitoring form three clear steps. Commercial scope and pricing are agreed for each project.
A review of existing tracking, representative pages and external services, followed by a draft register for confirmation.
ONE-OFF PREPARATIONA local CMP, published register, service controls, public cookie table and administrative consent records.
SYSTEM FOUNDATIONPeriodic scanning, continued crawling and findings for new or changed services, ready for administrative review.
ADDITIONAL SERVICEHow do we start?
We review existing scripts, storage, iframes and network requests on selected pages.
We connect services to categories, purposes, providers and technical loading rules.
In a browser, we verify the state before a decision, acceptance, rejection, partial choices and withdrawal.
When agreed, we enable automation that detects new findings and leaves them ready for review.
Before setup
Review the real state
We begin with a technical review and a clear list of what was found. We then agree what needs to be enabled, blocked and disclosed.