Pen Settings



CSS Base

Vendor Prefixing

Add External Stylesheets/Pens

Any URLs added here will be added as <link>s in order, and before the CSS in the editor. You can use the CSS from another Pen by using its URL and the proper URL extension.

+ add another resource


Babel includes JSX processing.

Add External Scripts/Pens

Any URL's added here will be added as <script>s in order, and run before the JavaScript in the editor. You can use the URL of any other Pen and it will include the JavaScript from that Pen.

+ add another resource


Add Packages

Search for and use JavaScript packages from npm here. By selecting a package, an import statement will be added to the top of the JavaScript editor for this package.


Auto Save

If active, Pens will autosave every 30 seconds after being saved once.

Auto-Updating Preview

If enabled, the preview panel updates automatically as you code. If disabled, use the "Run" button to update.

Format on Save

If enabled, your code will be formatted when you actively save your Pen. Note: your code becomes un-folded during formatting.

Editor Settings

Code Indentation

Want to change your Syntax Highlighting theme, Fonts and more?

Visit your global Editor Settings.


                <!doctype html>

    <script type="text/javascript">
        var _iub = _iub || [];
        _iub.csConfiguration = {
                "lang": "en",
                "siteId": 896537, //use your siteId
                "cookiePolicyId": 8207462, //use your cookiePolicyId
                "consentOnContinuedBrowsing": false, //avoid to collect consent by scrolling and continued browsing activity
                "perPurposeConsent": true,
                "banner": {
                    "acceptButtonDisplay": true,
                    "closeButtonRejects": true,
                    "customizeButtonDisplay": true,
                    "explicitWithdrawal": true,
                    "listPurposes": true,
                    "position": "float-top-center",
                    "rejectButtonDisplay": true

                //some (optional) callbacks that our Cookie Solution can perform upon the occurrence of an event
                callback: {
                    "onConsentGiven": function() {
                        //invoked if the user has given the consent to the installation of cookies
                    "onConsentRejected": function() {
                        //invoked if the user has rejected the consent to the installation of cookies
                    "onPreferenceExpressed": function(preference) {
                        //fires whenever a preference is expressed, be it accept or reject
                        log('onPreferenceExpressed(' + JSON.stringify(preference) + ')');
    <script type="text/javascript" src="//" charset="UTF-8" async></script>

        <div class="wrapper">
            <h1>iubenda Cookie Solution</h1>
            <p>Per-category consent</p>

    <section class="wrapper">

        <p>This is one of the possible setups of our Cookie Solution: it's essentially the default configuration except for consent on continued browsing (disabled here), and the addition of the <a href="" target="_blank">reject button</a> and <strong>per-category consent</strong>.</p>
        <p>This feature gives users granular control on which categories of cookies or other identifiers to give consent to:</p>

        <div class="scripts">
            <li>Strictly necessary (purpose id 1): <span id="pur-1" class="activated">activated</span> (no consent required)</li>
            <li>Basic interactions & functionalities (purpose id 2): <span id="pur-2">blocked</span></li>
            <li>Experience enhancement (purpose id 3): <span id="pur-3">blocked</span></li>
            <li>Measurement (purpose id 4): <span id="pur-4">blocked</span></li>
            <li>Targeting & Advertising (purpose id 5): <span id="pur-5">blocked</span></li>
            <li>Scripts with purposes 2 and 5: <span id="pur-2-5">blocked</span></li>

        <div id="logs"></div>

        <script type="plain/text" class="_iub_cs_activate" data-iub-purposes="1">
            document.getElementById('pur-1').innerHTML = 'activated';
            document.getElementById('pur-1').className = 'activated'
        <script type="plain/text" class="_iub_cs_activate" data-iub-purposes="2">
            document.getElementById('pur-2').innerHTML = 'activated';
            document.getElementById('pur-2').className = 'activated';
        <script type="plain/text" class="_iub_cs_activate" data-iub-purposes="3">
            document.getElementById('pur-3').innerHTML = 'activated';
            document.getElementById('pur-3').className = 'activated';
        <script type="plain/text" class="_iub_cs_activate" data-iub-purposes="4">
            document.getElementById('pur-4').innerHTML = 'activated';
            document.getElementById('pur-4').className = 'activated';
        <script type="plain/text" class="_iub_cs_activate" data-iub-purposes="5">
            document.getElementById('pur-5').innerHTML = 'activated';
            document.getElementById('pur-5').className = 'activated';
        <script type="plain/text" class="_iub_cs_activate" data-iub-purposes="2,5">
            document.getElementById('pur-2-5').innerHTML = 'activated';
            document.getElementById('pur-2-5').className = 'activated';

        <p>The categories are displayed along with a short description and toggle so that users can either grant or reject consent for the particular processing purpose. The categories displayed in the modal are automatically detected, but they can also be customized by using the <code>purposes</code> parameter or through the configurator (see the <a href="" target="_blank">dedicated demo</a>).</p>
        <div class="tip">
            <p>💡 Click on the "Learn more and customize" button to see this feature in action. Grant consent to the "Experience enhancement" category to release the YouTube and Twitter scripts below.</p>
        <p>On the configurator:</p>
        <img src="" width="480" />
        <p>More options available in the Advanced View.</p>
        <div class="note">
                <li>Remember to use your own credentials from <a href="" target="_blank">your iubenda account</a></li>
                <li>This is a sample for pure demonstrative purposes, <strong>no consents are saved</strong> (result of <code>_iub.csConfiguration.skipSaveConsent = true</code>). Just refresh the page to make the cookie banner reappear.</li>
                <li><strong>If you don't see the cookie banner on your first visit</strong>, you may have a consent cookie saved from another demo: <a href="#" onclick="_iub.cs.cookie.resetCookies({local: true,remote: true});alert('Consent cookie deleted. Now click on OK and refresh the page to return to the starting point.')">reset consent</a> and refresh the page to make the cookie banner reappear.</li>
        <h3>Block cookies prior to consent</h3>

        <p>To demonstrate the cookie blocking feature, we've embed a YouTube video:</p>

        <div class="embed-container" -->
            <!-- please note type="text/plain" class="_iub_cs_activate" data-suppressedsrc="..." (manual tagging) and data-iub-purposes="3" (per-category consent) -->
            <iframe type="text/plain" class="_iub_cs_activate" width="560" height="315" data-suppressedsrc="" data-iub-purposes="3" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>

        <p>And a 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="" class="twitter-follow-button" data-show-count="true" data-size="large">Follow @iubenda</a>
        <script async type="text/plain" class="_iub_cs_activate" data-suppressedsrc="" data-iub-purposes="3" charset="utf-8"></script>

        <p>Both scripts are blocked through <a href="">manual tagging</a>, one of the <a href="" target="_blank">methods available</a> with the Cookie Solution.</p>

        <p>Since both the YouTube video widget and the Twitter follow button are part of the <strong>Experience enhancement</strong> purpose (id <code>3</code>), we've added <code>data-iub-purposes="3"</code> to their scripts so that the Cookie Solution can properly identify them for release.</p>

        <p>Click on the <strong>Accept</strong> button - or just activate the "Experience enhancement" toggle - to release these scripts (refresh the page to return to the starting point).</p>

        <hr />

        <h3>Learn more</h3>
        <div class="tip">
            <p>Read our <a href="" target="_blank">advanced guide</a> for more information about per-category consent (including manual tagging, Google Tag Manager and WordPress plugin blocking methods).</p>

        <p>Other helpful resources:</p>
        <ul class="guides">
            <li><a href="" target="_blank">Cookie Solution - Getting Started</a></li>
            <li><a href="" target="_blank">How to Customize the Look and Behavior of the Cookie Banner (Beginner's Guide)</a></li>
            <li><a href="" target="_blank">How to Configure Your Cookie Solution (Advanced Guide)</a></li>
            <li><a href="" target="_blank">Introduction to the Prior Blocking of Cookies</a></li>





                //don't copy this JS (just for demo purposes)

//don't save consent, always show the banner
_iub.csConfiguration.skipSaveConsent = true;

//per-category logs
function log(text) {
    var p = document.createElement('p');
    p.innerText = text;

window.onerror = function(err) {
    log('ERROR: ' + err);