Consent choices,
enforced
Recording a choice is the easy part. Clickio Consent makes the whole page obey it: the Google ad stack pauses and resumes automatically, standards-aware tags follow Consent Mode v2, and everything else is gated with one attribute or a GTM trigger.
Trusted by 2,000+clients worldwide
A banner that only records consent isn't compliance
If declined tags keep firing, the choice changed nothing. But the usual fixes create their own problems.
Recorded, not enforced
Many setups show a dialog, store the choice… and change nothing about what actually runs. Regulators, plugins and privacy tools can all see the gap.
Blunt blockers break sites
Generic "auto-blockers" that rewrite every script guess at what's safe. Guess wrong and tags run at the wrong time or essential embeds break.
Custom logic everywhere
Hand-writing consent checks around every pixel and partner script turns compliance into a permanent engineering project, one that breaks each time marketing adds a tag.
Three layers. Every tag covered.
Clickio matches the enforcement mechanism to the tag: automation where it's safe, explicit control where it's needed.
The Google ad stack
- Ad Manager and AdSense requests are paused before the visitor chooses and resumed the moment consent resolves. Declined personalization switches ads to non-personalized mode.
- Zero setup: no changes to your ad implementation, with a per-site opt-out if you prefer to manage it yourself.
Tags that understand consent signals
- IAB TCF 2.4 and GPP for the advertising ecosystem, plus Google Consent Mode v2 end to end: denied by default, updated on every choice, replayed for returning visitors. Microsoft UET gets the same treatment.
- Any tag that honors these standards (GA4, Google Ads, Floodlight, Bing) is governed with no per-tag work.
Everything else
- Mark any script
type="text/clickiocmp"and declare when it may run withdata-clickio-cmp-*attributes: TCF purposes or vendors, custom purposes, US privacy state, even paywall status. - Prefer no code? The CMP pushes consent events and variables to the dataLayer for per-purpose GTM triggers, and a JS API is there for custom logic.
<!-- runs only for visitors who consented to the declared purposes -->
<script type="text/clickiocmp" async
data-clickio-cmp-purpose-consent="1,3"
src="https://partner.example.com/pixel.js"></script>
Discovery and enforcement, connected
Orchestration is only as good as your vendor list, so Clickio builds it for you.
- The Cookie Scanner finds the vendors actually present on your site and can add missing ones in one click; non-TCF vendors are created with the right Consent Mode category mapping automatically
- In the vendor list, every non-TCF vendor is labeled by integration type: automatic when it supports Consent Mode, manual when it needs an attribute or a GTM trigger, so you always know what's covered and what needs a decision
- Discover: the scanner maps your real vendors and cookies
- Enforce: orchestration holds every tag to the visitor's choice
- Disclose: the dialog and your policy page show it, always current
- Record: consent records show which choice each visitor made and when
Frequently asked questions
Do I need to change my Google tags?
No. Ad Manager and AdSense are paused and resumed automatically, and Consent Mode v2 signals govern GA4, Google Ads and Floodlight without per-tag work. You add the consent script; the orchestration is built in.
What's the difference between Basic and Advanced Consent Mode?
In Advanced mode, Google tags load with denied-by-default signals and run cookieless until the visitor consents, preserving modeled conversions. In Basic mode, Google tags are held entirely until consent is granted. Clickio supports both; see our Consent Mode v2 page for the full picture.
How do I control a tag that has no consent API at all?
Change its type to text/clickiocmp and add a data-clickio-cmp-* attribute declaring the purposes or vendors it needs. The browser won't execute the script until the CMP confirms the visitor's consent matches. No wrapper code, no callbacks.
Does it work with Google Tag Manager?
Two ways. GTM's own consent features work through Consent Mode. And for per-purpose or per-vendor firing, the CMP pushes clickio_consent_update events and clickio_cmp_* dataLayer variables you can use in GTM triggers, with no custom JavaScript needed.
What about scripts added to the page after consent, by GTM for example?
A DOM observer watches for newly injected text/clickiocmp scripts and evaluates them against the visitor's consent as they appear. Late-injected tags follow the same rules as everything in your source.
What happens after a visitor makes a choice?
The pause lasts until the visitor decides. Ad slots then refresh according to the consent state; declined personalization uses non-personalized mode.
Ad-stack control and tag gating are included on every plan. Start a free trial.
Ad-stack control, Consent Mode v2 and attribute-based gating are on every plan, as is automatic blocking of supported non-advertising vendors; Microsoft UET consent signals start on Starter. Other tags use script attributes or GTM triggers.