Our WP cookie plugin automatically adds the iubenda code to all the pages of a site (to the HEAD section)
Allows the manual blocking of all other resources without direct intervention on the actual scripts
Allows the management of the iubenda Cookie Solution for multilingual sites using WPML. More information regarding this can be found in this article
It displays a clean page (without cookie banner) to users who have already provided their consent
It detects bots/spiders and serves them a clean page
It supports the auto-assignment of categories when blocking scripts
It supports AMP pages
Google Site Search
Google Tag Manager
Download the plugin from the WordPress plugin repository. Access the administration panel within WordPress and click on Plugins > Add New Plugin > Cookie Solution. Then install and activate it.
These scripts can be blocked by entering the source into the Custom Script boxes in the plugin console or by using the manual wrapping method illustrated in the example below and (in more detail) in this help post
Blocking custom scripts from within the console
The Custom Scripts field makes it easy for you to block scripts inserted into the page directly from within the plugin console. This greatly reduces the need for direct edits to the site’s code.
Here’s how to do it:
In the left menu within your administration panel click oniubenda Cookie Solution.
Next, scroll down to find the Custom scripts and Custom iframes fields near the center of the page.
Enter your script or iframe sources as needed, and click the Save Changes button at the bottom-left of the page.
Using these fields are pretty straightforward. Simply enter the script or iframe src attribute you’d like to block.
Let’s say you wanted to block scripts inserted into the page via the following iframe
What you’ll need to enter into the iframe field would be videowebsite.com/embed/ as this is the actual source of the scripts. Be careful NOT to enter the component id (videowebsite.com/embed/xxFhMChxx) to ensure that all scripts coming from the actual source are blocked.
Manual Use (wrapping method)
This method requires you to directly modify your site’s code. You’ll need to go into the relevant section of your site’s code and add the scripts to be blocked as explained below.
For example a conversion pixel for Google Ads would be handled this way:
Compliance obligations for different cookie typologies
We’ve prepared a table (Italian only) to better understand which categories of cookies require the banner, preemptive consent, notification to the appropriate regulatory body and so on.
How to install a Beta version of the Plugin
We often provide updated versions of our plugin which are unstable during the testing phase as Beta versions are.
To install a Beta version of the plugin, the first thing to do is install an external plugin called “WP Rollback”, which allows you to select an unofficial version of our plugin.
WP Rollback installation
Please note: WP Rollback requires a WordPress version above 4.0.
As for other plugins, you can install WP Rollback by accessing the Plugin area in your WordPress admin panel and clicking on “Add new”; from here you can search for “WP Rollback” and install it.
After the installation and activation, it will be necessary to go back to the page in which all the installed plugins are listed. Here you’ll notice that “Rollback” will have appeared next to every entry.
All that needs to be done now is to look for the “iubenda Cookie Solution” plugin and click on the “Rollback” entry. Here you’ll find all the different versions of the plugin; the version currently in use will be labelled “installed version”, while the Beta versions will be labeled as such.
To install and test the Beta version of the plugin, simply click on the Beta entry you wish to use. This will cause the current version of the Plugin to be overwritten by the Beta version; to revert the process, the same process will have to be undertaken, the difference being the selecting of the previous stable version and not the Beta one.
How to signal a bug or request support
To signal a bug please email us and provide a clear and detailed description of the problem.
It’s always useful to attach the debug information provided by WordPress along with your request for support. To access the debug information, you must open the WordPress installation folder and look for the file named wp-config.php.
Once inside, please look for the following line:
Modify it to:
Once the file saved, open a page on your WordPress and the debug information will start to appear. Keep our plugin active and send us any errors or messages shown by WordPress.