Steps to take if you are encountering unexpected issues using Clym's blocking solution
While we hope that your process of adding Clym's blocking script is smooth and seamless, we understand that there are possibly edge cases where you may encounter roadblocks. In any situation, we want you to know that we are here to help, so please don't hesitate to reach out to support@clym.io. Below you can find several troubleshooting steps for helping to pinpoint the issue you are experiencing in the meantime.
I rejected everything but still see some cookies on my website. How can I fix this?
If you reject everything and you still see cookies in your browser, that might be because:
- Those cookies were created earlier when the scripts were enabled, and even rejecting a service does not mean the cookie will be destroyed. To test it out, you can visit your website from an opt-out location in incognito mode.
If you still see cookies that are created and you think they are not Essential cookies, for example, _ga cookies that belong to Google Analytics, then it is possible that something with the blocking does not work correctly. We recommend checking the source code of the website to verify if the execution of the script is in progress. If yes, you should follow this troubleshooting guideline below.
How do I know what scripts are blocked on my website?
If you want to know exactly what scripts are picked up by Clym on individual webpages, you can read the “window.CLYM_BLOCKING_SCRIPTS” global variable. This variable includes a list of objects of the scripts that are being picked up by our system. In each object, 2 flags indicate the status of the script.
If it’s blocked: true, it means that the script is getting blocked, and if it’s injected: true, it means that consent was given and Clym put the script back to the source code.
Nothing gets picked up in the CLYM_BLOCKING_SCRIPTS variable. Why is that?
If you get an empty list, it might be because
- There are no scripts that can be blocked on your website
- The blocking.js was not implemented at the very beginning of the <head> tag
- You use it in explicit mode, and nothing was set to blocked explicitly
Some of my scripts and functionalities are not working properly after implementing the Clym Blocking solution.
- If Clym blocks a certain script or a cookie, you can whitelist it by following the following steps. Even after applying restrict-blocking and attempting implicit blocking on your website, the issue may persist because the blocking solution script delays the execution of your scripts. In this case, it might be better to switch to alternative solutions from Blocking to Clym Tag Manager or Clym Google Tag Manager integration.
If you encounter any challenges, please reach out to us at support@clym.io.