Script Blocking
Script blocking decides what CookieRay does with tracking scripts before a visitor has given consent. You pick the behavior in Settings, choosing between two modes: Log Only and Strict.
Log Only mode
In Log Only mode, CookieRay records consent without enforcing blocking. It captures what each visitor agreed to, but it does not stop any scripts from running.
In Log Only mode, you must ensure your third-party integrations respect consent themselves. CookieRay is keeping the record, but it is not standing between the visitor and the scripts.
Use this mode when your tracking tools already have their own consent handling, or when you want to observe consent activity before enforcing anything.
Strict mode
In Strict mode, CookieRay delays known tracking scripts until the visitor agrees to matching categories. It intervenes early so that known tracking snippets don’t execute before consent is given.
Once a visitor consents to a category, the scripts mapped to that category are allowed to run.
Built-in patterns
CookieRay includes built-in patterns to recognize common tracking scripts, including:
- Google Analytics
- Meta Pixel
- Hotjar
- HubSpot
- TikTok Pixel
- and many others
These patterns let Strict mode identify and hold known trackers without you having to configure each one by hand.
Choosing a mode
| Mode | What it does | When to use |
|---|---|---|
| Log Only | Records consent, does not block | Your integrations enforce consent themselves, or you want to observe first |
| Strict | Delays known trackers until consent matches their category | You want CookieRay to enforce blocking before consent |
Pick the mode that matches how much enforcement you want CookieRay to handle directly.