Iubenda logo
Start generating

Documentation

Table of Contents

How to add a Cookie Solution to Weebly

Created your Weebly website and need to manage cookies? We’ll show you how! In this guide, you’ll learn if and when you need a cookie consent management system (CMS) for Weebly and how to add iubenda’s Cookie Solution to your Weebly site.


➜ Jump directly to How to add iubenda’s Cookie Solution to your Weebly site.

Yes, you do, 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 and GDPR. This means that you’ll need to block cookie scripts and similar technologies until the user gives consent. 

Also, for the consent to be considered valid, you’ll need to make certain disclosures via a cookie banner and link to a more detailed cookie policy. More details here.

💡 Need to add a Privacy policy to your Weebly site? See the Weebly Privacy policy integration guide.

How to add iubenda’s Cookie Solution to Weebly

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

Once you’ve generated and customized your Cookie Solution you can follow these steps to integrate it with your Weebly website:

To get started first head over to your iubenda dashboard click on [Your website] > Cookie Solution > Embed.

How to add a Cookie Solution to Weebly

Here you can customize and then copy your Cookie Solution.

How to add a Cookie Solution to Weebly

First, head over to your Weebly site and click on Website > Site Preferences.

How to add a Cookie Solution to Weebly

Next, scroll down to “Cookie Consent“ and select Change cookie consent on the right.

How to add a Cookie Solution to Weebly

From here you want to select the Custom Banner Coder option and select Next.

How to add a Cookie Solution to Weebly

Lastly, paste your iubenda cookie solution code in the text box and click on Save.

How to add a Cookie Solution to Weebly

Congratulations, you’ve successfully added your iubenda cookie solution to Weebly! 

Please note it may take up to 24hours for your new cookie banner to appear on the front end of your website. 

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

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

Manual tagging is the method of prior-block we’ll be using for the tutorial below. You can view other methods here.

To set up prior blocking, you’ll need to make some minor changes to your site’s scripts. But it’s simple; just do the following:

  1. Identify the script/iframe for any additional services that are running on your website (e.g., Twitter follow button)
  2. Add some simple text to the HTML code (we’ll show you how below!)
  3. Save!

In this tutorial, we are 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 now.

In your Weebly admin, click on Edit Site

Then, open your Build tab to find the script you need to modify (simply search for the service you want to block, in this case, it is the Twitter follow button) and then click Edit Custom HTML to open the code editor.

Prior blocking checkbox - Flow page
Now, we’re going to change the script. To do this, we will make 3 simple changes:
  • add this class: _iub_cs_activate to the script tags, and change the “type” attribute from text/javascripttext/plain
  • replace the src with data-suppressedsrc or suppressedsrc
  • specify the categories of the scripts/iframes with a special 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 enhancement (Purpose 3 below). Purposes are grouped into 5 categories each with an id (1, 2, 3, 4, and 5):

  • strictly necessary (id: 1)
  • basic interactions & functionalities (id: 2)
  • experience enhancement (id: 3)
  • measurement (id: 4)
  • targeting & advertising (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.

And the code structure should be like this:

Prior blocking checkbox - Flow page
<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, simply 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 code pen 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 enhancement purpose (id 3) we’ve added data-iub-purposes="3" to their scripts so that the Cookie Solution can properly identify them for release.

Click on the Accept button – or just 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 code pen example, the Youtube and Twitter scripts do not load if you do not consent. (You can test this function again by opening this link (https://codepen.io/iubenda/pen/KKKxmVO/?editors=1000) in incognito mode in your browser)

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

Please refer to this dedicated article if you’d like to know how to block cookies before consent using other options available. ➔ Take a look at 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.

See also