.png)
.png)
The banner shows, but scripts aren’t being blocked
Possible cause 1: Scripts aren’t tagged for blocking.
Solution: 1. Run a cookie scan in ConsentBit. 2. Confirm the scripts you expect to block are listed and assigned to a non-Necessary category. 3. If they aren’t detected, tag them manually with type="text/plain" and data-consentbit-category="..." (see Section 14.3).
Possible cause 2: ConsentBit script loads after other tracking.
Solution: 1. Open page source. 2. Confirm the ConsentBit <script> tag appears before any other tracking scripts in the <head>. 3. If it’s after, move it to be the first script in head.
Possible cause 3: Scripts are injected dynamically by another tool (e.g., Google Tag Manager).
Solution: 1. In Google Tag Manager, set up the Consent Initialization tag. 2. Use ConsentBit’s Consent Mode v2 integration (see Section 8.3). 3. In each GTM tag’s settings, configure the Additional Consent Checks to require consent before firing.