iubenda All-in-one Compliance – WordPress plugin

Next, you can configure the cookie banner/consent banner directly in our configurator here.
You can check our complete guide on the Privacy Controls and Cookie Solution for more information.

Finally, paste the embed code and click save settings in the bottom-right of the page.

Automated prior-blocking of scripts

Our WP plugin will also recognize and automatically detect and block the cookies indicated in the above block list on your site.

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 dramatically 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 on iubenda.
• Next, click on configure in the Privacy Controls and Cookie Solution area and scroll down to find the Blocked domains setting.
• Enter your script or iframe sources as needed, assign their purpose (optional), and click the Save Changes button at the bottom-left of the page.

Usage Examples

Using these fields is pretty straightforward. Simply enter the script or iframe src attribute you’d like to block.

Script

If you wanted to block a social button (which inserts scripts into the page via JavaScript), you’d simply need to enter the script source, e.g. connect.socialwebsite.net/en_US/track.js into the scripts field.

iframe

Let’s say you wanted to block scripts inserted into the page via the following iframe

<iframe width="1280" height="720" src="https://www.videowebsite.com/embed/xxFhMChxx" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></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 modify your site’s code directly. As explained below, you’ll need to go into the relevant section of your site’s code and add the scripts to be blocked.

For example, a conversion pixel for Google Ads would be handled this way:

<!--IUB-COOKIE-BLOCK-START-->
<script type="text/javascript">
    /* <![CDATA[ */
    var google_conversion_id =CONVERSION_ID;
    var google_conversion_label = "CONVERSION-LABEL";
    var google_custom_params = window.google_tag_params;
    var google_remarketing_only = true;
    /* ]]> */
</script>
<script type="text/javascript" src="//www.googleadservices.com/pagead/conversion.js">
</script>
<noscript>
    <div style="display:inline;">
        <img height="1" width="1" style="border-style:none;" alt="" src="//googleads.g.doubleclick.net/pagead/viewthroughconversion/1030205862/?value=0&amp;guid=ON&amp;script=0"/>
    </div>
</noscript>
<!--IUB-COOKIE-BLOCK-END-->

If you’ve enabled the per-category consent feature, you’ll need to assign the purpose. Resuming the previous example, being part of the “Targeting & Advertising” purpose (id 5):

<!--IUB-COOKIE-BLOCK-START-PURPOSE-5-->
      <script type="text/javascript">
      ...
      </script>
      <script type="text/javascript" src="..."></script>
      <noscript>
      ...
      </noscript>
<!--IUB-COOKIE-BLOCK-END-PURPOSE-5-->

If there are HTML / IMG / IFRAME elements, you will need to do it this way:

<!--IUB-COOKIE-BLOCK-START-->
      <iframe src="...
      <img src="...
<!--IUB-COOKIE-BLOCK-END-->

To stop automatic parsing/replacing the iframe/scripts that contain a defined src:

<!--IUB-COOKIE-BLOCK-SKIP-START-->
      <script type="text/javascript">...</script>
<!--IUB-COOKIE-BLOCK-SKIP-END-->

Shortcodes are available for elements installed directly within WordPress posts (as opposed to elements integrated at the template level – for example, footer.php):

[iub-cookie-policy]
[/iub-cookie-policy]

iubenda and Google AMP – How to collect cookie consent in WordPress

If you’re using or planning to use Google’s Accelerated Mobile Pages (AMP) to load your web pages faster on mobile, you might be wondering how to set up your WordPress site in a way that allows you to collect cookie consent and avoid penalties. It requires some work, but luckily, iubenda can help: in fact, our All-in-one compliance plugin for WordPress is fully compatible with AMP.

For a step-by-step guide (complete with sample codes, a demo, and WordPress tips) and more information on how to block cookies before user consent on AMP, read How to integrate iubenda Privacy Controls and Cookie Solution with Google AMP (WordPress method included).

Further information

For API calls and xmlrpc we suggest the following parameter ?iub_no_parse=1: this will place the iubenda script in a deactivated state and therefore avoids all parsing/replacing operations.