Script and tracker control
The bootstrap can pause known optional loader URLs. It is not a promise that every unknown tracker on the internet is blocked.
Enforcement
Consent enforcement for the choices you record
Consent enforcement is how a recorded allow or deny reaches the tags, cookies, and scripts that would otherwise run on their own.
What is consent enforcement?
Consent enforcement means applying the current consent record to the technologies you have mapped, so optional scripts and trackers wait on the purposes the person allowed. It covers what the SDK can see and what you configured. It cannot undo a request that already left the browser.
A stored choice that never reaches the tag is only a log
Teams often collect a banner click and leave the tag manager unchanged. The person refused advertising, and the advertising tag still loaded. Enforcement is the step that connects those two facts.
Consent Guru’s SDK can pause known optional script URLs when the mapped purpose is denied, and it can update Google consent signals when Consent Mode is enabled for that website. Tags already inside a container, or injected before the SDK runs, still need their own checks.
How enforcement runs on a page
Step 1
Map
Classify cookies, scripts, and vendors against purposes. Unmapped tags are a review list, not a silent allow.
Step 2
Default
Optional purposes stay off until there is a recorded choice, when that is the experience you published.
Step 3
Apply
After the person chooses, the SDK follows the record: allowed purposes can load, denied purposes stay paused.
Step 4
Update
A later withdrawal changes the current record. Enforcement follows the update. It does not rewrite the evidence of the earlier choice.
Key capabilities
Consent-aware tags
Google Consent Mode, when you enable it, maps purposes to signals such as analytics_storage and ad_storage.
Consent enforcement API
Your backend can read the same choice through an API key and apply it in systems the browser SDK never sees.
Scanner as a review aid
Discovery lists cookies and script patterns. It does not recategorize production tags without a published policy.
What teams use it for
- Fewer optional tags firing before a choice.
- One purpose model for the banner and the tag decision.
- A server-side path when the browser is not the system of record.
- A clear limit: enforcement follows configuration, not an invisible guarantee.
Marketing sites
Hold analytics and advertising loaders until the matching purpose is allowed.
Tag managers
Pause the loader URL you know about, and keep consent checks inside the container for tags that are already there.
Logged-in products
Read the record from the API and gate server-side processing the same way.
Privacy considerations
Enforcement does not decide whether you needed consent in the first place. It applies the model you configured.
A tag that runs from a domain you did not map, or that fired before the SDK, is outside what this control can retract.
Technical capabilities
Early blocking
The embed runs a blocking bootstrap so mapped optional scripts can wait. Requests that already left the browser stay sent.
Webhooks
Signed webhooks can tell your systems that a choice changed, so warehouses and apps are not left on the previous state.
Questions
1.Does consent enforcement block every cookie?
No. It applies the purposes you published to the scripts and cookies you mapped. Strictly necessary technologies that you have marked as required are not treated as optional. Unknown tags still need a review.
2.What is consent-based tracking?
It means measurement or advertising tags run only when the purpose they are mapped to has been allowed. The mapping is yours to configure and to keep current.
3.Can enforcement replace a privacy review?
No. It is a control in the browser and, through the API, in your systems. Contracts, notices, and the choice of lawful ground remain separate work.
Related pages
- Cookie consent managementDiscover cookies and map them to purposes.
- Google Consent ModePurpose-to-signal mapping for Google tags.
- Consent recordsThe decision enforcement is applying.
- Consent SDKInstall the script that performs browser enforcement.
- Consent APIRead the same choice from your backend.
This page describes how Consent Guru supports privacy operations. It is not legal advice, and using the product does not by itself make an organization compliant with GDPR, CCPA, CPRA, the DPDP Act, or any other law.