Prior-script blocking
Block trackers before consent, not after.
The problem
The dirty secret of cookie banners is that most of them record a choice while the trackers already fired on page load. Recording consent without blocking is the gap regulators fine you for.
With ConsentX
Nothing non-essential runs until the visitor says yes. If they say no, ConsentX sweeps the cookies that tried to set. That is the difference between looking compliant and being compliant.
How it works
Tag or auto-detect scripts
Mark scripts with data-cx-consent, or let ConsentX auto-block untagged third-party tags.
Nothing runs before a choice
Blocked tags stay inert until the matching category is allowed.
Sweep on reject
If a category is rejected, ConsentX aggressively clears cookies it tried to set.
What you get
- True prior consent, no first-load leaks
- Auto-block untagged third-party scripts
- Cookie sweeping when a category is rejected
- Works with GTM and direct tags
Where teams use it
- A site that failed a regulator cookie scan for pre-consent tags
- A team migrating off a banner that only records consent
- An agency standardizing real blocking across client sites
Helps you meet
Scan your site for leaksTry Prior-script blocking free
Install in minutes. Free plan, no credit card.
Frequently asked questions
Why is blocking different from recording consent?+
Recording writes a row, blocking actually prevents the tracker from running before consent. Regulators care about the second one.
Do I have to tag every script?+
No. You can tag scripts with data-cx-consent for precise control, or rely on auto-blocking of untagged third-party tags.
What happens to cookies if someone rejects?+
ConsentX sweeps cookies the rejected category tried to set, so a no really means nothing persists.