Created your Weebly website and need to manage cookies? In this guide, you’ll learn when you need a cookie consent management system for Weebly and how to add iubenda’s Privacy Controls and Cookie Solution to your Weebly site.
Jump directly to How to add iubenda’s Privacy Controls and Cookie Solution to your Weebly site.
Do I need a cookie policy for Weebly?
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 Weebly site? See the Weebly privacy policy integration guide.
What the solution supports
When you embed the Privacy Controls and Cookie Solution on your Weebly 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 iubenda’s Privacy Controls and Cookie Solution to Weebly
Once you’ve generated and customized your Privacy Controls and Cookie Solution, follow these steps to integrate it with your Weebly website.
Step 1: Copy your iubenda code
Head over to your iubenda dashboard and click on [Your website] > Privacy Controls and Cookie Solution > Embed.
Here you can customize your banner and then click Copy to copy your Privacy Controls and Cookie Solution snippet.
Step 2: Open the Weebly editor
- Log into your Weebly dashboard.
- Click Edit site to open the editor.
Step 3: Add the iubenda script
- In the editor, go to Settings > General.
- Scroll down to the Cookie Banner section.
- Paste your iubenda Privacy Controls and Cookie Solution code into the Cookie Banner text box.
- Click Save.
- Publish your site to apply the changes.
Note
It may take up to 24 hours for the cookie banner to appear on your website’s frontend after publishing.
Set up prior blocking of cookie scripts
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.
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 Weebly 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 Weebly editor, click on Edit Site.
Then, open your Build tab to find the script you need to modify (search for the service you want to block) and click Edit Custom HTML to open the code editor.
Step 2: Modify your script
- Add the class
_iub_cs_activateto the script tags, and change the “type” attribute fromtext/javascripttotext/plain - Replace the src with
data-suppressedsrcorsuppressedsrc - Specify the categories of the scripts/iframes with a comma-separated
data-iub-purposesattribute, e.g.data-iub-purposes="2"ordata-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.
Both scripts are blocked through manual tagging. Since both widgets 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 scripts do not load if you do not consent. (You can test this 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: Weebly-specific considerations
Keep these points in mind when using Privacy Controls and Cookie Solution on Weebly:
- Built-in Cookie Banner field. Weebly provides a dedicated Cookie Banner field under Settings > General. This is the recommended location for your iubenda snippet, as it ensures the code loads on every page.
- Publishing delay. After adding your code and publishing, it may take up to 24 hours for the cookie banner to appear on your site’s frontend.
- Limited code injection options. Weebly’s closed architecture means manual tagging can be more difficult for scripts added through Weebly’s built-in elements. For these, auto-blocking is the recommended approach.