Privacy Controls and Cookie Solution – Jimdo Integration Guide

If you operate in the EU (or have EU visitors) and use cookies on your Jimdo site, privacy regulations like the GDPR and the ePrivacy Directive require you to:

Provide a cookie policy (you can add a cookie section to your privacy policy, learn more about creating a Privacy and Cookie Policy for Jimdo)
Display a cookie banner at the user’s first visit
Block non-exempt cookies (e.g. via Google Analytics) before obtaining user consent
Release cookies only after informed consent has been provided

iubenda’s Privacy Controls and Cookie Solution handles all of this: it displays a fully customizable cookie banner, collects consent, implements prior blocking, and supports compliance with multiple privacy frameworks.

To install the Privacy Controls and Cookie Solution, you need to add custom code to the <head> of your Jimdo site. This requires a paid Jimdo plan (Creator Pro or higher). On free or lower-tier plans, custom code injection is not available. More info on Jimdo’s help documentation.

What the solution supports

When you embed the Privacy Controls and Cookie Solution on your Jimdo site, you get access to the full iubenda cookie management platform:

Fully customizable cookie banner with options to match your site’s branding and colors
Automatic cookie policy generation based on the services detected on your site
Auto-blocking of scripts that install cookies before consent is collected
Integration with Google Consent Mode v2 (iubenda is a Google-certified CMP)
Integration with IAB’s Transparency and Consent Framework (TCF 2.3)
Support for US state privacy laws (CCPA/CPRA, VCDPA, CPA, CTDPA, and others)
Support for the Swiss Federal Act on Data Protection (FADP)
Support for Brazil’s LGPD
Granular, per-category consent (e.g. Functionality, Experience, Marketing)
Geo-detection to limit consent requests to regions where legally required
Storage of consent proofs for accountability

How to add the iubenda cookie banner on your Jimdo website

Generate your cookie banner from your iubenda dashboard. You can customize colors, layout, and behavior to match your Jimdo site.
Once configured, go to the Embed section of the Privacy Controls and Cookie Solution in your iubenda dashboard and copy the code snippet:

iubenda dashboard showing the Privacy Controls and Cookie Solution embed section

iubenda embedding code snippet for the Privacy Controls and Cookie Solution

In your Jimdo dashboard, go to Settings > Edit Head.
Paste the iubenda code snippet into the Edit Head box as the first element and save.

Jimdo Edit Head - pasting the iubenda code snippet

The iubenda cookie banner will now appear automatically at each visitor’s first visit. User consent is recorded and stored, so the banner won’t appear again on subsequent visits from the same browser.

Few categories of cookies are exempt from the consent requirement. Therefore, you need to block scripts from running until you get valid user consent.

Simplify your cookie-blocking process with auto-blocking

There’s a simpler option available for the prior blocking of cookies and trackers. Our auto-blocking feature automates the process, saving you time and effort. This is the recommended approach for Jimdo sites, since it works without any manual code changes.

If you prefer to manually tag your scripts, follow the step-by-step instructions below, or explore other methods in our general introduction to the prior blocking of cookies.

How to implement prior blocking via manual tagging on your Jimdo site

Manual tagging is the method of prior blocking we use for the tutorial below. You can view other methods here.

To set up prior blocking, you need to make some minor changes to your site’s scripts:

Identify the script/iframe for any additional services running on your website (e.g., a social media follow button)
Add some simple text to the HTML code (we show you how below)
Save

In this tutorial, we are going to block a social media follow button.

Not sure which services you need to block? If you’re using a Cookie Policy generated by iubenda, the services listed in your Cookie Policy are most likely the ones you need to modify.

Step 1: Identify the script

In your Jimdo dashboard, navigate to Settings > Edit Head. This is where you’ll find any custom scripts you’ve added to your site. Identify the script you need to block (e.g., a social media widget, analytics tracker, or advertising pixel).

If you’ve added third-party scripts via Jimdo’s HTML widget within a page, you’ll also need to locate those scripts and apply the changes described below.

Step 2: Modify your script

Now, we’re going to change the script. To do this, make 3 simple changes:

Add the class _iub_cs_activate to the script tags, and change the “type” attribute from text/javascript to text/plain
Replace the src with data-suppressedsrc or suppressedsrc
Specify the categories of the scripts/iframes with a comma-separated data-iub-purposes attribute, e.g. data-iub-purposes="2" or data-iub-purposes="2, 3"

More about categories and purposes

Purposes are your legal reasons for processing the particular type of user data. Different scripts on your site will fall into different categories and serve different purposes. Purposes are grouped into 5 categories, each with an id (1, 2, 3, 4, and 5):

Necessary (id: 1)
Basic interactions & functionalities (id: 2)
Experience enhancement (id: 3)
Measurement (id: 4)
Marketing (id: 5)

For more detailed info on categories and purposes, see our guide here.

Here is an example using a social media follow button:

We need to 1. Add the class and change the “type” attribute, 2. replace the src and 3. specify the categories.

The code structure should look like this:

<p>Follow button:</p>

        <!-- please note type="text/plain" class="_iub_cs_activate" data-suppressedsrc="..." (manual tagging) and data-iub-purposes="3" (per-category consent) -->
<a href="https://twitter.com/iubenda" class="twitter-follow-button" data-show-count="false">Follow @iubenda</a>
  <script async type="text/plain" class="_iub_cs_activate" data-suppressedsrc="https://platform.twitter.com/widgets.js" data-iub-purposes="3" charset="utf-8"></script>

Step 3: Save!

Now that you’ve made your changes, hit save, and you’re done.

Not sure if you’ve set up correctly? Check out the live example and FAQs below.

Live example

This is an example that shows everything we have described above. You can use this CodePen as a guide to see what happens before and after blocking scripts via manual tagging. (we’ve embedded a YouTube video, and a Twitter follow button)

(see the example)

Both scripts are blocked through manual tagging. Since both widgets are part of the Experience enhancement purpose (id 3), we’ve added data-iub-purposes="3" to their scripts so that the Privacy Controls and Cookie Solution can properly identify them for release.

Click on the Accept button, or activate the “Experience enhancement” toggle, to release these scripts (refresh the page to return to the starting point).

How can I tell if I’ve set prior blocking up properly?

As you can see in the CodePen example, the scripts do not load if you do not consent. (You can test this function again by opening the example in incognito mode in your browser.)

After you have saved, open your site in incognito mode and check if the scripts you blocked via manual tagging stay blocked until you consent.

For other blocking options, see Google Consent Mode as an alternative to prior blocking, Google Tag Manager to simplify the blocking of cookies, or the IAB Transparency & Consent Framework and how to enable it.

Good to know: Jimdo-specific considerations

Keep these points in mind when using Privacy Controls and Cookie Solution on Jimdo:

Paid plan required. Custom code injection requires a paid Jimdo plan (Creator Pro or higher). Lower-tier plans and the free plan do not support adding custom code to the <head> section.
Code must be first in the head. For auto-blocking to work correctly, the iubenda snippet must be the first element in the <head>. Jimdo may add its own scripts before yours, which could affect blocking behavior. Test your setup after installation.
Use Settings > Edit Head. Jimdo’s Edit Head section (found under Settings) is the only place to add site-wide custom code. If you need to block scripts embedded within individual pages using Jimdo’s HTML widget, you’ll need to modify those scripts directly in the widget editor.
Google Tag Manager integration. If you use Google Tag Manager with your Jimdo site, you can use iubenda’s GTM template for consent-based script management via Google Consent Mode.