Book a demo
Sign up

Privacy Controls and Cookie Solution – Jimdo Integration Guide

Built your website on Jimdo and need to manage cookies? In this guide, you’ll learn when you need a cookie consent management platform (CMP) or a cookie policy for Jimdo and how to add iubenda’s Privacy Controls and Cookie Solution to your Jimdo site.

Jump directly to How to add iubenda’s Privacy Controls and Cookie Solution to your Jimdo site.

Yes, and here’s why.

If you have EU-based users and your website uses cookies (which it most likely does), you need to manage cookie consents according to the ePrivacy Directive and GDPR. This means you need to block cookie scripts and similar technologies until the user gives consent.

Also, for the consent to be considered valid, you need to make certain disclosures via a cookie banner and link to a more detailed cookie policy. See our getting started guide.

Need to add a privacy policy to your Jimdo site? See the Jimdo privacy policy integration guide.

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. On the free plan, custom code injection isn’t available, so you can only link to your iubenda-hosted policy page.

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:

Before adding the cookie banner, generate a cookie policy for your Jimdo site. Head over to your iubenda dashboard and click on [Your website] > Privacy and Cookie Policy > Edit. Add each service your site uses (e.g. Google Analytics, embedded videos, social buttons) so that your cookie policy accurately reflects your data processing activities.

Once your cookie policy is ready, the Privacy Controls and Cookie Solution will automatically link to it from your cookie banner.

Generate a cookie policy in the iubenda dashboard
Note

The Privacy Controls and Cookie Solution requires that you link to a cookie policy from your banner as legally required. If you have the cookie policy feature activated on your iubenda account (as explained here), the Privacy Controls and Cookie Solution automatically integrates your cookie policy into the solution once the option is selected. Otherwise, if you already have your own compliant cookie policy, you can simply insert your own link there. Either way, please remember that a cookie policy is required.

Not sure what privacy documents you need for your Jimdo site? Take this quick quiz to see which laws apply to you and your business.

Once you’ve generated and customized your Privacy Controls and Cookie Solution, follow these steps to integrate it with your Jimdo website.

First, head over to your iubenda dashboard and click on [Your website] > Privacy Controls and Cookie Solution > Embed.

How to add the Privacy Controls and Cookie Solution to Jimdo

Then click Copy to copy your Privacy Controls and Cookie Solution snippet.

Copy the Privacy Controls and Cookie Solution snippet

Now head over to Jimdo. The exact location for pasting the snippet depends on which Jimdo product you use.

Jimdo Creator (legacy editor)

In your Jimdo Creator dashboard, open Settings > Edit Head, then paste the iubenda snippet into the head editor and save. The Edit Head option is available on paid Jimdo Creator plans only.

Jimdo Creator - Edit Head section

Paste the iubenda snippet in the Edit Head box

Jimdo Dolphin (AI-driven editor)

Jimdo Dolphin doesn’t allow custom HTML on the free or base plans. To install the iubenda snippet, you need a Business plan (or higher). Once on a supported plan, add a custom HTML block or use the site-wide code injection option, paste the iubenda snippet, and save.

Whichever Jimdo product you use, the iubenda cookie banner will automatically appear on the first visit. User preferences are stored so that the banner won’t be triggered again for the same visitor. All available options to customize the banner’s style and behavior are described in this guide.

Few categories of cookies are exempt from the consent requirement. Therefore, almost all scripts that install or can install cookies must be blocked before consent is obtained.

Set up prior blocking after installation. This step is legally mandatory under EU law. Skipping it means non-exempt cookies may fire before the user consents.

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. It’s the recommended approach for Jimdo sites, since Jimdo’s editor-based architecture makes manual tagging harder than on a self-hosted stack.

If you prefer to manually tag your scripts that install or may install cookies, you can still follow the process below for step-by-step instructions and practical examples. However, we highly recommend considering the auto-blocking feature for a more streamlined approach.

Learn more about auto-blocking and how it can simplify your cookie-blocking process.

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:

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

In this tutorial, we’re going to block a Twitter 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.

In your Jimdo editor, open the page or widget containing the third-party script you want to block (search for the service, in this case, the Twitter follow button). On Jimdo Creator, look inside the widget’s HTML/Widget block. On Jimdo Dolphin, open the custom HTML block on your Business plan.

Open the code editor so you can modify the script directly.

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. For example, Google Analytics may be used for Measurement, while the Pinterest button may be used for Experience (Purpose 3 below). Purposes are grouped into 5 categories, each with an id (1, 2, 3, 4, and 5):

  • Necessary (id: 1)
  • Functionality (id: 2)
  • Experience (id: 3)
  • Measurement (id: 4)
  • Marketing (id: 5)

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

Let’s take the Twitter follow button as an example:

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>Twitter 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>

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’ve described above. You can use this CodePen as a guide to see what happens before and after blocking scripts via manual tagging.

(see the example)

To demonstrate the cookie blocking feature, we’ve embedded a YouTube video and a Twitter follow button:
Follow @iubenda

Both scripts are blocked through manual tagging. Since both the YouTube video widget and the Twitter follow button are part of the Experience 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” 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 YouTube and Twitter scripts don’t load if you don’t consent. (You can test this again by opening this link in incognito mode in your browser.)

After you’ve 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 the Privacy Controls and Cookie Solution on Jimdo:

  • Paid plan required. Custom code injection isn’t available on Jimdo’s free plan. To install the iubenda snippet, you need a paid Jimdo Creator plan or a Jimdo Dolphin Business plan (or higher).
  • Creator vs. Dolphin. Jimdo offers two product families: Jimdo Creator (the legacy manual editor) and Jimdo Dolphin (the AI-driven editor). The installation path differs between them. Use Settings > Edit Head in Creator, or a custom HTML block on Dolphin Business.
  • Snippet placement. For auto-blocking to work correctly, the iubenda snippet should load as early as possible. On Jimdo Creator, the Edit Head field is the right location. On Jimdo Dolphin, use the site-wide code injection option rather than a per-page HTML block so the snippet loads across the entire site.
  • Third-party widgets. Jimdo’s built-in widgets (contact forms, image galleries, analytics) may load their own scripts you can’t directly edit. If manual tagging isn’t possible for these, use auto-blocking or configure them via Google Consent Mode where supported.

Manage cookie consent for your Jimdo website

Generate a cookie banner

See also