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!
💡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.
Here you can customize and then copy your Cookie Solution.
First, head over to your Weebly site and click on Website > Site Preferences.
Next, scroll down to “Cookie Consent“ and select Change cookie consent on the right.
From here you want to select the Custom Banner Coder option and select Next.
Lastly, paste your iubenda cookie solution code in the text box and click on Save.
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.
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:
In this tutorial, we are going to block a Twitter follow button.
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.
_iub_cs_activateto the script tags, and change the “type” attribute from
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):
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:
<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>
Not sure if you’ve set up correctly? Check out the live example and FAQs below
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.
To demonstrate the cookie blocking feature, we’ve embedded a YouTube video, and a Twitter follow button:
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).
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.