You might have seen a notification as shown below:
We have enabled integrations for plugins and services, please double-check your configuration. For more information, please read this article.
But what does it mean?
Integrations are one of the main reasons why WordPress plugins are better in consent management than cloud services like Cookiebot or OneTrust. You can read more about that here.
WordPress configurations are extremely varied and intricate, due mostly to different themes and plugin available to WordPress users. For these themes and plugins, a consent management plugin might need to adapt to handle consent. These are called integrations and are native to a WordPress plugin.
When is an integration needed?
Consent Management by Complianz is configured in the wizard. But the bulk of the heavy lifting is done automatically, without the need of configuring anything. Complianz’ is created to be made broadly compatible without much effort from our users. This is done by minimal configuration by you, but many integrations from our end. A recurring example is Google Maps.
While Google Maps by default is either done by iFrame, API and/or javascript and well documented by Google, when handled by a theme or plugin the implementations can be wildly different and might be dependent on many other factors than an isolated Google Maps script. These plugins or themes need an integration to work properly before and after consent, with or without placeholder.
If you’re missing an integration, it might be it should work out-of-the-box or is available on our Github page. If you’re not sure, please leave a feature request and we will have a look.
