Debugging Issues with Complianz

With thousands of different configurations in WordPress and possible themes, plugins, and manual implementations, sometimes, consent management might break functionality. Start here to fix the issue.

1. A script is not blocked properly

Complianz automatically detects the most popular services and plugins to integrate fully. In the wizard, you can specify specific services and social media to enable/disable integrations manually. Most heavy lifting is in the background, and you don’t have to worry about most configurations.

Still, you’re expecting Complianz to find, block, and release a service used, but it doesn’t appear to be blocked correctly. You can do this to find out why and how to proceed.

Take these steps

  • Make sure the cookie blocker is on. Under settings, please check if Safe Mode is disabled.
  • Disable all optimization plugins like WP Rocket, WP Optimize etc., or append a standard parameter ‘?nocache’ while the optimization . Proceed to 1.1 if this works.
  • Under integrations, check to see if the relevant service or plugin is found and enabled. If so, proceed to step 1.2.
  • Please check the documentation on our website regarding your service or plugin. We might have documentation that explains the steps to integrate with our script center.
  • If nothing is written about your service or plugin, try blocking the script yourself with our script center.
  • You can find a guide here.
  • We would appreciate a heads-up so we can integrate it in Complianz.
  • If you manually added a script, please follow this guide to adjust the attributes of your script.
  • If everything fails, and the script is unknown to Complianz, our website and can’t be blocked manually, please allow support to help you out. Let us know where you got stuck during these steps.
  • Ask support

1.1 Optimisation plugins

In rare cases, optimization plugins will defer or delay Complianz.min.js, which breaks functionality. You can exclude ‘complianz’ from any optimization plugin; Complianz minifies and defers itself by default.

More commonly, optimization plugins will combine javascript to a random hashed file. That file is not blocked, as the hash is random. Also, blocking combined scripts will block more than just the targeted service. You will have to exclude the service from the optimization plugin if needed.

  • If deactivating your optimisation plugins works, please continue.
  • Exclude ‘complianz’ from your optimisation plugin. If it doesn’t work…
  • Exclude the service or plugin Complianz needs to block.

1.2 A technical approach

The plugin or service is now found and integrated, but nothing seems to happen.

1.2.1 A plugin integration

If you’re having an issue with plugin integration, please follow this list:

  • Please ensure you’re on the latest version of Complianz and the integrated plugin. 
  • If that doesn’t help, please check our documentation for more context if available.
  • There are instances, for example, with Instagram Feed Plugins, that APIs are only used in the back-end and published as ‘native content. These will not be blocked, as the website visitor has no connection with Instagram.
  • Check to see if the integration is working properly:

1.2.2 Finding a script that needs to be blocked

Somehow, the integrated plugin is setting cookies on the front end, and now we have to find out which javascript file or inline script is setting these cookies. If you need help or find the culprit, please let us know!

Our manual to find the javascript that sets cookies before consent.

1.2.3 A service

Make sure your service doesn’t have a plugin integration or documentation for context on our website before you proceed. If your service is enabled under Complianz integrations but doesn’t get blocked properly, there are two main reasons:

  • The service is implemented manually and/or has custom development. If so, please block this script manually.
  • The service needs additional integrations; below is a Google Maps example to explain the necessity.

Example: Google Maps

Complianz offers a general service integration for common implementations of Google Maps, and supports multiple popular Google Maps plugins. There are however instances whereby Google Maps implementations are not supported. This is due to the fast amount of possibilities, themes and plugin, let alone API’s Google can use to add Google Maps to a website. We have created basic integration examples here: https://github.com/complianz/complianz-integrations/tree/master/Google%20Maps. If you are not familiar with PHP, please leave a feature request.

1.3 Feature request

The last step in debugging is realizing there’s no way of implementing your service or plugin without or help. You might either contacted us earlier and we created your request, or you can do it yourself here.